Everyone,
I am looking into setting up a webserver to hold some very sensitive
information. I am trying to figure out which is more secure, forcing
any web connections to be done using an ssh tunnel or forcing ssl.
I have not been able to figure out if one is definitively much more
secure
.
Thanks in advance
Mark Moellering
I don't think there is any extra security in tunneling an HTTP
connection over SSH. Use authentication is a different matter, but the
encryption algorithms are the same. Most web servers have an option of
configuring what ciphers are allowed (same as OpenSSH
On 5/3/11 10:22 AM, Mark Moellering wrote:
Everyone,
I am looking into setting up a webserver to hold some very sensitive
information. I am trying to figure out which is more secure, forcing any
web connections to be done using an ssh tunnel or forcing ssl.
I have not been able to figure out
On Tue, May 03, 2011, Mark Moellering wrote:
Everyone,
I am looking into setting up a webserver to hold some very sensitive
information. I am trying to figure out which is more secure, forcing
any web connections to be done using an ssh tunnel or forcing ssl.
I have not been able to
On 17 March 2011 11:52, Robert Huff roberth...@rcn.com wrote:
Carmel writes:
It is part of the base system. I don't know if it has a true
maintainer. In any case, I would need commit privileges which I
don't and never expect to have and have no desire to acquire..
I do not
of FreeBSD?
Currently, no-- TRUNK has:
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/crypto/openssh/version.h
Revision 1.41: download - view: text, markup, annotated - select for
diffs Thu Nov 11 11:46:19 2010 UTC (4 months ago) by des
Branches: MAIN
CVS tags: HEAD
Diff
On Thu, 17 Mar 2011 10:46:44 +
krad kra...@gmail.com articulated:
[snip]
a combination of time and limited resources I guess. If it bugs you
that much why dont you volunteer yourself to maintain it, i'm sure
that if you dont feel competent enough at present, people will help
and mentor
Carmel writes:
It is part of the base system. I don't know if it has a true
maintainer. In any case, I would need commit privileges which I
don't and never expect to have and have no desire to acquire..
I do not believe that is correct; a fair number of people
contribute
I was just wondering about the version of SSH used on FreeBSD.
According to the OpenSSH page:
OpenSSH 5.8/5.8p1 released February 4, 2011 [contains security fix]
Now, according to my system, FreeBSD-8.2, I have this version:
OpenSSH_5.4p1 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010
# openssl
On 16/03/2011 13:38, Carmel wrote:
I was just wondering about the version of SSH used on FreeBSD.
According to the OpenSSH page:
OpenSSH 5.8/5.8p1 released February 4, 2011 [contains security fix]
Now, according to my system, FreeBSD-8.2, I have this version:
OpenSSH_5.4p1 FreeBSD
On Wed, 16 Mar 2011 14:35:09 +
Matthew Seaman m.sea...@infracaninophile.co.uk articulated:
On 16/03/2011 13:38, Carmel wrote:
I was just wondering about the version of SSH used on FreeBSD.
According to the OpenSSH page:
OpenSSH 5.8/5.8p1 released February 4, 2011 [contains
On Mar 16, 2011, at 11:24 AM, Carmel wrote:
OK, then does that mean that the latest version will be used in the
still not released 9 version of FreeBSD?
Currently, no-- TRUNK has:
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/crypto/openssh/version.h
Revision 1.41: download - view
/cgi/cvsweb.cgi/~checkout~/src/crypto/openssh/version.h
Revision 1.41: download - view: text, markup, annotated - select for
diffs Thu Nov 11 11:46:19 2010 UTC (4 months ago) by des
Branches: MAIN
CVS tags: HEAD
Diff to: previous 1.40: preferred, colored
Changes since revision 1.40: +3 -3 lines
On Sun, Feb 6, 2011 at 5:42 AM, Bill Moran wmo...@potentialtech.com wrote:
Also, I'm having trouble understanding how people like that get grants
to do work like that. On the one hand, they obviously know enough about
cryptography to make improvements. On the other hand, they can't seem
to
On Mon, 7 Feb 2011 11:12:45 -0800
David Brodbeck g...@gull.us articulated:
On Sun, Feb 6, 2011 at 5:42 AM, Bill Moran wmo...@potentialtech.com
wrote:
Also, I'm having trouble understanding how people like that get
grants to do work like that. On the one hand, they obviously know
enough
https://www.psc.edu/networking/projects/hpn-ssh/hpn-v-ssh-tput.jpg
SCP and the underlying SSH2 protocol implementation in OpenSSH is network
performance limited by statically defined internal flow control buffers. These
buffers often end up acting as a bottleneck for network throughput of SCP
In response to kellyremo kellyr...@zoho.com:
https://www.psc.edu/networking/projects/hpn-ssh/hpn-v-ssh-tput.jpg
SCP and the underlying SSH2 protocol implementation in OpenSSH is network
performance limited by statically defined internal flow control buffers.
These buffers often end up
discussing OpenSSH rather than OpenSSL. Am I mistaken?
They are not the same project.
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
pgpYQp3xqsNOx.pgp
Description: PGP signature
I didn't get any reply from ports@,
so maybe somebody here can help
- Forwarded message from Anton Shterenlikht me...@bristol.ac.uk -
maybe this has been discussed already, my apologies in that case.
on current r203046 I'm trying to rebuild openssh-portable-5.2.p1_2,1
due to an upgrade
...@bristol.ac.uk -
maybe this has been discussed already, my apologies in that case.
on current r203046 I'm trying to rebuild openssh-portable-5.2.p1_2,1
due to an upgrade from libutil.so.8 to libutil.so.9
I get this error on sparc64 and ia64 (don't have any other arch to check):
=== Building
discussed already, my apologies in that case.
on current r203046 I'm trying to rebuild openssh-portable-5.2.p1_2,1
due to an upgrade from libutil.so.8 to libutil.so.9
I get this error on sparc64 and ia64 (don't have any other arch to check):
=== Building for openssh-portable-5.2.p1_2,1
cc
I noticed on the FreeBSD 8.0 page that OpenSSH is being updated from
4.5p1 to 5.1p1. [MERGED]; however, according to the OpenSSH page, the
present version is OpenSSH 5.2/5.2p1 released February 23, 2009.
I was just wondering why the FreeBSD team decided not to go with the
latest stable version
I have the following version of SSH installed:
OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.7e-p1 25 Oct 2004
I noticed an article regarding a flaw in OpenSSH below version 5.2. The
article is here: http://news.zdnet.com/2100-9595_22-303182.html
Is this anything to worry about? Does the FreeBSD
Jerry wrote:
I have the following version of SSH installed:
OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.7e-p1 25 Oct 2004
I noticed an article regarding a flaw in OpenSSH below version 5.2. The
article is here: http://news.zdnet.com/2100-9595_22-303182.html
Is this anything to worry about
Hi.
I trying to setup ssh+pam_krb5 for authentication and establishment of
credential cache on FreeBSD 6.3 against MIT kerberos. Everything is ok with
authentication, but not with establishment of credential cache by pam_krb5.
I tried different combinations of modules in /etc/pam.d/sshd
Hi,
Is there a way to just upgrade base openssh without breaking a lot of
things? I have an old 5.4 stable box, and I would like to get openssh
up to date, since it is running sshd service, and it is not possible
to allow it only from defined ips.
Or I just have to eat it and upgrade the whole
On Tuesday 11 November 2008 13:38:11 Matiss wrote:
Hi,
Is there a way to just upgrade base openssh without breaking a lot of
things? I have an old 5.4 stable box, and I would like to get openssh
up to date, since it is running sshd service, and it is not possible
to allow it only from defined
Christopher Key wrote:
Hello,
I've come upon OpenSSH bug 472, whereby scp refuses usernames
containing a '#' character, dieing with 'invalid user name'. Both
rsync and ssh accept such usernames, and after looking at
/usr/src/crypto/openssh/scp.c, it would appear that scp also allows
Hello,
I've come upon OpenSSH bug 472, whereby scp refuses usernames containing
a '#' character, dieing with 'invalid user name'. Both rsync and ssh
accept such usernames, and after looking at
/usr/src/crypto/openssh/scp.c, it would appear that scp also allows such
usernames for the source
Hi,
I've just updated my sources for 6.2-RELEASE. It took me from p11 to
p12. The changes were quite minor. Only changes were to UPDATING
(obviously), channels.c in the openssh directory and a newvers.sh file
in /usr/src/conf. So, instead of rebuilding world, since the UPDATING
notes say
On Thursday 25 September 2008 17:33:56 Andrew Falanga wrote:
Hi,
I've just updated my sources for 6.2-RELEASE. It took me from p11 to
p12. The changes were quite minor. Only changes were to UPDATING
(obviously), channels.c in the openssh directory and a newvers.sh file
in /usr/src/conf
in the openssh directory and a newvers.sh file
in /usr/src/conf. So, instead of rebuilding world, since the UPDATING
notes say that the changes only affect sshd, I'm following the
instructions in the handbook for section, 23.4.14.1. Do I need to
re-make the world for every change
quite minor. Only changes were to UPDATING
(obviously), channels.c in the openssh directory and a newvers.sh file
in /usr/src/conf. So, instead of rebuilding world, since the UPDATING
notes say that the changes only affect sshd, I'm following the
instructions in the handbook for section
Bad choice of words on my part. It won't rebuild openssl, if you still
have /usr/obj/usr/src/* from last time. But it will go through the motions to
see if stuff needs to be rebuilt. It will only rebuild libssh and anything
that uses libssh:
# find . -name 'Makefile' -exec grep channels.c {}
Hi,
I'm experiencing an issue related to the terminal capabilities and OpenSSH. I've
installed x11/rxvt-unicode port on my client and server. When I login to my server
from urxvt (running on client), I get messages related to terminal capabilities:
88
abbe [~] chateau% ssh
Valeriu Mutu [EMAIL PROTECTED] writes:
I am trying to build 'openssh-portable' from ports
(security/openssh-portable/) with the following configuration options:
PAM=on Enable pam(3) support
TCP_WRAPPERS=on Enable tcp_wrappers support
LIBEDIT=on Enable readline support
Hi all,
I am trying to build 'openssh-portable' from ports (security/openssh-portable/)
with the following configuration options:
PAM=on Enable pam(3) support
TCP_WRAPPERS=on Enable tcp_wrappers support
LIBEDIT=on Enable readline support to sftp(1)
KERBEROS=on Enable
Hi,
I'm setting up a 'chrooted' SFTP only set of users:
/etc/make.conf:
.if ${.CURDIR:M*/usr/ports/security/openssh-portable*}
WITH_SUID_SSH =yes
WITH_OPENSSH_CHROOT =yes
WITH_HPN =yes
WITH_OVERWRITE_BASE =yes
.endif
/etc/rc.conf:
sshd_enable=NO
openssh_enable
On Tue, Mar 11, 2008 at 06:08:44PM -0400, Philip M. Gollucci wrote:
Hi,
I'm setting up a 'chrooted' SFTP only set of users:
/etc/make.conf:
.if ${.CURDIR:M*/usr/ports/security/openssh-portable*}
WITH_SUID_SSH =yes
WITH_OPENSSH_CHROOT =yes
WITH_HPN =yes
Feb 2007
debug1: Remote protocol version 1.99, remote software version
OpenSSH_4.7p1-hpn12v20 FreeBSD-openssh-portable-overwrite-base-4.7.p1_1,1
debug1: match: OpenSSH_4.7p1-hpn12v20
FreeBSD-openssh-portable-overwrite-base-4.7.p1_1,1 pat OpenSSH*
debug2: channel 0: open confirm rwindow 0 rmax
-openssh-portable-overwrite-base-4.7.p1_1,1
debug1: match: OpenSSH_4.7p1-hpn12v20
FreeBSD-openssh-portable-overwrite-base-4.7.p1_1,1 pat OpenSSH*
debug2: channel 0: open confirm rwindow 0 rmax 32768
Request for subsystem 'sftp' failed on channel 0
Xt error: Can't open display:
xterm: DISPLAY is not set
[access1 ~]$ echo $DISPLAY
[access1 ~]$
X11Forwarding yes is in place on /etc/ssh/sshd_config and
/usr/local/etc/ssh/sshd_config
access1# pkg_info | grep openssh
openssh-portable-4.6.p1,1 The portable version of OpenBSD's OpenSSH
On Tue, Jul 31, 2007, Noah wrote:
Hi there,
$ ssh -X [EMAIL PROTECTED]
Try ``ssh -Y [EMAIL PROTECTED]''
...
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
FAX:(206) 232-9186 Mercer Island,
Hi all,
I'm using security/openssh-portable to provide chroot-ssh, but would now also
like to enable PAM for SSH so that I can take advantage of OPIE in certain
scenarios.
I've compiled openssh-portable with the PAM option (and something PAM-related
flashes by during 'configure'), and have
Hello all,
I recently installed the port openssh-portable. Since then I receive the
following when attempting to ssh into the box:
Permission denied (publickey).
I believe that I am getting this because sshd is attempting to use public
key authentication, but I don't want to use
Hello all,
I recently installed the port openssh-portable. Since then I receive the
following when attempting to ssh into the box:
Permission denied (publickey).
I believe that I am getting this because sshd is attempting to use public
key authentication, but I don't want to use
On 3/20/07, Jeffrey Meyer [EMAIL PROTECTED] wrote:
Hello all,
I recently installed the port openssh-portable. Since then I receive the
following when attempting to ssh into the box:
Permission denied (publickey).
I believe that I am getting this because sshd is attempting to use public
key
Hi,
I am having a big problem with the OpenSSH Daemon on my server. Whenever I
am connected to the server and the connection is idle for a few seconds it
gets disconnected. It's almost impossible to work from remote on the server
when the connection is always getting dropped. The server
On Sun, Mar 11, 2007, Alexander Schlichting wrote:
Hi,
I am having a big problem with the OpenSSH Daemon on my server. Whenever I
am connected to the server and the connection is idle for a few seconds it
gets disconnected. It's almost impossible to work from remote on the server.
It's
On Sunday 11 March 2007 09:52, Alexander Schlichting wrote:
I am having a big problem with the OpenSSH Daemon on my server. Whenever I
am connected to the server and the connection is idle for a few seconds it
gets disconnected. It's almost impossible to work from remote on the server
when
On 17/12/06 Eric said:
why not install the portable version? its much newer than the one you have.
I don't know what you mean by the portable version.
Can I assume that the answer to my original question then, is no?
Mike
--
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make
/security/openssh-portable/
Much newer, more secure, and fun for the whole family.
--
Jay Chandler
Network Administrator, Chapman University
714.628.7249 / [EMAIL PROTECTED]
Today's Excuse: Forced to support NT servers; sysadmins quit.
___
freebsd-questions
question! =)
openssh-portable is what i am speaking of.
the port is at /usr/ports/security/openssh-portable
current version is at 4.5 whereas yours was 1-2 major versions behind that.
check it out. once its installed, add this to /etc/rc.conf
sshd_enable=NO
openssh_enable=YES
that way the built
Michael P. Soulier wrote:
So, portaudit keeps complaining about openssh, but when I try to upgrade...
[EMAIL PROTECTED] ~]$ sudo portupgrade -R openssh
[Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 207 packages
found (-1 +1) (...). done]
--- Upgrading 'openssh-3.6.1_5' to 'openssh
So, portaudit keeps complaining about openssh, but when I try to upgrade...
[EMAIL PROTECTED] ~]$ sudo portupgrade -R openssh
[Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 207 packages
found (-1 +1) (...). done]
--- Upgrading 'openssh-3.6.1_5' to 'openssh-3.6.1_6' (security/openssh
On Sat, Dec 16, 2006 at 10:47:39PM -0500, Michael P. Soulier wrote:
So, portaudit keeps complaining about openssh, but when I try to upgrade...
[EMAIL PROTECTED] ~]$ sudo portupgrade -R openssh
[Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 207 packages
found (-1 +1) (...). done
Hi there,
If I want to use the openssh from ports to replace the one from the base,
after building and installing it, so I need to do anything special in rc.conf
to specify that I'd like that one run instead of sshd from the base?
Thanks,
Mike
--
Michael P. Soulier [EMAIL PROTECTED]
Any
Michael P. Soulier wrote:
Hi there,
If I want to use the openssh from ports to replace the one from the base,
after building and installing it, so I need to do anything special in rc.conf
to specify that I'd like that one run instead of sshd from the base?
Thanks,
Mike
Hi. From /usr/ports
On 25/03/06 Mark Kane said:
Hi. From /usr/ports/security/openssh/pkg-message
Doh!
Thanks,
Mike
--
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction. --Albert
Sorry for double-posting, somehow I forgot to include the subject
line.
Hi there,
If I want to use the openssh from ports to replace the one from
the base,
after building and installing it, so I need to do anything
special in rc.conf
to specify that I'd like that one run instead of sshd
On 25/03/06 Mark Kane said:
-
To enable this port, please add sshd_program=/usr/local/sbin/sshd and make
sure sshd_enable is set to YES in your /etc/rc.conf
What about the initscript? So I keep running the one from the base, and it
picks up this change, or
On 26/03/06 Bob Goodman said:
You will probably prefer to use security/openssh-portable.
That port is more recent if I understand correctly,
and is capable of replacing the base ssh automatically,
thus making it unnecessary to bug with rc.conf.
make config will list the options.
Hope
Daniel A. wrote:
So, basically, if I want the newest version of OpenSSH running on my
system, I have to not use the one shipped with 6.0-RELEASE, and
install OpenSSH from ports?
Please don't toppost.
Installing from ports you'll get version 3.6.1. Before you get paranoid,
check the changelog
On 26/02/06, Erik Nørgaard [EMAIL PROTECTED] wrote:
Daniel A. wrote:
So, basically, if I want the newest version of OpenSSH running on my
system, I have to not use the one shipped with 6.0-RELEASE, and
install OpenSSH from ports?
Please don't toppost.
Installing from ports you'll get
Hi, quick question.
How do I update the OpenSSH which ships with FreeBSD6.0-RELEASE by default?
It's just that I dont feel secure running an old version (4.2p1) of
OpenSSH when there is a newer (4.3) version available.
___
freebsd-questions@freebsd.org
On 2006-02-26 01:25, Daniel A. [EMAIL PROTECTED] wrote:
Hi, quick question.
How do I update the OpenSSH which ships with FreeBSD6.0-RELEASE by default?
It's just that I dont feel secure running an old version (4.2p1) of
OpenSSH when there is a newer (4.3) version available.
To get security
So, basically, if I want the newest version of OpenSSH running on my
system, I have to not use the one shipped with 6.0-RELEASE, and
install OpenSSH from ports?
On 2/26/06, Giorgos Keramidas [EMAIL PROTECTED] wrote:
On 2006-02-26 01:25, Daniel A. [EMAIL PROTECTED] wrote:
Hi, quick question
On 2006-02-26 03:32, Daniel A. [EMAIL PROTECTED] wrote:
So, basically, if I want the newest version of OpenSSH running on my
system, I have to not use the one shipped with 6.0-RELEASE, and
install OpenSSH from ports?
Maybe.
But do you *want* the latest version?
If the base-system version
On Sun, 19 Jun 2005, [ISO-8859-1] Björn König wrote:
Dan Mahoney, System Admin wrote:
Is freeBSD ever going to update the contributed version of openssh to
something more recent?
Yes. Currently OpenSSH 4.1p1 is part of 6-CURRENT developent branch. An
update in 5-STABLE may happen
Hi,
I'm trying to get OpenSSH with Kerberos5/GSSAPI authentication up and
running in an heterogenous environment, but having problems.
I'm running a vanilla FreeBSD-5.4p1 box as the KDC. I have another
FreeBSD-5.4 box, and a RedHat ES3 box running as a test client/server.
kinit works fine
Hey all, couple quick questions.
'
Is freeBSD ever going to update the contributed version of openssh to
something more recent? I'm particularly interested in the DNS SSHFP
support, and I'm unsure of the differences between the base version, the
one in ports, and the portable version in ports
Dan Mahoney, System Admin wrote:
Is freeBSD ever going to update the contributed version of openssh to
something more recent?
Yes. Currently OpenSSH 4.1p1 is part of 6-CURRENT developent branch. An
update in 5-STABLE may happen, but not regulary and not definitely. I
strongly believe
case.
[Tue, Mar 29, 2005 at 09:14:07AM -0500]
This one time, at band camp, Lowell Gilbert said:
Redmond Militante [EMAIL PROTECTED] writes:
hi all
i get this installing the openssh-portable port on a 4.8-RELEASE
machine
=== Building
said:
Redmond Militante [EMAIL PROTECTED] writes:
hi all
i get this installing the openssh-portable port on a 4.8-RELEASE machine
=== Building for openssh-portable-3.9.0.1,1
if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi
(cd openbsd-compat
:
hi all
i get this installing the openssh-portable port on a 4.8-RELEASE machine
=== Building for openssh-portable-3.9.0.1,1
if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi
(cd openbsd-compat make)
cc -o ssh ssh.o readconf.o clientloop.o sshtty.o
Redmond Militante [EMAIL PROTECTED] writes:
hi all
i get this installing the openssh-portable port on a 4.8-RELEASE machine
=== Building for openssh-portable-3.9.0.1,1
if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi
(cd openbsd-compat make)
cc -o ssh ssh.o
all
i get this installing the openssh-portable port on a 4.8-RELEASE machine
=== Building for openssh-portable-3.9.0.1,1
if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi
(cd openbsd-compat make)
cc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o
hi all
i get this installing the openssh-portable port on a 4.8-RELEASE machine
=== Building for openssh-portable-3.9.0.1,1
if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi
(cd openbsd-compat make)
cc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o
wo_shi_big_stomach [EMAIL PROTECTED] writes:
Phil Schulz wrote:
If you can't afford to upgrade the base OS and you do not want to
install OpenSSH from the ports
Sorry, I wasn't clear. I have no problem installing or
upgrading OpenSSH from ports. Indeed, that's all I
know how to do
Phil Schulz wrote:
If you can't afford to upgrade the base OS and you
do not want to
install OpenSSH from the ports
Sorry, I wasn't clear. I have no problem installing or
upgrading OpenSSH from ports. Indeed, that's all I
know how to do.
My question is how to upgrade OpenSSH as included
What is the procedure for patching/updating system
version of OpenSSH on an FBSD 5.2.1 box?
I used the excellent Rootkit Hunter security
assessment tool:
http://www.rootkit.nl/projects/rootkit_hunter.html
and it found that I'm running OpenSSH 3.6.1p1, which
has at least one vulnerability.
I
On 02/25/05 20:55, David Newman wrote:
What is the procedure for patching/updating system
version of OpenSSH on an FBSD 5.2.1 box?
If you can't afford to upgrade the base OS and you do not want to
install OpenSSH from the ports, then you'll need to specify what
vulnerability you are talking
David Newman wrote:
What is the procedure for patching/updating system
version of OpenSSH on an FBSD 5.2.1 box?
I used the excellent Rootkit Hunter security
assessment tool:
http://www.rootkit.nl/projects/rootkit_hunter.html
and it found that I'm running OpenSSH 3.6.1p1, which
has at least one
Hi all
did anybody knows how I can build openssh from the ports collection with
opensc support ???
best regards
Michael
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
dear firends:
there is a puzzle about openssh authentication, i try to solve it,
but i could not, could you help me?
there is two account named as 'joshua' and 'moon' on my server. i
want to disable password authentication method for 'joshua', let he can
login only use public key
* joshua [EMAIL PROTECTED] [1036 13:36]:
dear firends:
there is a puzzle about openssh authentication, i try to solve it,
but i could not, could you help me?
there is two account named as 'joshua' and 'moon' on my server. i
want to disable password authentication method for 'joshua
- Original Message -
From: Dan Finn [EMAIL PROTECTED]
Sent: Friday, October 01, 2004 2:20 AM
I want to upgrade OpenSSH/OpenSSL and I only want to have to use the
ports tree to do this. What is the best way to do this? If possible
I would like to over write my existing base
as the default instalation of openssh becomes deprecated, I don't know
which of the ports should I use, openssh or openssh-portable ?
what are the differences between them (besides the version number,
openssh-portable being the latest version, while openssh is only 3.6) ?
thanks in advance
I believe that openssh is openBSD's while portable is meant to be
installed on other OSes. Portable is your choice here.
Cristi
Petre Bandac wrote:
as the default instalation of openssh becomes deprecated, I don't know
which of the ports should I use
I want to upgrade OpenSSH/OpenSSL and I only want to have to use the
ports tree to do this. What is the best way to do this? If possible
I would like to over write my existing base installations of those two
packages, or delete the base install ones if that's possible
(preferably not by hand
On Thu, 30 Sep 2004 17:20:01 -0700, Dan Finn [EMAIL PROTECTED] wrote:
I want to upgrade OpenSSH/OpenSSL and I only want to have to use the
ports tree to do this. What is the best way to do this?
Just cd to the ports directory and
make all install clean
f possible
I would like to over write
On Wed, Apr 10, 2002 at 02:35:16AM -0400, Peter Leftwich wrote:
On Mon, 8 Apr 2002, Crist J. Clark wrote:
[snip]
PL My question was regarding ssh, not sshd.
Then I shall reprhase: Are you actually running the ssh(1) in /usr/local/bin/ssh
or the old one in /usr/bin/ssh?
Crist J. Clark
On Mon, 8 Apr 2002, Crist J. Clark wrote:
[snip]
PL My question was regarding ssh, not sshd.
Then I shall reprhase: Are you actually running the ssh(1) in /usr/local/bin/ssh or
the old one in /usr/bin/ssh?
Crist J. Clark | [EMAIL PROTECTED],[EMAIL PROTECTED]
On Sun, Apr 07, 2002 at 12:00:55AM -0800, Peter Leftwich wrote:
prompt$ pkg_info | grep -i openssh
openssh-3.0.2 OpenBSD's secure shell client and server (remote login prog
I just upgraded (or tried to upgrade) openssh on my FreeBSD 4.5-RELEASE
box using /stand/sysinstall but I get
On Sun, 7 Apr 2002 00:00:55 -0800 (PST)
Peter Leftwich [EMAIL PROTECTED] wrote:
prompt$ pkg_info | grep -i openssh
openssh-3.0.2 OpenBSD's secure shell client and server (remote
login prog
I just upgraded (or tried to upgrade) openssh on my FreeBSD
4.5-RELEASE box using /stand
Jason P Holland wrote:
Hello,
What is the preferred method that people are using for keeping openssl and
openssh up to date? Are most people using the ports version? Or the base
version? Seems like if there is a vunlerability released, its much easier
to cvsup the ports tree and reinstall
Hello,
What is the preferred method that people are using for keeping openssl and
openssh up to date? Are most people using the ports version? Or the base
version? Seems like if there is a vunlerability released, its much easier
to cvsup the ports tree and reinstall. But if you use the base
Thanks for the tip. Would you believe though I now
also have a problem installing openSSH from ports. I
have just CVSuped my ports tree but executing: make
install clean from the openssh directory exits with
the error:
Dependency warning: used OpenSSL version contains
known vulnerabilities
Please
Bryce wrote:
Dependency warning: used OpenSSL version contains
known vulnerabilities
Please update or define either WITH_OPENSSL_BASE or
WITH_OPENSSL_PORT
Can anyone throw some light on how to fix this?
Hi Bryce,
I'm not sure, but my guess is you need to install the openssl port
first!
On Fri, Jul 23, 2004 at 09:20:13AM +0200, Danny De Bie typed:
Bryce wrote:
Dependency warning: used OpenSSL version contains
known vulnerabilities
Please update or define either WITH_OPENSSL_BASE or
WITH_OPENSSL_PORT
Can anyone throw some light on how to fix this?
Hi Bryce,
I'm
1 - 100 of 186 matches
Mail list logo
