Bug 514 – ESCAPECHARS effectively always on

Bug 514 - ESCAPECHARS effectively always on

Summary:	ESCAPECHARS effectively always on

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	initscripts (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1998-12-18 07:29 EST by Göran Uddeborg
Modified:	2014-03-16 22:08 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-01-25 08:51:41 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Göran Uddeborg 1998-12-18 07:29:07 EST

In ifup-ppp, if ESCAPECHARS is "yes", the flag "asyncmap
FFFFFFF" is added to the options to pppd.  All characters
will be escaped.  So far so good.  If it is not "yes" no
flag is added, no flag is added.  According to the manual
page for pppd "If no asyncmap option is given, no async
character map will be negotiated for the receive direction;
the peer should then escape all control characters."  Which
means all charactars will STILL be escaped.

It appears to me the correct thing to do in ifup-ppp would
be to add "asyncmap 0" if ESCAPECHARS is "no".

Comment 1 David Lawrence 1998-12-18 16:27:59 EST

This has been assigned to a developer as a change request.

Comment 2 Jeff Johnson 1999-01-25 08:51:59 EST

Fixed in initscripts 3.83.

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