Re: SSH problem
On Tue, Jan 27, 2009 at 1:44 PM, Jasvinder S. Bahra wrote: But, when I try to use WinSCP under windows, it always failed. WinSCP errors: "Network error: Connection refused". Both scp & sftp fail if using WinSCP. > > Is there an entry /etc/hosts.allow allowing connections to the applicable > port? > > Jazz > If tcpwrappers were at fault I'd expect to see the connection open and then immediately close, not a connection-refused error. I'd lean more towards a network/port problem as some of the previous posters have mentioned. tcpdump would be a good tool here. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH problem
>>> But, when I try to use WinSCP under windows, it always failed. WinSCP >>> errors: "Network error: Connection refused". Both scp & sftp fail >>> if using WinSCP. Is there an entry /etc/hosts.allow allowing connections to the applicable port? Jazz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH problem
On Jan 26, 2009, at 12:54, Julian Stacey wrote: Hi, Reference: From: Xian Chen Date: Mon, 26 Jan 2009 13:45:56 -0500 Message-id: > Xian Chen wrote: Hi All, I can use scp to move files from a linux to my Freebsd machine. But, when I try to use WinSCP under windows, it always failed. WinSCP errors: "Network error: Connection refused". Both scp & sftp fail if using WinSCP. Any clues for this? on FreeBSD: man sftp says -v option exists man ssh also offers -v so try both those from Win/Lose/Mickesoft (*), Also ref. man sshd try kill -9 `cat /var/run/sshd.pid` or hash out sshd line in /etc/inetd.conf & then kill -HUP `cat /var/run/inetd.pid` & then run as root /usr/sbin/sshd -D -d & more /var/run/auth.log (*) PS I hate MS & dont use it, but doesnt invalidate debug stuff above though, except you might need to start ssh from a command line to add a parameter, rather than just clicking. Here is how I have setup secure ftp for our users: LAFN now provides a ftp server that handles the ftp-ssl and ftp-tls protocols (RFC-2228). These protocols will encrypt the user id and password and can also be configured to encrypt the file contents if desired. The standard ftp port, 21, is used for both encrypted and non-encrypted ftp sessions. The older sftp, scp, and implicit ftp-ssl protocols are not supported. Obviously transfer times are longer if encryption is used. There are several Windows and Unix clients that support these protocols. The following clients are believed to work properly: CuteFTP Pro 2.0 Windows FileZilla 2.0.0 beta 5 Windows (GPL) SmartFTP 1.0 build 969 Windows WinSSLWrap 1.17 Windows WS_FTP Pro 7.5 Windows FTP Voyager Secure 9.1.0.1 Windows Lftp 2.5.2 Unix In addition there is a client available at http://bsdftpd-ssl.sc.ru that will work with Windows 9x, NT, 2000, and some Linux distributions. The only known client for Macintosh is available in the LAFN FAQ. It only works with OS-X and is the command line client from the fstftpd-ssl distribution. The client info above is a bit old, but is probably still accurate. There may be additional clients available now. On the server I use the bsdftpd-ssl port. It replaces the base ftpd. Several of the above clients are in regular use. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH problem
Hi, Reference: > From: Xian Chen > Date: Mon, 26 Jan 2009 13:45:56 -0500 > Message-id: Xian Chen wrote: > Hi All, > > I can use scp to move files from a linux to my Freebsd machine. > > But, when I try to use WinSCP under windows, it always failed. WinSCP > errors: "Network error: Connection refused". Both scp & sftp fail if using > WinSCP. > > Any clues for this? on FreeBSD: man sftp says -v option exists man ssh also offers -v so try both those from Win/Lose/Mickesoft (*), Also ref. man sshd try kill -9 `cat /var/run/sshd.pid` or hash out sshd line in /etc/inetd.conf & then kill -HUP `cat /var/run/inetd.pid` & then run as root /usr/sbin/sshd -D -d & more /var/run/auth.log (*) PS I hate MS & dont use it, but doesnt invalidate debug stuff above though, except you might need to start ssh from a command line to add a parameter, rather than just clicking. Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH problem
On Mon, Jan 26, 2009 at 6:44 PM, SDH Support wrote: > >> I don't think he'll be able to tcpdump on the windows box. > > > There are tcpdump equivalents such as wireshark and windump. > Yeah, I was replied to off-list with that information. I stand corrected, and apologize. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: SSH problem
> I don't think he'll be able to tcpdump on the windows box. There are tcpdump equivalents such as wireshark and windump. --- Kevin Systems Administrator www.stardothosting.com/linux-vps-hosting ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH problem
On Mon, Jan 26, 2009 at 6:10 PM, SDH Support wrote: >> >> Hi All, >> >> I can use scp to move files from a linux to my Freebsd machine. >> >> But, when I try to use WinSCP under windows, it always failed. WinSCP >> errors: "Network error: Connection refused". Both scp & sftp fail if >> using >> WinSCP. >> >> Any clues for this? > > Tcpdump on both boxes. -w to a file and analyze w/ ipsumdump. > I don't think he'll be able to tcpdump on the windows box. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: SSH problem
> > Hi All, > > I can use scp to move files from a linux to my Freebsd machine. > > But, when I try to use WinSCP under windows, it always failed. WinSCP > errors: "Network error: Connection refused". Both scp & sftp fail if > using > WinSCP. > > Any clues for this? Tcpdump on both boxes. -w to a file and analyze w/ ipsumdump. --- Kevin Systems Administrator www.stardothosting.com/linux-vps-hosting ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH problem
On Mon, Jan 26, 2009 at 11:21:57AM -0800, Xin LI wrote: > Xian Chen wrote: > > I can use scp to move files from a linux to my Freebsd machine. > > > > But, when I try to use WinSCP under windows, it always failed. WinSCP > > errors: "Network error: Connection refused". Both scp & sftp fail if using > > WinSCP. > > > > Any clues for this? > My guess is that you have specified an incorrect port number. Try tcpdump? Another possibility, IIRC, is a bad ssh hostkey (I haven't used WinSCP in quite some time, but I recall that its error messages are not particularly informative). You can also check to see if you can reach the server. Try a plain telnet to port 22. You won't actually be able to establish a connection if you aren't running ssh, but you should see something like: Connected to . Escape character is '^]'. SSH-2.0-OpenSSH_5.1p1 FreeBSD-20080901 -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Xian Chen wrote: > Hi All, > > I can use scp to move files from a linux to my Freebsd machine. > > But, when I try to use WinSCP under windows, it always failed. WinSCP > errors: "Network error: Connection refused". Both scp & sftp fail if using > WinSCP. > > Any clues for this? My guess is that you have specified an incorrect port number. Try tcpdump? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkl+DVUACgkQi+vbBBjt66AOWgCfWt79XNAP8piVB2etJS6BxKL2 2NUAnAw2nnOUrGbl8Wk0YmdYRXq3BTjP =9ax6 -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
SSH problem
Hi All, I can use scp to move files from a linux to my Freebsd machine. But, when I try to use WinSCP under windows, it always failed. WinSCP errors: "Network error: Connection refused". Both scp & sftp fail if using WinSCP. Any clues for this? Thanks in advance. Xian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: SSH Problem
* Kevin Oberman <[EMAIL PROTECTED]> [011003 08:50]: > > Date: Tue, 2 Oct 2001 22:54:22 -0400 > > From: parv <[EMAIL PROTECTED]> > > > > this was, on the fateful occasion around Oct 02 21:07 -0400, > > sent by Kevin Oberman > > > > > > It does not distribute 2.3 with either stable or current. It was > > > included (with security patches) in 4.4-release. > > > > > > >From 4.4-stable: > > > > ssh -V > > > OpenSSH_2.9 FreeBSD localisations 20010713, SSH protocols 1.5/2.0, OpenSSL >0x0090601f > > > > really? i get... > > > > SSH Version OpenSSH_2.3.0 FreeBSD localisations 20010713, protocol versions >1.5/2.0. > > Compiled with SSL (0x0090601f). > > > > > > ...i cvusp'd sources on sep 21 2001 6.30.41 utc. when did you build your > > world? > > cvsuped on Sat. the 29th. I got a fresh /usr/src from cvsup.uk.freebsd.org yesterday afternoon: rasputin@shikima rasputin]$ls -l `which ssh` -r-xr-xr-x 2 root wheel 199064 Oct 2 16:25 /usr/bin/ssh rasputin@shikima rasputin]$uname -a FreeBSD 4.4-STABLE #0: Tue Oct 2 15:42:36 BST 2001 \ rasputin@s hikima.mine.nu:/usr/obj/devel/src/sys/SHIKIMA i386 rasputin@shikima rasputin]$ssh -V OpenSSH_2.9 FreeBSD localisations 20010713, SSH protocols 1.5/2.0, OpenSSL 0x0090601f Are the mirrors up to date? -- [Sir Stafford Cripps] has all the virtues I dislike and none of the vices I admire. -- Winston Churchill Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SSH Problem
In message <[EMAIL PROTECTED]> "Klaus-J. Wolf" writes: : with 4.4-STABLE 010929, ssh seems to work unexpectedly - even when I : have my public key in the target machine's authorized_keys, ssh aks me : for a password (breaks a lot of scripts). Could this be because you are using protocol version 2, but only have version 1 keys? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: SSH Problem
It seems to me that's because OpenSSH_2.9 has been MFC. It by default has ForwardAgent option off (at least on FreeBSD with default config). You can fix it with ~/.ssh/config or change /etc/ssh/ssh_config Host * ForwardAgentyes -- Michal Mertl [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SSH Problem
> Date: Tue, 2 Oct 2001 22:54:22 -0400 > From: parv <[EMAIL PROTECTED]> > > this was, on the fateful occasion around Oct 02 21:07 -0400, > sent by Kevin Oberman > > > > It does not distribute 2.3 with either stable or current. It was > > included (with security patches) in 4.4-release. > > > > >From 4.4-stable: > > > ssh -V > > OpenSSH_2.9 FreeBSD localisations 20010713, SSH protocols 1.5/2.0, OpenSSL >0x0090601f > > really? i get... > > SSH Version OpenSSH_2.3.0 FreeBSD localisations 20010713, protocol versions 1.5/2.0. > Compiled with SSL (0x0090601f). > > > ...i cvusp'd sources on sep 21 2001 6.30.41 utc. when did you build your > world? cvsuped on Sat. the 29th. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
SSH Problem
Hi, with 4.4-STABLE 010929, ssh seems to work unexpectedly - even when I have my public key in the target machine's authorized_keys, ssh aks me for a password (breaks a lot of scripts). Greetings k.j. -- Klaus-Juergen Wolf | Tiscali Business GmbH System Engineering | Robert-Bosch-Str. 32 / D-63303 Dreieich fon: +49-6103-916-993 | http://www.tiscali-business.de/ fax: +49-6103-916-899 | [EMAIL PROTECTED] gpg: 900E 93B4 B772 B132 FBF4 796E 2E20 3CAC 1C50 95BA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ssh problem upgrading to 4.2-stable
On Wed, Jan 31, 2001 at 11:41:14AM +, Pete French wrote: > So, yesterday we upgraded the last machine running 3.5 here to 4.2 stable > (CVSuped on saturday I believe). All went very smoothly and everything runs > fine except for ssh. We are using openssh, and it rejects peoples > passwords with "Permission denied, please try again." > > I seem to recall reading that password encryptionc hanged from MD5 to DES > between 3.x and 4.x - and I suspect this could be the problem. The > /usr/lib/libcrypt.so file is a link to libdescrypt.so, so I assume > we are now using DES passwords. Old users have MD5 passwords, but new > users are created with DES passwords. Using 'passwd' however converts them > to MD5. I have checked auth.conf, mailing list archives and done a web > search and am running out of ideas. > There is an issue with /etc/pam.conf. You can overwrite it with the one under /usr/src. This worked for me. Also there is another pithole (i fell into): sshd dies because there is an obsolete option in /etc/ssh/sshd_config, that you need to remove. ConnectionsPerPeriod 5/10 > Am I barking up the wrong tree entirely here ? > > -pete. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Michel Talon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ssh problem
On Sun, 21 Jan 2001, Chris Faulhaber wrote: Thanks a lot ... These infos passed myself unread. I changed one line and all things worked fine. Thanks ... :>On Sun, Jan 21, 2001 at 09:50:00PM +0100, O. Hartmann wrote: :>> Mmmh, well, I do not know whether this is a subject of this forum. :>> :>> Since a couple of days I lost contact to one of our machines, means: :>> I can not login via ssh. I think it has something to do with the last :>> cvsupdate I made (and buildworld afterwards), because I did not chance the :>> configuration and it worked before. :>> :>> I thinks I saw three or five days before some openssh-changes in the :>> source code, so maybe this problem is related to a simple :>> "misconfiguration due a source update. Does anyone have some hints :>> or can report the same problem? :>> :> :>/etc/ssh/sshd_config changed due to the OpenSSH MFC. If you did not :>merge the changes, sshd will not start. :> :>-- :>Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] :> :>FreeBSD: The Power To Serve - http://www.FreeBSD.org :> - MfG O. Hartmann --- [EMAIL PROTECTED] Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ssh problem
On Sun, Jan 21, 2001 at 09:50:00PM +0100, O. Hartmann wrote: > Mmmh, well, I do not know whether this is a subject of this forum. > > Since a couple of days I lost contact to one of our machines, means: > I can not login via ssh. I think it has something to do with the last > cvsupdate I made (and buildworld afterwards), because I did not chance the > configuration and it worked before. > > I thinks I saw three or five days before some openssh-changes in the > source code, so maybe this problem is related to a simple > "misconfiguration due a source update. Does anyone have some hints > or can report the same problem? > /etc/ssh/sshd_config changed due to the OpenSSH MFC. If you did not merge the changes, sshd will not start. -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ssh problem
Mmmh, well, I do not know whether this is a subject of this forum. Since a couple of days I lost contact to one of our machines, means: I can not login via ssh. I think it has something to do with the last cvsupdate I made (and buildworld afterwards), because I did not chance the configuration and it worked before. I thinks I saw three or five days before some openssh-changes in the source code, so maybe this problem is related to a simple "misconfiguration due a source update. Does anyone have some hints or can report the same problem? Oliver - MfG O. Hartmann --- [EMAIL PROTECTED] Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Major SSH problem
There was a security fix related to this posted in this list a few weeks ago. It sounds like its related to that. ---Mike At 12:52 PM 11/22/00 -0600, Thomas T. Veldhouse wrote: >I just upgraded via sources from a 4.2-BETA to todays 4.2-STABLE. Now I >can not get port forwarding to work through my SSH clients anymore. I can >not find an option in /etc/ssh/sshd_config that turns this option on or >off. What am I missing? Why has this option so quietly changed? > >Tom Veldhouse >[EMAIL PROTECTED] > > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Major SSH problem
I just upgraded via sources from a 4.2-BETA to todays 4.2-STABLE. Now I can not get port forwarding to work through my SSH clients anymore. I can not find an option in /etc/ssh/sshd_config that turns this option on or off. What am I missing? Why has this option so quietly changed? Tom Veldhouse [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Small ssh problem in latest STABLE
> uname -a FreeBSD puppeteer.es.net 4.2-BETA FreeBSD 4.2-BETA #0: Thu Nov 2 10:43:54 PST 2000 [EMAIL PROTECTED]:/scratch/obj/scratch/src/sys/THINKPAD i386 Just cvsuped and re-built and X forwarding via ssh did not work. I edited /etc/ssh/ssh_config by uncommenting the ForwardX11=yes and it started working again. It looks like defaults have changed with no changes to the /usr/src/crypto/openssh/ssh_config to match. The man page IS correct, but with no change in ssh_config, mergemaster does not provide and alert that something needs to be changed. I suspect that the same is true of sshd_config. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
