Summary: | net/tightvnc vncviewer can't handle null authentication | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Peter Jeremy <peter> | ||||
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | marino, meta, meta, pi | ||||
Priority: | Normal | ||||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Peter Jeremy
2013-09-29 00:40:00 UTC
Responsible Changed From-To: freebsd-ports-bugs->itetcu Over to maintainer (via the GNATS Auto Assign Tool) Responsible Changed From-To: itetcu->freebsd-ports-bugs Reassign to the heap I'm not so comfortable to apply such a adhoc patch. Anyway, I will look how other vnc viewers treat empty password. -- `whois vmeta.jp | nkf -w` meta <meta@vmeta.jp> State Changed From-To: open->feedback This should have been set to feedback some time ago. Reassign to maintainer Strange, Koichiro IWAO is usually responsive. Moving this to patch-ready. Maintainer approval no longer needed due to multiple timeouts. Assuming this patch is still valid.. (In reply to meta from comment #3) > I'm not so comfortable to apply such a adhoc patch. > Anyway, I will look how other vnc viewers treat empty password. > > -- > `whois vmeta.jp | nkf -w` > meta <meta@vmeta.jp> Okay, so I see he did respond but never came up with a better patch, then didn't respond to the more recent ping. A commit references this bug: Author: pi Date: Mon Aug 11 18:33:10 UTC 2014 New revision: 364635 URL: http://svnweb.freebsd.org/changeset/ports/364635 Log: net/tightvnc: allow null authentication PR: 182474 Submitted by: peter@rulingia.com Approved by: meta@vmeta.jp (maintainer timeout) Changes: head/net/tightvnc/files/patch-vncviewer__rfbproto.c The implications for this are still open for discussion, but the need to allow vncviewer to connect to VBox is demostrated. If it needs to be reverted, pointy hat to me. |