From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: SSH 1 TO SSH 2
Date: Sat, 19 Feb 2005 15:40:15 -0700 (Mountain Standard Time) [thread overview]
Message-ID: <Pine.WNT.4.62.0502191537130.2596@merlin> (raw)
In-Reply-To: <000101c5169f$feaa6c40$6a01a8c0@canadarm>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
If you're using open ssh for serving ssh connections (most likely), then you don't need to do
anything. This server will automatically try to use ssh2, and fall back to ssh1 if your client
doesn't support the newer protocol. If you would like to disable ssh1 so that it won't be used
by the server, see the man page for sshd_config.
Marriage. (N): An arrangement which usually results in twice the amount
of arguing and half the amount of sex.
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7
And so it came to pass that on Sat, 19 Feb 2005, Rejean Proulx said
> I am trying to do something which should be easy like changing from ssh1 to
> ssh2 as TeraTerm now supports SSH 2. I am using Debian. Can't seem to find
> any docs telling me how to do this, as it is probably easy. How do I do
> this?
>
>
>
>
> Rejean Proulx
> Visit my family at http://interfree.ca
> MSN is: rejp@rogers.com
> Ham License VA3REJ
>
> Rejean Proulx
>
> Visit my family at http://interfree.ca
>
> MSN is: rejp@rogers.com
>
> Ham License VA3REJ
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3
iQA/AwUBQhfAOyenap9Jqj2wEQIAbgCgiwUqcL8bR8DvCb4+JCuf6VXyApMAoJCN
nb+qD8CAoQfsFcKyIRTd0A+K
=I4DL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Rejean Proulx
` Gregory Nowak
` Sean McMahon
` Joseph C. Lininger [this message]
` Ralph W. Reid
` Butch Bussen
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=Pine.WNT.4.62.0502191537130.2596@merlin \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).