
robertfwest at gmail
Jun 19, 2008, 8:29 PM
Post #10 of 12
(289 views)
Permalink
|
OK, tried with revision 325. Both command-line and kvpnc work now. So, what is your favored way to handle Ubuntu? Get them to apply the patch or to grab a revision from svn? Thanks, Rob On Thu, Jun 19, 2008 at 6:08 PM, Rob West <robertfwest[at]gmail.com> wrote: > Yesterday is a little hazy due to being at YAPC, but I'm fairly sure I > tried it and it worked. To be sure though, I'll try to update and retest > again tonight. > > So, how can I test the NEXT_PIN mode? I think I've hit it in the past, but > don't know what I did to hit it. > > Cheers, > Rob > > > On Wed, Jun 18, 2008 at 12:51 AM, Joerg Mayer <jmvpnc[at]loplof.de> wrote: > >> On Tue, Jun 17, 2008 at 01:21:46PM -0500, Rob West wrote: >> > I checked out revision 317 and built trunk. It still has the problem >> with >> > our VPN. >> > >> > So, I ran it with debug level 3 to give you more info. The output is >> > attached. >> >> OK, by looking at the trace I finally understood what this is all about: >> SecurID and maybe other token cards showed that problem, normal password >> prompts didn't. Your proposed fix seems correct in that it restores the >> previous behaviour. I'm not quite sure that the previous behaviour is >> correct in all cases but that's a different story. >> Both, trunk and Nortel branch have your fix, so everyone who had this >> problem: Please test. If possible: Can you test whether the NEXT_PIN mode >> for SecurID still works? >> >> Thanks for your analysis! >> >> Joerg >> _______________________________________________ >> vpnc-devel mailing list >> vpnc-devel[at]unix-ag.uni-kl.de >> https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel >> http://www.unix-ag.uni-kl.de/~massar/vpnc/<http://www.unix-ag.uni-kl.de/%7Emassar/vpnc/> >> > >
|