Bug 127259 - RFE: Prompt for password on PPP connections
Summary: RFE: Prompt for password on PPP connections
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: rcn-modem
TreeView+ depends on / blocked
 
Reported: 2004-07-05 11:27 UTC by Leon Stringer
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-11-13 11:33:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Leon Stringer 2004-07-05 11:27:07 UTC
From Bugzilla Helper:
User-Agent: 

Description of problem:
Could there be an option which prompts for a password when PPP or
other dial-up (or ISDN) network devices are activated?

This is as opposed to having the password stored.

My organization (and presumably others) uses a rotating password (like
and RSA security token) so I have to type a new password for every
connection, this is quite cumbersome with the current interface.

Obviously, this should be optional, if your password is static you
don't want to get this prompt.

I'm not sure whether this belongs in system-config-network or
system-control-network. I think the latter but as that isn't in
Bugzilla I'm listing it here.

It would be extra useful if this integrated with the Modem Lights
GNOME utility, a change to /sbin/ifup may allow the RedHat GUI to fit
in with this.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
(Enhancement)

Additional info:

Comment 1 Matthew Miller 2005-04-26 15:16:13 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.


Note You need to log in before you can comment on or make changes to this bug.