Qual é o pacote que fica o ssh no Woody ?
Olá pessoal, o título diz tudo. Valeu Sucesso flavio alberto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Qual é o pacote que fica o ssh no Woody ?
apt-get install ssh ? Sempre que quiser procurar um pacote que contenha algo que deseja faça assim: dpkg -l *coisa-desejada* No caso do ssh: dpkg -l *ssh* E para achar pacotes relacionados: apt-cache search ssh Isso vale para outros pacotes! []'s Henrique Olá pessoal, o título diz tudo. Valeu Sucesso flavio alberto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Henrique Pedroni Neto Administrador de Rede - ITAL (http://www.ital.org) E-mail: [EMAIL PROTECTED] UIN: 8146255 Dúvidas sobre Debian? Visite o Rau-Tu: http://rautu.cipsga.org.br -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Can't seem to get in via .shosts anymore after security update of ssh on woody?
Just curious as to why I can no longer use a .shosts file to get in as root anymore. I haven't changed sshd_config in any way. Anyone aware of some kind of change I'm running woody and have: dpkg -s ssh : kodaira:~# dpkg -s ssh Package: ssh Status: install ok installed Priority: optional Section: non-US Installed-Size: 1504 Maintainer: Matthew Vernon [EMAIL PROTECTED] Source: openssh Version: 1:3.4p1-0.0woody1 Provides: rsh-client Depends: libc6 (= 2.2.4-4), libpam0g (= 0.72-1), libssl0.9.6, libwrap0, zlib1g (= 1:1.1.4), libpam-modules (= 0.72-9), debconf, adduser Suggests: ssh-askpass, xbase-clients, dpkg (= 1.8.3.1), dnsutils Conflicts: ssh-nonfree ( 2), ssh-socks, ssh2, debconf ( 0.2.17), debconf-tiny ( 0.2.17), sftp, rsh-client ( 0.16.1-1) Conffiles: /etc/ssh/ssh_config 43aaf8cdb9b148e2dcc10469fba36e41 /etc/ssh/moduli c67600310eb998d72dff1e98b0a9051e /etc/init.d/ssh c3172ab180c4f0fc628bd0aa24707591 /etc/pam.d/ssh 7b36e8ca3b50960d7c222ed104328abf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SSH de woody no hace caso del umask
La cuestion es la siguiente, he actualizado el servidor de ssh a la version 3.0.2p1-9 y los clientes usan el mindterm para enviar ficheros al servidor, pero ahora todos los ficheros nuevos se crean con permisos 600. La nueva version no hace caso del umask? Las versiones viejas si tenian una directiva Umask para usar en el sshd_config, pero ahora no funciona. ¿Que puedo hacer, para que los usuarios (no iniciados en linux) no tengan que ir cambiando los privilegios a mano? -- Jordi Román Mejias e-mail: [EMAIL PROTECTED] Servei d' Informatica DistribuidaEscola Universitaria de Sabadell Universitat Autònoma de Barcelona -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: trouble installing the latest ssh from woody
Here's what I get now. any idea what's going on? danjah:/home/tim# DEBCONF_DEBUG=developer apt-get install ssh Reading Package Lists... Done Building Dependency Tree... Done The following NEW packages will be installed: ssh 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 2 packages not fully installed or removed. Need to get 0B/600kB of archives. After unpacking 1352kB will be used. Preconfiguring packages ... debconf (developer): starting /tmp/config.97771 configure debconf (developer): -- VERSION 2.0 debconf (developer): -- 0 2.0 debconf (developer): -- SET ssh/use_old_init_script true debconf (developer): -- 10 ssh/use_old_init_script doesn't exist debconf (developer): -- FSET ssh/use_old_init_script isdefault false debconf (developer): -- 10 ssh/use_old_init_script doesn't exist debconf (developer): -- INPUT medium ssh/protocol2_only debconf (developer): -- 10 ssh/protocol2_only doesn't exist debconf (developer): -- INPUT medium ssh/SUID_client debconf (developer): -- 10 ssh/SUID_client doesn't exist debconf (developer): -- INPUT medium ssh/run_sshd debconf (developer): -- 10 ssh/run_sshd doesn't exist debconf (developer): -- INPUT low ssh/forward_warning debconf (developer): -- 10 ssh/forward_warning doesn't exist debconf (developer): -- GO debconf (developer): -- 0 ok (Reading database ... 64061 files and directories currently installed.) Unpacking ssh (from .../ssh_1%3a3.0.2p1-8_i386.deb) ... debconf (developer): frontend started debconf (developer): frontend running, package name is ssh debconf (developer): starting /var/lib/dpkg/tmp.ci/config configure debconf (developer): -- VERSION 2.0 debconf (developer): -- 0 2.0 debconf (developer): -- SET ssh/use_old_init_script true debconf (developer): -- 10 ssh/use_old_init_script doesn't exist debconf (developer): -- FSET ssh/use_old_init_script isdefault false debconf (developer): -- 10 ssh/use_old_init_script doesn't exist debconf (developer): -- INPUT medium ssh/protocol2_only debconf (developer): -- 10 ssh/protocol2_only doesn't exist debconf (developer): -- INPUT medium ssh/SUID_client debconf (developer): -- 10 ssh/SUID_client doesn't exist debconf (developer): -- INPUT medium ssh/run_sshd debconf (developer): -- 10 ssh/run_sshd doesn't exist debconf (developer): -- INPUT low ssh/forward_warning debconf (developer): -- 10 ssh/forward_warning doesn't exist debconf (developer): -- GO debconf (developer): -- 0 ok debconf (developer): starting /var/lib/dpkg/tmp.ci/preinst install debconf (developer): -- VERSION 2.0 debconf (developer): -- 0 2.0 debconf (developer): -- GET ssh/use_old_init_script debconf (developer): -- 10 ssh/use_old_init_script doesn't exist dpkg: error processing /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb (--unp ack): subprocess pre-installation script returned error exit status 10 Errors were encountered while processing: /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) danjah:/home/tim# I'm also getting exit status 10 while trying to upgrade cvs and ash, and while trying to uninstall gdm Is my debconf setup just messed up? Is there an easy way to clean it up? thanks, Tim On Wed, Mar 13, 2002 at 02:59:47PM -0600, Colin Watson wrote: On Wed, Mar 13, 2002 at 11:36:09AM -0500, Tim Olsen wrote: I'm having trouble installing the latest ssh from woody: [..] dpkg: error processing /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb (--install): subprocess pre-installation script returned error exit status 10 Exit code 10 is usually a debconf error. Try it with DEBCONF_DEBUG=developer set in the environment. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
trouble installing the latest ssh from woody
I'm having trouble installing the latest ssh from woody: danjah:~# dpkg -D3773 -i /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb D10: ensure_pathname_nonexisting `/var/lib/dpkg/tmp.ci' (Reading database ... 63983 files and directories currently installed.) Unpacking ssh (from .../ssh_1%3a3.0.2p1-8_i386.deb) ... D20: process_archive conffile `/etc/ssh/ssh_config' no package, no hash D20: process_archive conffile `/etc/ssh/moduli' no package, no hash D20: process_archive conffile `/etc/init.d/ssh' no package, no hash D20: process_archive conffile `/etc/pam.d/ssh' no package, no hash D01: process_archive oldversionstatus=not installed D02: fork/exec /var/lib/dpkg/tmp.ci/preinst ( ) dpkg: error processing /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb (--install): subprocess pre-installation script returned error exit status 10 D02: fork/exec /var/lib/dpkg/tmp.ci/postrm ( ) D10: ensure_pathname_nonexisting `/var/lib/dpkg/tmp.ci' D10: ensure_pathname_nonexisting running rm -rf D10: ensure_pathname_nonexisting `/var/lib/dpkg/reassemble.deb' Errors were encountered while processing: /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb Upgrading also failed, so then I tried a purge followed by the above install. Is there a way to get more useful information out of the preinst script? can dpkg somehow have it set -v ? I had no trouble upgrading ssh on another woody machine that I maintain so this must be something specific to this machine. thanks, Tim
Re: trouble installing the latest ssh from woody
On Wed, Mar 13, 2002 at 11:36:09AM -0500, Tim Olsen wrote: I'm having trouble installing the latest ssh from woody: [..] dpkg: error processing /var/cache/apt/archives/ssh_1%3a3.0.2p1-8_i386.deb (--install): subprocess pre-installation script returned error exit status 10 Exit code 10 is usually a debconf error. Try it with DEBCONF_DEBUG=developer set in the environment. Cheers, -- Colin Watson [EMAIL PROTECTED]
Problema com o ssh do woody
Oi pessoal da lista Uso o potato a algum tempo e recentemenete instalei a versao woody. Nao consigo fazer conexao do potato para o woody utilizando ssh. O erro e o seginte: bad packet length 1349676916 Algum poderia me dizer qual e o problema Ate mais e obrigado Mauricio Perez
Re: SSH potato = woody
On Mon, Dec 24, 2001 at 12:05:47PM +0100, [EMAIL PROTECTED] wrote: On Mon, 24 Dec 2001, D. Gregory wrote: Salut, j'ai SSH 2.3.0p1-0.11 sur une potato, et SSH 3.0.1p1-1.2 sur une woody. Quand je me connecte sur ma woody depuis la patate, le prompt pour le mot de passe met environ 10s pour apparaitre, ce qui est relativement long: d'habitude c'est quasi instantané. Par contre quand je me connecte de ma woody sur ma patate, le prompt met moins d'une seconde a apparaitre... ssh 3 communique par defaut avec un protocole en version 2 ssh 2 communique par defaut avec un protocole en version 1 d'ou le temps de latence, le temps que ssh 3 bascule en protocole v1 Bof, ssh 2 est parfaitement capable de causer en protocole en version 2 avec ssh 3. Je pencherais plutôt (mais il faut voir les logs avec -v) pour un problème de résolution de nom (DNS et DNS inverse). Vincent
Re: SSH potato = woody
Le Mon, Jan 07, 2002 at 01:19:29PM +0100, Vincent Danjean a écrit : j'ai SSH 2.3.0p1-0.11 sur une potato, et SSH 3.0.1p1-1.2 sur une woody. Quand je me connecte sur ma woody depuis la patate, le prompt pour le mot de passe met environ 10s pour apparaitre, ce qui est relativement long: d'habitude c'est quasi instantané. Par contre quand je me connecte de ma woody sur ma patate, le prompt met moins d'une seconde a apparaitre... d'ou le temps de latence, le temps que ssh 3 bascule en protocole v1 Bof, ssh 2 est parfaitement capable de causer en protocole en version 2 avec ssh 3. Oui ssh3 est capable de parler v1 et v2 mais le temps de passer automatiquement de v2 a v1 est relativement long. Pour ne pas passer le paramètre à ssh à chaque lancement d'une commande ssh creer-modifier le fichier : ~/.ssh/config ex : ... Host le_nom_de_ma_machine.le.domaine le_nom_de_ma_machine CheckHostIP yes User toto Protocol 1 ... Pour plus d'information man ssh Je pencherais plutôt (mais il faut voir les logs avec -v) pour un problème de résolution de nom (DNS et DNS inverse). Vincent -- sudo ou je peux trouver une liste avec tous les raccourcis clavier linux? Nicolas Ledez - Virtual Net (www.virtual-net.fr) pgpwbLpV47ntY.pgp Description: PGP signature
Re: passwordless ssh on woody failed
In Debian A, I ssh-keygen the public key, scp and append to Debian B ~/.ssh/authorized_keys It seems that Debian now uses protocol version 2, so maybe you need to add v2 key to ~/.ssh/authorized_keys2. -- Alexey Python is executable pseudocode, Perl is executable line-noise.
Re: passwordless ssh on woody failed
In Debian A, I ssh-keygen the public key, scp and append to Debian B ~/.ssh/authorized_keys It seems that Debian now uses protocol version 2, so maybe you need to add v2 key to ~/.ssh/authorized_keys2. -- Alexey Python is executable pseudocode, Perl is executable line-noise. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Thanks. I end up with ssh-keygen -t rsa and then appended id_rsa.pub to .ssh/authorized_keys2 on the other machine. It works! -- Patrick Hsieh [EMAIL PROTECTED] GPG public key http://pahud.net/pubkeys/pahudatpahud.gpg
Re: passwordless ssh on woody failed
On Mon, Jan 07, 2002, Patrick Hsieh wrote: In Debian A, I ssh-keygen the public key, scp and append to Debian B ~/.ssh/authorized_keys It seems that Debian now uses protocol version 2, so maybe you need to add v2 key to ~/.ssh/authorized_keys2. Thanks. I end up with ssh-keygen -t rsa and then appended id_rsa.pub to .ssh/authorized_keys2 on the other machine. It works! Hi, Not sure exactly what's going on here, maybe you just have some config option specifying this in sshd_config, but, according to the release notes on openssh.org, for version 3.0 of openssh, authorized_keys2 is now depracated in favor of authorized_keys. Supposedly, IIRC, support for it might be removed in the future. HTH, Daniel -- Patrick Hsieh [EMAIL PROTECTED] -- Daniel A. Freedman Laboratory for Atomic and Solid State Physics Department of Physics Cornell University
Re: passwordless ssh on woody failed
On Mon, 7 Jan 2002 03:06:39 -0500 Daniel Freedman [EMAIL PROTECTED] wrote: Not sure exactly what's going on here, maybe you just have some config option specifying this in sshd_config, but, according to the release notes on openssh.org, for version 3.0 of openssh, authorized_keys2 is now depracated in favor of authorized_keys. Supposedly, IIRC, support for it might be removed in the future. Interesting, the ssh(1) manpage doesn't refer to authorized_keys2 anymore, just authorized_keys(and in the SSH protocol v2 section, to boot). Thanks for letting us know :) -- .--=-=-=-=--=---=-=-=. /David Barclay HarrisAut agere, aut mori. \ \Clan Barclay Either action, or death./ `---==-=-=-=-===-=---=--=' pgpFExezltWLM.pgp Description: PGP signature
passwordless ssh on woody failed
Hello list, I have to Debian woody with ssh-3.0.1p1-1.2. In Debian A, I ssh-keygen the public key, scp and append to Debian B ~/.ssh/authorized_keys Then I try to ssh login from Debian A to Debian B again, but still got the password prompt. Is there something wrong? -- Patrick Hsieh [EMAIL PROTECTED] GPG public key http://pahud.net/pubkeys/pahudatpahud.gpg
SSH potato = woody
Salut, j'ai SSH 2.3.0p1-0.11 sur une potato, et SSH 3.0.1p1-1.2 sur une woody. Quand je me connecte sur ma woody depuis la patate, le prompt pour le mot de passe met environ 10s pour apparaitre, ce qui est relativement long: d'habitude c'est quasi instantané. Par contre quand je me connecte de ma woody sur ma patate, le prompt met moins d'une seconde a apparaitre... Une idée ? -- Greg
Re: SSH potato = woody
Le Mon, Dec 24, 2001 à 10:09:49 +0100, D. Gregory écrivit: Salut, j'ai SSH 2.3.0p1-0.11 sur une potato, et SSH 3.0.1p1-1.2 sur une woody. Quand je me connecte sur ma woody depuis la patate, le prompt pour le mot de passe met environ 10s pour apparaitre, ce qui est relativement long: d'habitude c'est quasi instantané. Par contre quand je me connecte de ma woody sur ma patate, le prompt met moins d'une seconde a apparaitre... Une idée ? Salut, L'idée: je ne suis pas sûr mais je pense qu'entre la woody et la patatate il peut y avoir différente version du protocole (ie 1 et 2). Le conseil: l'option -v qui permet d'avoir le mode verbose PS: ce qui ne veut pas dire qu'il faut le balancer sur la liste brute de coffrage, il peut être intéressant de masquer quelques informations sensibles (point de vue de la sécurité). Bruno D.
Re: SSH potato = woody
On Mon, 24 Dec 2001, D. Gregory wrote: Salut, j'ai SSH 2.3.0p1-0.11 sur une potato, et SSH 3.0.1p1-1.2 sur une woody. Quand je me connecte sur ma woody depuis la patate, le prompt pour le mot de passe met environ 10s pour apparaitre, ce qui est relativement long: d'habitude c'est quasi instantané. Par contre quand je me connecte de ma woody sur ma patate, le prompt met moins d'une seconde a apparaitre... ssh 3 communique par defaut avec un protocole en version 2 ssh 2 communique par defaut avec un protocole en version 1 d'ou le temps de latence, le temps que ssh 3 bascule en protocole v1 il est possible d'initier la cnnection en fixant le protocole via l'option -1, voir man ssh Eric -- «Je suis en train de peaufiner les definitions de locales pour le vietnamien; est-ce que pour l'ordre alphabetique les lettres A(, A^, DD, E^, O^, O+ et U+ sont bien considerées comme des lettres à part ?» Pablo in Guide du linuxien pervers : Les locales ? C'est simple !
Restriction ssh access (woody)?
How do I allow only certain hosts to connect with ssh to my woody machine. In potato I has a file sshd_config that had an AllowHosts entry. I don't see this in woody's sshd_config file. Thanks, Lars. %%% Lars Jensen, Truckee Meadows Community College, Reno NV 89512-3999. Tel: 775.673.7113 E-mail: [EMAIL PROTECTED]
Re: Restriction ssh access (woody)?
On Tue, Dec 04, 2001 at 12:18:55AM -0800, Lars Jensen wrote: How do I allow only certain hosts to connect with ssh to my woody machine. In potato I has a file sshd_config that had an AllowHosts entry. I don't see this in woody's sshd_config file. You can use hosts.allow and hosts deny. It works without a problem for me. Regards. Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch Behold, happy is the man whom God correcteth. Therefore despise thou not the chastening of the Almighty. Job 5:17
Rãspuns: Restriction ssh access (woody)?
if i recall correct you add in /etc/hosts.deny a line ALL: ALL and in /etc/hosts.allow lines with the ips allowed and the services they can access,like sshd: 194.112.102.3, 193.230.167.22, 212.155.,217. and in.telnetd: server.host.com, 198.204.22.4, 140.24. or in.pop3d: ALL and stuff.. take care. Petre L. Daniel Linux Administrator,Canad Systems Pitesti http://www.cyber.ro email:[EMAIL PROTECTED] phone: +4048220044,+4048206200 -Mesaj original- De la: Johann Spies [mailto:[EMAIL PROTECTED] numele Johann Spies Trimis: Tuesday, December 04, 2001 4:12 AM Catre: Debian Users List Subiect: Re: Restriction ssh access (woody)? On Tue, Dec 04, 2001 at 12:18:55AM -0800, Lars Jensen wrote: How do I allow only certain hosts to connect with ssh to my woody machine. In potato I has a file sshd_config that had an AllowHosts entry. I don't see this in woody's sshd_config file. You can use hosts.allow and hosts deny. It works without a problem for me. Regards. Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch Behold, happy is the man whom God correcteth. Therefore despise thou not the chastening of the Almighty. Job 5:17 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh in woody?
On Thu, Jan 18, 2001 at 09:14:42PM -0700, Robert L. Harris wrote: I've build a new box, very basic. I did an upgrade to woody and now I try apt-get install ssh and it can't find a candidate??? Help? ssh is [non-us], so you need to add to your /etc/apt/sources.list: deb http://non-us.debian.org/debian-non-US stable/non-US main contrib non-free or anything along these lines.
ssh in woody?
I've build a new box, very basic. I did an upgrade to woody and now I try apt-get install ssh and it can't find a candidate??? Help? Robert :wq! --- Robert L. Harris| Micros~1 : Senior System Engineer |For when quality, reliability at RnD Consulting | and security just aren't \_ that important! DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. FYI: perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
Re: ssh in woody?
I've build a new box, very basic. I did an upgrade to woody and now I try apt-get install ssh and it can't find a candidate??? Help? ssh is in the non-US part of Debian. To install it add a line like deb ftp://ftp.de.debian.org/debian-non-US potato/non-US main contrib non-free to your sources.list file, and then run apt-get again. Hope this helps, Cheng
Re: ssh in woody?
On Thu, Jan 18, 2001 at 09:14:42PM -0700, Robert L. Harris wrote: I've build a new box, very basic. I did an upgrade to woody and now I try apt-get install ssh and it can't find a candidate??? Help? http://www.debian.org/distrib/packages Shows the package exists. What are the actual errors that apt-get displays and what are your source lines pointing to in - /etc/apt/sources.list ? kent -- I'd really love ta wana help ya Flanders but... Homer Simpson
ssh problem (woody)
Hello... After doing an upgrade just now, the new version of ssh ( sshd) is OpenSSH_2.3.0p1. Before the upgrade (done with apt-get), ssh service was working fine. Now, it's not working. I can still login to other machines, but when trying to login here, I get a Permission denied, please try again. error after entering the password. I don't know if this happens when using keys to authenticate. auth.log shows this: Jan 9 05:22:32 decoy sshd[6756]: Failed password for sena from 1.2.3.4 port 1023 Jan 9 05:22:36 decoy last message repeated 2 times Jan 9 05:22:36 decoy sshd[6756]: Connection closed by 1.2.3.4 Jan 9 05:22:36 decoy sshd[6756]: Cannot close PAM session[4]: System error The last line appears any time that I try to login. These lines appear when the server is started: Jan 9 05:24:35 decoy sshd[6774]: Server listening on 0.0.0.0 port 22. Jan 9 05:24:35 decoy sshd[6774]: Generating 768 bit RSA key. Jan 9 05:24:36 decoy sshd[6774]: RSA key generation complete. So, no error here. And when the server is stopped: Jan 9 05:25:48 decoy sshd[6774]: Received signal 15; terminating. No error either. Anyone has a clue? TIA, sena... -- [EMAIL PROTECTED], http://www.smux.net/~sena/ gpg fingerprint: F20B 12A8 A8F6 FD1F 9B1D BA62 C424 8E73 DD2E 47C8 SMUX - http://www.smux.net/
Cannot ssh from woody -- slink
Hi I have a slink-based machine (running the Linux Router Project, actually) that I use as a server, and a workstation I dual-boot with Win NT and Debian woody. I can ssh to the server from (1) itself, using ssh 1.2.26 (2) my workstation in Win NT (using SecureCRT) (3) my wife's Win NT machine, using SecureCRT I can also ssh from the server to the workstation. However, using the latest binaries, I cannot ssh to the server from my workstation running woody. The IP is the same in WinNT mode as in Linux, so there's no firewall on the server preventing this. If I run ssh -v myserver, I see (as best I can recall) something like this: Connecting to myserver [192.168.1.1] port 22. Allocated local port 1023. Connection closed. -- Here are some things I have tried: (1) Both ssh-nonfree and openssh packages (2) Removing and regenerating /etc/ssh/ (3) Removing ~/.ssh (4) Attempting to ssh from a newly created user ID (5) Removing known_hosts from the server (6) Running the server's sshd in debug mode (with -d flag) When I ran sshd in debug mode, it died when I tried to connect from the workstation, with a complaint about not forking in debug mode. Fair enough, perhaps. So, I am now completely stumped! The fundamental issue, I suppose, is why can I ssh in from WinNT, but not from Debian? Has anybody else got a theory as to why this might be happening? Help! Yours, Brian
