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>] [day] [month] [year] [list]

Message-ID: <EA7C77F97CC73F4AAC856A4595DF34E205C476C5@swilnts801.wil.fusa.com>
From: Glenn_Everhart at bankone.com (Glenn_Everhart@...kone.com)
Subject: Ancient Trivia: +++ath0

The <delay>+++<delay> scheme, using time delays, was more like the old
break signal, not really like a string that would not transmit...at least
on modems that used the delay. You could sometimes kinda/sorta get
something like that to work by switching to 110 baud and sending nulls,
then switching back to whatever rate you were using, but normal
protocols that sent text would very rarely have packet boundaries just
at either end of the sequence. Also the modems let you set the break length
and the character to use in case "+++" was inconvenient for some reason. 
Certainly anything in the ASCII character set other than null would have
been ok. Don't know about null (or rubout for that matter).

-----Original Message-----
From: Luke Scharf [mailto:lscharf@....vt.edu]
Sent: Thursday, March 18, 2004 8:49 AM
To: full-disclosure@...ts.netsys.com
Subject: Re: [Full-Disclosure] Ancient Trivia: +++ath0

On Wed, 2004-03-17 at 21:30, cstone wrote:
> * = Hayes has a patent on a scheme to protect against unintentional
> triggering of the escape sequence; on their modems, you have to
> wait a specific amount of time before and after the +++ before
> issuing a command.  

Doh!  I thought that there was an easier way to escape the escape
sequence.  Too much Unix -- '\+\+\+' :-)

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

Anyway, I'm starting to get nostalgic about the old BBS days -- maybe I
should put my old one up again?  But, they just haven't the same since I
started using the WWW, and telnet BBSs just don't do it for me.

-Luke

-- 
Luke Scharf, Systems Administrator
Virginia Tech Aerospace and Ocean Engineering

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html

**********************************************************************
This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you
**********************************************************************