full-disclosure - Apparently the practice was prevalent

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

From: John.Airey at rnib.org.uk (John.Airey@...b.org.uk)
Subject: Apparently the practice was prevalent

>-----Original Message-----
>From: Martin Macok
>To: full-disclosure@...ts.netsys.com
>Sent: 10/02/04 17:43
>Subject: Re: [Full-Disclosure] Apparently the practice was prevalent
>
>On Tue, Feb 10, 2004 at 11:23:55AM -0000, John.Airey@...b.org.uk wrote:
>>
>> Regardless of what you think of these 'ancient' RFCs, you must bear
>> in mind that an even more 'ancient' RFC determines the format of the
>> email you are reading, RFC 822. It's worth pointing out that anyone
>> who does not have an "open" email relay is in breach of this RFC

>Not true.

At the risk of descending into a playground argument, 'tis true. Sections
4.3.2, 6.2.2 and 6.2.6 imply that you have an open relay. In fact, RFC 2822
which obsoletes RFC 822 doesn't even mention relays. Remember that RFC 822
was written before spam was something other than the subject of an ironic
Monty Python sketch. I haven't even mentioned 'ancient' ethernet which is
getting on for 25 years old. Is there any RFC that specifies that open
relays are a bad idea? I can't find one.

Anyway, if we all wish to ignore RFCs and do our own thing, we might as well
abandon inter-operation now and go back to closed protocols.

(no sig with Outlook Web Access. Bah...)
- 
DISCLAIMER: 

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged. If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system. 

RNIB endeavours to ensure that emails and any attachments generated by 
its staff are free from viruses or other contaminants. However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments. 

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent 
those of RNIB. 

RNIB Registered Charity Number: 226227 

Website: http://www.rnib.org.uk