Bug Tracker item #3434118, was opened at 2011-11-06 08:31 Message generated for change (Tracker Item Submitted) made by mfisk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126848&aid=3434118&group_id=254363
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: UN*X version Group: trunk Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mike Fisk (mfisk) Assigned to: Adam Tkac (atkac) Summary: Regression: Xvnc requires auth even on reverse connections Initial Comment: Reverse connections (trigerred with "vncconfig -connect") did not previously have the same client authentication requirements as connections accepted from Xvnc's listener, but now (DRC's pre-1.2 build binaries) it requires authentication from the client. In the 1_0 branch, SSecurityFactoryStandard::getSecTypes() has a parameter to specify if we're looking up security types for reverse connections or not. aktac's new Security::GetEnabledSecTypes in common/rfb/Security.cxx does not and apparently should. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126848&aid=3434118&group_id=254363 ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
