full-disclosure - Ancient Trivia: +++ath0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20040318181436.GF19675@FreiNet.de>
From: full-disclosure at FreiNet.de (Alexander Bochmann)
Subject: Ancient Trivia: +++ath0

Hi,

...on Thu, Mar 18, 2004 at 08:48:59AM -0500, Luke Scharf wrote:

 > But, still, isn't a string of characters that the modem won't transfer
 > something that the communications system on a PC should handle?

Why should it? After all, the escape sequence is 
configurable with the S2 register on Hayes comptaible 
modems, so as far as PPP is concerned, it can't know 
the current value (but it should be safe to assume it's 
been switched off by setting S2>=127 in any sane 
environment).

On the other hand, there were setups that needed 
to have the escape sequence (specifically, if the 
system didn't support the DTR line on their serial 
interface so they had to use +++ath to actively hang 
up the line).

Quite funny how much time has been wasted rediscovering 
this "feature" over and over again in the last years.

See for example 
http://groups.google.com/groups?selm=12500013%40uiucuxc.UUCP&output=gplain
where the author is perfectly aware of the escape problem.

Alex.

(do I seem to remember that some people ran into this 
trouble with uncompressed FidoNet netmail packets, too?)