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: <1078083870.12474.5.camel@anduril.intranet.cartel-securite.net>
From: blancher at cartel-securite.fr (Cedric Blancher)
Subject: secure downloading of patches (Re: Knocking
	Microsoft)

Le dim 29/02/2004 ? 17:57, Martin Ma?ok a ?crit :
> You are true that PGP is a stronger protection from this point of view
> but keep in mind that neither SSL nor PGP can protect us in the case
> of the compromised end point -- the server or developper's workstation
> in the case of SSL/TLS and the developper's workstation in the case of
> PGP.

Developper's private key compromission is quite unlikely to happen,
although it is clearly possible, especially if we think to Valve case
(code source steal through developper station compromise).

> From the other point of view, only SSL/TLS can protect you against the
> attacks on the transfer itself. For example, the attacker can poison
> your DNS cache and trick you into connecting to the site that does not
> provide the patch (so you stay vulnerable).

True, this is definitly a good point I didn't think of.

-- 
http://www.netexit.com/~sid/
PGP KeyID: 157E98EE FingerPrint: FA62226DA9E72FA8AECAA240008B480E157E98EE
>> Hi! I'm your friendly neighbourhood signature virus.
>> Copy me to your signature file and help me spread!


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ