[vpnc-devel] have to type password twice now
jmvpnc at loplof.de
Fri Jun 20 03:31:08 CEST 2008
after your patch that introduced NEXT_PIN support SecurID users needed to
enter a password that was not evaluated before being allowd to enter the
passcode. So I committed a small patch that fixes that problem but I don't
have any way to test whether next-pin mode still works.
Is it possible for you to test this?
On Thu, Jun 19, 2008 at 06:08:48PM -0400, Rob West wrote:
> > > 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?
> 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
> 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.
Joerg Mayer <jmayer at loplof.de>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
More information about the vpnc-devel