From: Dan Foster <dsf@frontiernet.net>
To: mlan@cpu.lu
Cc: pogtal@erols.com, linuxppc-user@lists.linuxppc.org,
linuxppc-dev@lists.linuxppc.org, dsf@frontiernet.net (Dan Foster)
Subject: Re: ssh2 and multiheaded X
Date: Wed, 22 Sep 1999 02:24:30 -0400 (EDT) [thread overview]
Message-ID: <199909220624.CAA42912@frontiernet.net> (raw)
In-Reply-To: <199909220616.IAA00379@piglet.cpu.lu> from Michel Lanners at "Sep 22, 99 08:16:03 am"
Hot Diggety! On a bright and sunny day, Michel Lanners was rumored to have said.
>
> On 21 Sep, this message from Doomsday Machine echoed through cyberspace:
> >
> > Greetings all-
> > Has anyone successfully compiled ssh2 or gotten some version of
> > multiheaded X working? ssh1 is pretty useless, since any machine not
> > running linuxppc is running ssh2, not ssh1.
[...snip....]
1. ssh2 daemon has a ssh v1 compatibility mode that can be enabled.
2. there is no real intrinsic difference in running ssh v2 over v1;
v2 just has tighter licensing requirements. v1 code has been pored over
line by line after that bad scare (but later turned out to be unfound)
around 1.2.25 and a break-in of a key site.
Of course, neither helps much if a site has chosen to use v2 everywhere :-)
That said, I'm not running a recent version of LinuxPPC so I can't really
tell what exactly is broken at the moment. Sorry.
-Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~1999-09-22 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199909220616.IAA00379@piglet.cpu.lu>
1999-09-22 6:24 ` Dan Foster [this message]
1999-09-22 7:39 ` ssh2 and multiheaded X Gabriel Paubert
1999-09-22 11:09 ` Michael Schmitz
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=199909220624.CAA42912@frontiernet.net \
--to=dsf@frontiernet.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
--cc=mlan@cpu.lu \
--cc=pogtal@erols.com \
/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;
as well as URLs for NNTP newsgroup(s).