At 10:37 PM +0100 3/6/00, Christian Weisgerber wrote:
William Woods [EMAIL PROTECTED] wrote:
How do we update it, ie, when a updated version comes out.
OpenSSH doesn't really have releases. The upstream version is
straight out of the OpenBSD repository. I assume several of our
developers
On Mon, 6 Mar 2000, Garance A Drosihn wrote:
Out of the OpenBSD repository, or out of the OpenSSH project?
Both are the same thing.
Note that www.openssh.COM currently says:
*NEW* OpenSSH 1.2.3 released March 6, 2000
which sounds a lot like a new release to me...
They
Second, how does one specify options on the command line? In ssh
1.2.x, I say ssh -o ForwardX11=yes, but that doesn't work in OpenSSH.
Bug or feature?
Browsing the source, it looks like "ssh -o 'ForwardX11 yes'" should
work. Both ssh and openssh define -o as:
-o 'option'
Thanks Bill. I forgot that old versions of ssh were this picky...
OpenSSH inherited this from the 1.2.12 version it started from.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, Mar 06, 2000 at 02:20:35AM -0700, Warner Losh wrote:
: OpenSSH inherited this from the 1.2.12 version it started from.
On a side note: last week, Tatu Ylonen, principal author of SSH, posted a
message on the SSH mailing-list (in the thread about the new SSH2 license)
saying that:
Warner Losh wrote:
First, how does one enable TIS/SKEY authorization for ssh? It appears
that the frst step would be to add -DSKEY to the Makefile conditional
on something. Are there other steps?
Yes, there are other steps. openssh depends upon functions in the
openbsd libskey that we
On Mon, Mar 06, 2000 at 11:29:39AM +0100, Edwin Kremer wrote:
" I do not recommend use of OpenSSH (or SSH1 generally, for that matter).
There hasn't been much followup on this. Anybody here who cares to
comment on this? What issues are relevant here and how bad is it?
I'm sure he'd much
Bill Fumerola wrote:
On Mon, Mar 06, 2000 at 11:29:39AM +0100, Edwin Kremer wrote:
" I do not recommend use of OpenSSH (or SSH1 generally, for that matter)
.
There hasn't been much followup on this. Anybody here who cares to
comment on this? What issues are relevant here and
At 11:29 AM +0100 3/6/00, Edwin Kremer wrote:
On a side note: last week, Tatu Ylonen, principal author of SSH, posted a
message on the SSH mailing-list (in the thread about the new SSH2 license)
saying that:
" OpenSSH is based on my version from back in 1995 or 1996. The
" OpenSSH folks
Now that openssh is in the base system, I assume it will no longer be in the
ports. How do we update it, ie, when a updated version comes out. I would
rather not make world just to update that.
--
E-Mail: [EMAIL PROTECTED]
Date: 06-Mar-00
Time: 11:22:26l
On 6 Mar 2000, Christian Weisgerber wrote:
Now that openssh is in the base system, I assume it will no longer
be in the ports.
I expect the port to be maintained for the remaining lifetime of
the 3.x branch. This is of no concern to 4.x users, of course.
Correct. We should probably mark
On Mon, Mar 06, 2000 at 11:23:45AM -0800, William Woods wrote:
Now that openssh is in the base system, I assume it will no longer be in the
ports. How do we update it, ie, when a updated version comes out. I would
rather not make world just to update that.
# cvsup standard-supfile (until 4.0
Actually two.
First, how does one enable TIS/SKEY authorization for ssh? It appears
that the frst step would be to add -DSKEY to the Makefile conditional
on something. Are there other steps?
Second, how does one specify options on the command line? In ssh
1.2.x, I say ssh -o
13 matches
Mail list logo
