Bug 2668 - Some PAP secrets need quoting
Some PAP secrets need quoting
Status: CLOSED DUPLICATE of bug 987
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
: 4753 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 1999-05-08 15:54 EDT by danf
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-28 15:32:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description danf 1999-05-08 15:54:47 EDT
A PAP password entered with gnome-linuxconf that contains an
octothorpe '#' character appears to cause pppd to truncate
the password, causing logins to fail. '#' (and maybe other
characters) must be backslash quoted in the
/etc/ppp/pap-secrets file.
Comment 1 Bill Nottingham 1999-08-27 19:07:59 EDT
*** Bug 4753 has been marked as a duplicate of this bug. ***

I am setting up a system that uses PPP to dial out to a
server.  To dial out through the PBX at that location, you
must dial a "#" first.  This character is a comment
character to the "chat" program if it is at the beginning of
a line, but not anywhere else on the line.  However,
linuxconf cannot handle the "#" in the dial string.  If I
put it in and save the interface and then go back in to the
interface configuration screen, the dial number is empty
(like linuxconf sees "#" as a comment anywhere and tosses
it).  It looks like linuxconf does not even save the dial
number; if I go in and manually edit
/etc/sysconfig/network-scripts/chat-ppp0, it just has a line


and I have to manually put in the number to dial.  If I go
back in to linuxconf and do anything to the interface I have
to again manually put the number in.
Comment 2 Michael K. Johnson 1999-08-28 15:32:59 EDT
*** This bug has been marked as a duplicate of 987 ***

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