<?xml version="1.0"  encoding="ISO-8859-1" ?>
<rss version="2.0">
<channel>
<title>Debian-security Mailing List Threads</title>
<link>http://readlist.com</link>
<description>Debian-security Mailing List - New Threads feed</description>
<language>en</language>
<image>
  <url>http://readlist.com/readlist-logo-tiny.gif</url>
  <title>ReadList.com</title>
  <link>http://readlist.com/</link>
  <width>156</width>
  <height>30</height>
</image>
<item>
  <title>Minor improvement to openssl-blacklist</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4960.html</link>
  <pubDate>Fri, 16 May 2008 11:04:25 GMT</pubDate>
  <description>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The diff below lets one not just check the private keys - but also check the public part thereof. This is useful - as the latter can also be obtained with: 	openssl s_client -connect fqdn:443 -showcerts or be ran over a store, say the 'issued' store of a Certificate Authority. Dw *** openssl-vulnkey	2008-05-14 12:41:00.000000000 -0400 - --- ...</description>
</item>
<item>
  <title>Fault in openssl-blacklist - version 0.1 -- false negatives.</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4959.html</link>
  <pubDate>Fri, 16 May 2008 11:03:21 GMT</pubDate>
  <description>Just FYI - there seems a minor fault in the openssl-blackist tool[1], I strongly suspect that the line: #print "bits: %s\nmodulus: %s\nkey: %s\nkey80: %s" % (bits, modulus, key, key[20:]) if key[20:] in db_lines: needs to be key = sha.sha(modulus).hexdigest() #print "bits: %s\nmodulus: %s\nkey: %s\nkey80: %s" % (bits, modulus, key, key[20:]) if key in db_lines: for the ...</description>
</item>
<item>
  <title>Thanks to Debian OpenSSL developers</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4947.html</link>
  <pubDate>Thu, 15 May 2008 20:15:39 GMT</pubDate>
  <description>Hi list, I want to say: Thank you! Why? The Debian developers seems the only developers, who investigated the openssl code and not just used it. They found a strange thing in the OpenSSL Code, asked the OpenSSL people and after all, they removed the potentielly dangerous code peace. OK, this time, it was a mistake, but who but them have not just used he code for theire packages? In Germany we say: "Wer nichts ...</description>
</item>
<item>
  <title>pr1</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4946.html</link>
  <pubDate>Thu, 15 May 2008 19:49:46 GMT</pubDate>
  <description>-- lpct http://www.linuxiso.cl -- To UNSUBSCRIBE, email to debian-security-REQUEST with a subject of "unsubscribe". Trouble? Contact listmaster ...</description>
</item>
<item>
  <title>Re: blacklist.RSA-1024 missing?</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4940.html</link>
  <pubDate>Thu, 15 May 2008 17:39:08 GMT</pubDate>
  <description>I was able to find blacklist.RSA-1024 in Ubuntu's openssl-blacklist package, and (fortunately) found that my 1024-bit RSA keys are in fact not blacklisted. -- http://www.doorstop.net/ ...</description>
</item>
<item>
  <title>openssh: working exploit on bugtraq</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4938.html</link>
  <pubDate>Thu, 15 May 2008 15:38:39 GMT</pubDate>
  <description>http://www.securityfocus.com/archive/1/492112/30/0/threaded -- To UNSUBSCRIBE, email to debian-security-REQUEST with a subject of "unsubscribe". Trouble? Contact listmaster ...</description>
</item>
<item>
  <title>DSA-1571 and GSSAPI</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4935.html</link>
  <pubDate>Thu, 15 May 2008 13:31:36 GMT</pubDate>
  <description>Hi all! I was wondering how bad this actually is and it looks extremely horrible. In practice, all data transmitter over the wire for the last two years and be snooped upon (if someone has captured it - and the paranoid must assume someone has). Trusting on the security of ssh, we have, for example, used ssh to transmit data from server to server, including such sensitive information as Heimdal database master key... Am I ...</description>
</item>
<item>
  <title>ssh-vulnkey and authorized_keys</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4932.html</link>
  <pubDate>Thu, 15 May 2008 07:52:50 GMT</pubDate>
  <description>Hello all, thanks for the quick response to the SSL bug and for providing ssh-vulnkey and dokuwd.pl. SSH-VULNKEY produces funny output when processing authorized_keys with additional options like from="host", command="something to do", no-agent-forwarding, etc... Instead of the file name it prints these extra options. It is hard to find such files then, especialy if they are not in regular user homes but used for ...</description>
</item>
<item>
  <title>Re: [SECURITY] [DSA 1571-1] vulnerability of past SSH/SSL sessions</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4921.html</link>
  <pubDate>Wed, 14 May 2008 23:36:29 GMT</pubDate>
  <description>&gt; Affected keys include SSH keys [...] and session keys used &gt; in SSL/TLS connections. It seems that people are insisting quite a lot on the bad keys, but what worry me a lot more is that, apparently and very logically, past ssh connections and any SSL session keys are to be considered compromised. In other words, if a vulnerable key have been involved, and if someone was able to intercept and save the encrypted ...</description>
</item>
<item>
  <title>DSA/DSS keys and DSA 1576-1/CVE-2008-0166.</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4918.html</link>
  <pubDate>Wed, 14 May 2008 22:41:48 GMT</pubDate>
  <description>There seems to be some confusion going around about the effect of the openssl issue on dsa keys. &gt;From what I understand, when using a DSA key and the random number used to generate a signature is known, predictable, or used twice the private key can be calculated. So it seem to me that if a DSA key was ever used on a system which had that openssl version and openssl was used to generate that random number, you have to revoke ...</description>
</item>
<item>
  <title>openssl/openssh fixes for lenny (testing)</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4916.html</link>
  <pubDate>Wed, 14 May 2008 18:02:19 GMT</pubDate>
  <description>Are there any plans to issue the same openssl/openssh security fixes for lenny has have been done for etch? -- Dr. Harry Edmon			E-MAIL: harry 206-543-0547				harry Dept of Atmospheric Sciences		FAX:	206-543-0308 University of Washington, Box 351640, Seattle, WA 98195-1640 -- To UNSUBSCRIBE, email to debian-security-REQUEST with a subject of "unsubscribe". Trouble? Contact listmaster ...</description>
</item>
<item>
  <title>openssl / x509 certs</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4913.html</link>
  <pubDate>Wed, 14 May 2008 17:11:19 GMT</pubDate>
  <description>How can I check if a rsa key created by 'openssl genrsa ...' and its x509 certificate is vulnerable ? The utility ssh-vulnkey seems to only check ssh keys. Thanks in advance ! Cheers, Philip ------------------------------------------ System Engineer Unix B | SOURCE Phone +41 44 712 65 14 Mobile +41 79 412 36 40 (for urgent cases) ------------------------------------------ -- To ...</description>
</item>
<item>
  <title>leakage of keys?</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4911.html</link>
  <pubDate>Wed, 14 May 2008 14:17:56 GMT</pubDate>
  <description>Hallo, http://wiki.debian.org/SSLkeys says | Additionally, some DSA keys may be compromised in the following situations: ... | * key generated with good openssl and used to ssh from a machine with bad ssl = bad Are really only DSA keys affected (i.e., RSA key generated with good openssl and used to ssh from a machine with bad ssl = good)? Does this affect other protocols? ssl/ipsec/openvpn (with certificates) ...</description>
</item>
<item>
  <title>dowkd.pl - how the blacklist data is generated ?</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4910.html</link>
  <pubDate>Wed, 14 May 2008 12:27:45 GMT</pubDate>
  <description>Hi, For my understanding, the black list in the dowkd.pl is generated from the potential remaining entropy source which seems to be only the PID value added in the pool. Could we have some false negative[1] when running the dowkd script ? and would it possible to have the source code of the "black list generator" application (especially to see the endianness effect on some arch) ? Thanks a lot for any info, ...</description>
</item>
<item>
  <title>Re: [SECURITY] [DSA 1576-1] New openssh packages fix predictable randomness</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4902.html</link>
  <pubDate>Wed, 14 May 2008 10:13:28 GMT</pubDate>
  <description>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Florian Weimer wrote: | ------------------------------------------------------------------------ | Debian Security Advisory DSA-1576-1 security | http://www.debian.org/security/ Florian Weimer | May 14, 2008 http://www.debian.org/security/faq | ...</description>
</item>
<item>
  <title>dowkd.pl via Package</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4895.html</link>
  <pubDate>Wed, 14 May 2008 03:06:33 GMT</pubDate>
  <description>Hi, Is there any plan to provide dowkd.pl via Debian Package? I'm worried about that modified dowkd.pl, by malicious attacker, would be spread out. -- Hideki Yamane -- To UNSUBSCRIBE, email to debian-security-REQUEST with a subject of "unsubscribe". Trouble? Contact listmaster ...</description>
</item>
<item>
  <title>CHAO BAN</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4890.html</link>
  <pubDate>Tue, 13 May 2008 23:51:37 GMT</pubDate>
  <description>MOI BAN VAO XEM WEBSITE HAY www.thongtri.com -- To UNSUBSCRIBE, email to debian-security-REQUEST with a subject of "unsubscribe". Trouble? Contact listmaster ...</description>
</item>
<item>
  <title>Re: [SECURITY] [DSA 1571-1] New openssl packages fix predictable random number generator</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4857.html</link>
  <pubDate>Tue, 13 May 2008 13:36:59 GMT</pubDate>
  <description>On Tue, May 13, 2008 at 02:06:39PM +0200, Florian Weimer wrote: &gt; &lt;http://security.debian.org/project/extra/dowkd/dowkd.pl.gz.asc&gt; &gt; (OpenPGP signature) This URL 404s (but the tool URL doesn't... possibly encouraging bad practice in running unverified code) &gt; Instructions how to implement key rollover for various packages will be &gt; published at: &gt; &gt; ...</description>
</item>
<item>
  <title>Broken link on Debian CVE Web page (Was: [SECURITY] [DSA 1571-1] New openssl packages fix predictabl</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4856.html</link>
  <pubDate>Tue, 13 May 2008 13:32:38 GMT</pubDate>
  <description>On Tue, May 13, 2008 at 02:06:39PM +0200, Florian Weimer &lt;fw&gt; wrote a message of 274 lines which said: &gt; This is caused by an incorrect Debian-specific change to the openssl &gt; package (CVE-2008-0166). By the way, the page &lt;http://www.debian.org/security/cve-compatibility&gt; has a link http://security-tracker.debian.org/, labeled "The Debian Security Tracker has the canonical list of CVE names, ...</description>
</item>
<item>
  <title>Re: [SECURITY] [DSA 1571-1] New openssl packages fix predictablerandom number generator</title>
  <link>http://readlist.com/lists/lists.debian.org/debian-security/0/4855.html</link>
  <pubDate>Tue, 13 May 2008 13:28:04 GMT</pubDate>
  <description>On Tue, May 13, 2008 at 02:06:39PM +0200, Florian Weimer wrote: &gt; A detector for known weak key material will be published at: &gt; &gt; &lt;http://security.debian.org/project/extra/dowkd/dowkd.pl.gz&gt; &gt; &lt;http://security.debian.org/project/extra/dowkd/dowkd.pl.gz.asc&gt; &gt; (OpenPGP signature) On stable I get "close is not a valid DB_File macro at /home/pkern/dowkd.pl line 51". Kind regards, ...</description>
</item>
</channel>
</rss>
