From: Zack Gilburd <klasikahl@gentoo.org>
To: vapier@gentoo.org, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] lsh (and liboop) on Gentoo
Date: Tue, 16 Sep 2003 22:09:59 -0700 [thread overview]
Message-ID: <200309162210.04858.klasikahl@gentoo.org> (raw)
In-Reply-To: <200309162132.01170.vapier@gentoo.org>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 399 bytes --]
On Tuesday 16 September 2003 06:32 pm, Mike Frysinger wrote:
> with all this openssh crap thats been happening today, i was wondering if
> anyone made ebuilds for lsh (and thus liboop) for Gentoo ... i was looking
> at liboop and they use the autotools pretty poorly imho ...
AFAIK, lsh is not secure, whatsoever.
--
Zack Gilburd
http://tehunlose.com
GnuPG Key ID: A79A45668240AB6C
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-17 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 1:32 [gentoo-dev] lsh (and liboop) on Gentoo Mike Frysinger
2003-09-17 5:09 ` Zack Gilburd [this message]
2003-09-17 12:01 ` Karsten Schulz
2003-09-17 16:02 ` Zack Gilburd
2003-09-19 15:43 ` Patrick Lauer
2003-09-17 17:05 ` Alexander Gretencord
2003-09-17 20:50 ` Mike Frysinger
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=200309162210.04858.klasikahl@gentoo.org \
--to=klasikahl@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=vapier@gentoo.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox