full-disclosure - HTTP AUTH BASIC monowall.

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: <4418673A.1030009@snosoft.com>
Date: Wed Mar 15 19:13:14 2006
From: simon at snosoft.com (Simon Smith)
Subject: HTTP AUTH BASIC monowall.

Actually,
    You are trusting the user to do the right thing. Historically, users
don't always do the right thing. Hence, why I want a technology to
protect data and not a human being.

Tim wrote:
>> (assuming the admin doesn't notice the cert changes and all that good
>> stuff.) 
>>     
>
>
> There's your problem.  If you assume this, you will always be vulnerable
> to MitM if the software you're using allows you to communicate anyway.
>
> If you're SSH client lets you connect to systems whose keys have
> changed, same problem.  If your VPN client allows it, same problem.
>
> This is why I wanted you to think about what you are trusting in the
> first place.  You are trusting your CA and the certificate chain.  If
> you can't do that, then you have no trust.
>
> tim
>   


-- 


Regards, 
	Adriel T. Desautels
	Harvard Security Group
	http://www.harvardsecuritygroup.com