Bug 679869

Summary:	VPNC does not support token change
Product:	[Fedora] Fedora	Reporter:	Zdenek Kabelac <zkabelac>
Component:	NetworkManager-vpnc	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	dcbw, nphilipp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-25 13:38:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Zdenek Kabelac 2011-02-23 18:14:33 UTC

Description of problem:

NM failed to connect to vpnc - and was just giving all the time
only message about failed connection.

After configure  /etc/vpnc/default.conf to be able to use 'vpnc' command line - it's been pretty simple to log in - as the command line provided simple query to insert next token.

==
S5.3 type-is-xauth check
 [2011-02-23 18:42:12]

S5.4 xauth type check
 [2011-02-23 18:42:12]

Wait for token to change,
then enter the new tokencode:
===

Version-Release number of selected component (if applicable):
NetworkManager-gnome-0.8.2-8.git20101117.fc15.x86_64
NetworkManager-glib-0.8.2-8.git20101117.fc15.x86_64
NetworkManager-vpnc-0.8.1-1.fc14.x86_64
NetworkManager-debuginfo-0.8.2-8.git20101117.fc15.x86_64
NetworkManager-0.8.2-8.git20101117.fc15.x86_64


How reproducible:
One probably needs to get out of sync with i.e. RSA SecureID.
Any futher login seems to fail without giving any hint how to fix problem.
Command line tool doesn't have such problem.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Nils Philippsen 2011-06-03 11:11:24 UTC

I've run into the same issue, but only saw the "Wait for token to change" text when running vpnc with --debug=3 (didn't try 1 or 2 here, but didn't see it before using this option).

Comment 3 Fedora End Of Life 2013-04-03 14:21:50 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 Dan Williams 2013-06-25 13:38:55 UTC

This is getting worked on finally, thanks for the output Nils; now I don't have to go reproduce it with the new tokens somehow :)

*** This bug has been marked as a duplicate of bug 655882 ***