From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Linux Sisyphus mailing list <sisyphus@lists.altlinux.org>
Subject: Re: [sisyphus] Security of openssh
Date: Fri, 16 May 2008 03:09:05 +0400
Message-ID: <20080515230905.GD5999@wo.int.altlinux.org> (raw)
In-Reply-To: <200805151759.43334.iadzhubey@rics.bwh.harvard.edu>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
On Thu, May 15, 2008 at 05:59:43PM -0400, Ivan Adzhubey wrote:
> On Thursday 15 May 2008 05:39:13 pm Dmitry V. Levin wrote:
> > On Thu, May 15, 2008 at 03:05:24PM -0400, Ivan Adzhubey wrote:
> > > On Thursday 15 May 2008 07:27:09 am Dmitry V. Levin wrote:
> > > > Hi,
> > > >
> > > > On Thu, May 15, 2008 at 04:01:04AM -0400, Ivan Adzhubey wrote:
> > > > > А что у нас с openssh? Он не подвержен этому багу с генерацией
> > > > > уязвимых ключей?
> > > >
> > > > Если я вам отвечу, что он не подвержен этому багу, вы мне поверите?
> > >
> > > Да, конечно. Это собственно то, что я и хотел услышать в ответ на свой
> > > вопрос.
> >
> > А вот я бы на вашем месте не поверил, а пошёл проверять. :)
>
> Я и проверил:
>
> # rpm -qi openssh|fgrep Packager
Ну всё же openssh тут всего-навсего один из пострадавших
(см. http://wiki.debian.org/SSLkeys), проверять нужно openssl/libssl*.
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-15 23:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 8:01 Ivan Adzhubey
2008-05-15 8:04 ` Andrey Rahmatullin
2008-05-15 8:14 ` Ivan Adzhubey
2008-05-15 8:17 ` Led
2008-05-15 19:02 ` Ivan Adzhubey
2008-05-15 11:27 ` Dmitry V. Levin
2008-05-15 11:40 ` Michael Shigorin
2008-05-15 19:05 ` Ivan Adzhubey
2008-05-15 21:39 ` Dmitry V. Levin
2008-05-15 21:59 ` Ivan Adzhubey
2008-05-15 23:09 ` Dmitry V. Levin [this message]
2008-05-26 18:16 ` Dmitry V. Levin
2008-05-27 18:37 ` Michael Shigorin
2008-05-27 19:39 ` Dmitry V. Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080515230905.GD5999@wo.int.altlinux.org \
--to=ldv@altlinux.org \
--cc=sisyphus@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Sisyphus discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
public-inbox-index sisyphus
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git