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  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 (
Subject: Apparently the practice was prevalent

> -----Original Message-----
> From: Martin Macok []
> Sent: 11 February 2004 12:17
> To:
> Subject: Re: [Full-Disclosure] Apparently the practice was prevalent
> In other words, "do not have open relays".
> Martin Ma?ok
I now give up. You've been unable to follow what I've written down clearly.
The "it" in my former statement referred quite clearly to RFC 821. Try
actually reading what I sent. Do I have to do everything for you? Are you
some spotty teen who has to have everything done for them? Or are you a

You've completely missed the point. RFC 821 and 822 were inadequate even
before April 2001. So most people ignored parts of them FOR GOOD REASON.
There was NO GOOD REASON for Microsoft to ignore the RFCs in this case. Like
you yourself said, there isn't an RFC for every bad idea, so even if any
relevant RFC didn't mention username:password for http and https, it would

I'm only continuing this so that the archives come to a sensible end,
although I suspect you'll troll some more. Any further responses from me
will probably contribute more heat than light.

John Airey, BSc (Jt Hons), CNA, RHCE
Internet systems support officer, ITCSD, Royal National Institute of the
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 

According to the book of Acts, Eutychus was the first man to suffer from a
General Protection Fault with Windows.


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 


Powered by blists - more mailing lists