On Wed, Nov 1, 2017 at 7:58 PM, Greg Wooledge wrote:
> The directives that work in ~/.ssh/config also work in /etc/ssh/ssh_config
> and this includes the Host matching stuff.
>
> As it says in the man page,
>
> SYNOPSIS
> ~/.ssh/config
> /etc/ssh/ssh_config
>
> Since you only want to us
On Wed, Nov 01, 2017 at 07:40:40PM +, Glenn English wrote:
> I didn't create the ~/.ssh/config file because I wanted ssh to work
> for me, no matter who I logged in as or su'ed to. I realize (or think,
> anyway) that's going to open my admin box to the darkSide. I need to
> think about that.
T
On Wed, Nov 1, 2017 at 12:47 AM, Sven Hartge wrote:
> No, this is not the solution, as this will a) set this for every
> connection and b) restrict the Cipher list to *only* this insecure
> cipher.
>
> Please read "man ssh_config". The Ciphers statement recognizes + and -
> as prefixes to add or
Glenn English wrote:
> On Wed, Nov 1, 2017 at 12:47 AM, Sven Hartge wrote:
>> What do you mean? Just create ~/.ssh/config and put a Host statement
>> like above inside it.
> No prob, and will do. I'm used to ssh creating files in config
> directories for me.
OpenSSH never did that for config f
On Wed, Nov 1, 2017 at 12:47 AM, Sven Hartge wrote:
> There are. Both sides exchange a symmetric session key to use for the
> connection. The public/private key which can be used with SSH has
> nothing to do with this.
Yeah. That what I thought it was all about -- the login keys.
> What do you
On Tue, 31 Oct 2017, Glenn English wrote:
> On Tue, Oct 31, 2017 at 9:45 PM, Don Armstrong wrote:
> > Host cisco1841
> > KexAlgorithms diffie-hellman-group1-sha
> > Ciphers aes128-cbc,3des-cbc
> > MACs hmac-md5,hmac-sha1
> >
> > in your ~/.ssh/config and then connect to the machine
Glenn English wrote:
> On Tue, Oct 31, 2017 at 9:45 PM, Don Armstrong wrote:
>> It's ~/.ssh/config.
> Typo, please excuse.
>> That's the Key-exchange algorithm.
> That kinda makes sense. It sounds like that has nothing to do with the
> problem, since there are no keys involved here.
There ar
Take it back. Doesn't work anywhere but the router. FYI...
--
Glenn English
On Tue, Oct 31, 2017 at 9:45 PM, Don Armstrong wrote:
> It's ~/.ssh/config.
Typo, please excuse.
> That's the Key-exchange algorithm.
That kinda makes sense. It sounds like that has nothing to do with the
problem, since there are no keys involved here.
> Generally, what happens is that older
On Tue, 31 Oct 2017, Glenn English wrote:
> So I looked around a bit, and the openssh website says that's a
> insecure algorithm, but I can enable it if I want to by putting some
> text in ~/.ssh.config. Except there is no ~/.ssh.config. I created one
> and put what I think is the recommended text
buster, seems to be all hosts can't talk to Cisco router
I'd like to get into my Cisco 1841 (IOS 12.4) router with ssh like I
have for a decade or so. But buster's ssh says there's no useful
encryption algorithm -- says the offer is diffie-hellman-group1-sha1.
So I looked around a bit, and the ope
It helps to explain things, Daniel, but truly, the client in question
is horrendously out of date and deprecated for all secure intents and
purposes, I'm quite happy to retire it from active support on my
server.
On Sat, 16 Jan 2016 15:19:33 -0300, you wrote:
>Hi, Steve.
>
>On 14/01/16 13:10, Ste
Daniel,
On Sat, 16 Jan 2016 14:50:20 -0300, you wrote:
>I'm sorry. I Had forgotten of the detail of the accessibility :(
No worries. Things are in a sorry state at the moment because of other
things I did without realizing I did them, but I've already told my
usership that Voyager will have to g
Hi, Steve.
On 14/01/16 13:10, Steve Matzura wrote:
> Failing connection:
> (...)
> no matching cipher found: client
> aes192-cbc,3des-cbc,blowfish-cbc,aes128-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-...@lysator.liu.se,des-cbc,des-...@ssh.com
> server
> aes128-ctr,ae
Hi, Steve.
On 14/01/16 13:01, Steve Matzura wrote:
>> I do not know that client, but if your users are using Firefox, maybe
>> you could use FireFTP [1]. I never had problems with it, and we could
>> also say that while users use Firefox, you could run it on different
>> operating systems.
> It
The problem is that the older client doesn't support ciphers newer than CBC
and arcfour (both depreciated on the newer server versions of OpenSSH).
Lookup how to re-enable these suites using the Cipher directive.
One more piece of the puzzle. The working system is Red Hat Fedora 20,
the non-working one is Debian 8.2.
More info. I used getenforce' and found SELinux is installed but
disabled on the system where FTP Voyager can connect using SFTP over
ssh, and not installed at all on the system where FTP Voyager cannot
connect. In fact, using either the `getenforce' or `'sestatus' on the
no-connect system yields `
Daniel,
On Thu, 14 Jan 2016 09:05:36 -0300, you wrote:
>Hi, Steve.
>
>On 14/01/16 08:45, Steve Matzura wrote:
>
>> This is clearly the problem area. I tried some ssh option settings in
>> Voyager with no success. Should this client be retired? It's not
>> *that* old.
>
>I do not know that client,
I decided to put the two logs from `sshd -d' side-by-side to try to
figure out where the differences are. Both logs have the following
lines immediately after the connection request:
debug1: Client protocol version 2.0; client software version
FTP-Voyager-15.2.0.15
debug1: no match: FTP-Voyager-15
Hi, Steve.
On 14/01/16 08:45, Steve Matzura wrote:
> This is clearly the problem area. I tried some ssh option settings in
> Voyager with no success. Should this client be retired? It's not
> *that* old.
I do not know that client, but if your users are using Firefox, maybe
you could use FireFTP
Lars,
On Thu, 14 Jan 2016 12:45:09 +0200, you wrote:
>Can you update the client to one that uses the safer ciphers and avoids
>the deprecated ones?
You and I came to the same conclusion with the same lines of log as
evidence at about the same time. Amazing.
Many of my users use Voyager version
Tomas,
On Thu, 14 Jan 2016 05:32:04 -0500, I wrote:
>debug1: Enabling compatibility mode for protocol 2.0
>debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-5
>debug1: permanently_set_uid: 107/65534 [preauth]
>debug1: list_hostkey_types:
>ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 [p
On 01/14/2016 12:32 PM, Steve Matzura wrote:
> debug1: sshd version OpenSSH_6.7, OpenSSL 1.0.1k 8 Jan 2015
>...
> debug1: Client protocol version 2.0; client software version
> FTP-Voyager-15.2.0.15
> debug1: no match: FTP-Voyager-15.2.0.15
> debug1: Enabling compatibility mode for protocol 2.0
> .
Tomas,
On Wed, Jan 13, 2016 at 07:13:57PM -0500, Steve Matzura wrote:
>> I hope this isn't off-topic by too much. If it is, a word to me
>> privately and I'll wait for responses to queries I've made elsewhere.
>I'm not as much of an SSH guru to "get" what's going on by just reading
>configs, but a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jan 13, 2016 at 07:13:57PM -0500, Steve Matzura wrote:
> I hope this isn't off-topic by too much. If it is, a word to me
> privately and I'll wait for responses to queries I've made elsewhere.
>
> I maintain two FTP servers and support four Wi
I hope this isn't off-topic by too much. If it is, a word to me
privately and I'll wait for responses to queries I've made elsewhere.
I maintain two FTP servers and support four Windows-based FTP clients
for users of those servers--FTP Voyager, FlashFXP, Filezilla, and
WinSCP. One server accepts a
>
> $ ssh badapple df -lh
>
Not work. the administrator can't ssh either.
I don't know. at present just wait.
Thanks,
Best regards,
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http
lina wrote:
> When I tried to ssh, it's chocked without warning:
>
> $ ssh badapple -v
Unfortunately -v on the client side rarely returns the critically
useful information to know what is happening. It is -v on the sshd
side that is more interesting. But of course it is hard to set up an
'sshd
On 17/07/12 11:09 PM, lina wrote:
Hi,
When I tried to ssh, it's chocked without warning:
$ ssh badapple -v
OpenSSH_6.0p1 Debian-2, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /home/lina/.ssh/config
debug1: /home/lina/.ssh/config line 30: Applying options for badapple
debug1: R
Hi,
When I tried to ssh, it's chocked without warning:
$ ssh badapple -v
OpenSSH_6.0p1 Debian-2, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /home/lina/.ssh/config
debug1: /home/lina/.ssh/config line 30: Applying options for badapple
debug1: Reading configuration data /etc/ssh/s
On 08/23/2011 04:18 PM, RiverWind wrote:
> I do indeed have an "ssh" server installed on my linux box, and it
> seems to be working just fine.
We need details, see below.
> I am able to ssh over to my
> "shellworld" account without any problem. However, I am not able to
> ssh over from shellworld
Hey There,
I would first of all like to thank everyone who responded
altruistically to my originally posts. I would say that I now have
half a problem compared to the whole specimen that I had before.
I do indeed have an "ssh" server installed on my linux box, and it
seems to be working just fi
> Alan Chandler writes:
> On 04/08/11 09:15, Ivan Shmakov wrote:
> Alan Chandler writes:
>>> (I actually have loads of these in my config file for all different
>>> combinations of username and host - I also tend to make different
>>> key pairs for each host which is why I am spe
On 04/08/11 09:15, Ivan Shmakov wrote:
Alan Chandler writes:
> (I actually have loads of these in my config file for all different
> combinations of username and host - I also tend to make different key
> pairs for each host which is why I am specifying an IdentityFile in
> each.)
> Alan Chandler writes:
> (I actually have loads of these in my config file for all different
> combinations of username and host - I also tend to make different key
> pairs for each host which is why I am specifying an IdentityFile in
> each.)
Why? The asymmetric cryptography e
On Thu, Aug 4, 2011 at 3:23 PM, Alan Chandler
wrote:
> Apologies to lina - I replied directly to her instead of the list = here is
> what I sent.
>
> On 04/08/11 08:21, Alan Chandler wrote:
>> On 02/08/11 16:02, lina wrote:
>>> Hi,
>>>
>>> when I tried to ssh some_server, it showed me,
>>>
>>> Per
Apologies to lina - I replied directly to her instead of the list = here
is what I sent.
On 04/08/11 08:21, Alan Chandler wrote:
> On 02/08/11 16:02, lina wrote:
>> Hi,
>>
>> when I tried to ssh some_server, it showed me,
>>
>> Permission denied (publickey,gssapi-with-mic,password).
>>
>> 1] I t
Thanks all for your suggestions.
The problem was solved after chmod og-rw * in ~/.ssh directory.
Thanks,
On Wed, Aug 3, 2011 at 11:55 AM, Eero Volotinen wrote:
> 2011/8/2 lina :
>> Hi,
>>
>> when I tried to ssh some_server, it showed me,
>>
>> Permission denied (publickey,gssapi-with-mic,passwo
2011/8/2 lina :
> Hi,
>
> when I tried to ssh some_server, it showed me,
>
> Permission denied (publickey,gssapi-with-mic,password).
>
> 1] I tried ssh from desktop, laptop and other server, the same problem.
> 2] I generate a new key by ssh-keygen in some_server, it still has
> this problem.
>
>
On Wed, Aug 3, 2011 at 12:34 AM, Juan Sierra Pons wrote:
> 2011/8/2 lina :
>> On Tue, Aug 2, 2011 at 11:24 PM, Joao Ferreira Gmail
>> wrote:
>>> On Tue, 2011-08-02 at 23:02 +0800, lina wrote:
Hi,
when I tried to ssh some_server, it showed me,
Permission denied (publickey,
lina:
>
> I can ssh by username@full_some_server_address, but can't access in a
> simple way,
Then create the file ~/.ssh/config and add an entry like this:
Host shortname
User username
HostName full_some_server_address
After saving the file, you can use 'ssh shortname' to connect to th
2011/8/2 lina :
> On Tue, Aug 2, 2011 at 11:24 PM, Joao Ferreira Gmail
> wrote:
>> On Tue, 2011-08-02 at 23:02 +0800, lina wrote:
>>> Hi,
>>>
>>> when I tried to ssh some_server, it showed me,
>>>
>>> Permission denied (publickey,gssapi-with-mic,password).
>>>
>>> 1] I tried ssh from desktop, lapt
Hi Lina,
lina wrote:
I can ssh by username@full_some_server_address, but can't access in a
simple way,
Is it simply that you are one user and you want to ssh to a different
user name?
If you ssh some_server, then it will default to whatever username you
are currently logged in as.
--
Kin
On Tue, Aug 2, 2011 at 11:24 PM, Joao Ferreira Gmail
wrote:
> On Tue, 2011-08-02 at 23:02 +0800, lina wrote:
>> Hi,
>>
>> when I tried to ssh some_server, it showed me,
>>
>> Permission denied (publickey,gssapi-with-mic,password).
>>
>> 1] I tried ssh from desktop, laptop and other server, the sam
On Tue, 2011-08-02 at 23:02 +0800, lina wrote:
> Hi,
>
> when I tried to ssh some_server, it showed me,
>
> Permission denied (publickey,gssapi-with-mic,password).
>
> 1] I tried ssh from desktop, laptop and other server, the same problem.
> 2] I generate a new key by ssh-keygen in some_server,
Hi,
when I tried to ssh some_server, it showed me,
Permission denied (publickey,gssapi-with-mic,password).
1] I tried ssh from desktop, laptop and other server, the same problem.
2] I generate a new key by ssh-keygen in some_server, it still has
this problem.
I can ssh by username@full_some_se
I've been experiencing problems with my machine. After some time of
remotely logging on it via ssh next thing is I knew is that I am
disconnected and now I cannot login again via ssh and its giving me:
/no matching cipher found/: client server
aes128-cbc,3des-cbc,blowfish-cbc,cast128
-cbc,arc
On Fri, Sep 21, 2007 at 10:30:03AM -0400, Douglas A. Tutty wrote:
> On Fri, Sep 21, 2007 at 02:33:14AM -0600, Nate Duehr wrote:
> > On Sep 19, 2007, at 10:54 AM, Wayne Topa wrote:
> > >Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> > >>Just for completeness, you didn't need a googl
On Fri, Sep 21, 2007 at 02:33:14AM -0600, Nate Duehr wrote:
> On Sep 19, 2007, at 10:54 AM, Wayne Topa wrote:
> >Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> >>Just for completeness, you didn't need a google search. The info is
> >>somewhere around line 721 in the ssh(1) man pag
On Sep 19, 2007, at 10:54 AM, Wayne Topa wrote:
Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
On Tue, Sep 18, 2007 at 10:38:50PM -0400, Wayne Topa wrote:
I've been messing with that for 2 weeks. I must not have used a
good
enough search phrase on Google.
Just for comple
On Thu, Sep 20, 2007 at 11:19:35AM -0400, Wayne Topa wrote:
> Andrew Sackville-West([EMAIL PROTECTED]) is reported to have said:
> > well its interesting that it cares what the parent directory perms are
> > (from your other mail in this thread). I would think the .ssh
> > directory would be suff
Andrew Sackville-West([EMAIL PROTECTED]) is reported to have said:
> On Wed, Sep 19, 2007 at 01:42:48PM -0400, Wayne Topa wrote:
>
> ...
>
> > I agree Andrew. Other then reading the mail today I am going to be
> > looking into the problem, as it was, to see if I can figure out
> > exactly, why t
On Wed, Sep 19, 2007 at 01:42:48PM -0400, Wayne Topa wrote:
...
> I agree Andrew. Other then reading the mail today I am going to be
> looking into the problem, as it was, to see if I can figure out
> exactly, why the problem occured and what package the bug report
> should be filed against.
>
Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> On Wed, Sep 19, 2007 at 12:54:57PM -0400, Wayne Topa wrote:
> > Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> > > On Tue, Sep 18, 2007 at 10:38:50PM -0400, Wayne Topa wrote:
> > >
> > > > I've been messing with that
On Wed, Sep 19, 2007 at 12:54:57PM -0400, Wayne Topa wrote:
> Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> > On Tue, Sep 18, 2007 at 10:38:50PM -0400, Wayne Topa wrote:
> >
> > > I've been messing with that for 2 weeks. I must not have used a good
> > > enough search phrase on
Andrew Sackville-West([EMAIL PROTECTED]) is reported to have said:
> On Wed, Sep 19, 2007 at 12:54:57PM -0400, Wayne Topa wrote:
> > Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> > > On Tue, Sep 18, 2007 at 10:38:50PM -0400, Wayne Topa wrote:
> > >
> > > > I've been messing with
On Wed, Sep 19, 2007 at 12:54:57PM -0400, Wayne Topa wrote:
> Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> > On Tue, Sep 18, 2007 at 10:38:50PM -0400, Wayne Topa wrote:
> >
> > > I've been messing with that for 2 weeks. I must not have used a good
> > > enough search phrase on
Douglas A. Tutty([EMAIL PROTECTED]) is reported to have said:
> On Tue, Sep 18, 2007 at 10:38:50PM -0400, Wayne Topa wrote:
>
> > I've been messing with that for 2 weeks. I must not have used a good
> > enough search phrase on Google.
> >
>
> Just for completeness, you didn't need a google se
On Tue, Sep 18, 2007 at 10:38:50PM -0400, Wayne Topa wrote:
> I've been messing with that for 2 weeks. I must not have used a good
> enough search phrase on Google.
>
Just for completeness, you didn't need a google search. The info is
somewhere around line 721 in the ssh(1) man page. :))
Do
had used
that a few years ago when troubleshooting an ssh problem. I'll crawl
off onto the corner stool now.
Many Thanks Guys!!!
Wayne (The Dunce)
--
Don't document the program; program the document.
___
--
To UNSUBSCRIBE, email to
On 2007-09-18T16:46:59-0700, David Brodbeck wrote:
> Nine times out of ten when passwordless login doesn't work for me,
> it's a permissions issue.
David probably nailed it, but if you still have an issue it is sometimes
helpful to run ssh with - then compare output between working and
non
On Sep 18, 2007, at 4:25 PM, Wayne Topa wrote:
If anyone has an idea as to what is going on, I would appreciate a
kick in the right direction.
Check auth.log on the box you're having problems logging into. Often
there are clues there. See if sshd logs something it's unhappy about
when yo
I have a little ssh problem that I hope ya'll can help me with.
We have a 8 box LAN, 6 of which are Linux. The latest addition is an
AMD64 box that has an ssh problem.
I have setup password-less ssh logins on all of the Linux boxen for 3
users. All ssh logins work from 5 of the boxes. O
"Russell L. Harris" <[EMAIL PROTECTED]> wrote:
> * Amy Templeton <[EMAIL PROTECTED]> [070515 11:07]:
> > Alternately, have you considered using GNU Screen? That way, if you
> > start up mc in it and later SSH in, all you need to do is screen -r
> > and you've got it...
> Thanks for the introductio
* Amy Templeton <[EMAIL PROTECTED]> [070515 11:07]:
> Alternately, have you considered using GNU Screen? That way, if you
> start up mc in it and later SSH in, all you need to do is screen -r
> and you've got it...
Thanks for the introduction to screen, Amy. I installed screen and
printed the man
"Russell L. Harris" <[EMAIL PROTECTED]> wrote:
> * dulev <[EMAIL PROTECTED]> [070515 01:56]:
> > > > > After starting Edith (but not logging in locally), I have been
> > > > > logging into Edith via SSH from Kate. But when I execute mc over
> > > > > the SSH link, the two-panel mc display is corru
* dulev <[EMAIL PROTECTED]> [070515 01:56]:
> > > > After starting Edith (but not logging in locally), I have been
> > > > logging into Edith via SSH from Kate. But when I execute mc over
> > > > the SSH link, the two-panel mc display is corrupted. Instead of
> > > > horizontal and vertical rules
On Fri, Dec 29, 2006 at 10:33:14AM +, Roger Morgan wrote:
> The problem is that I ssh to a server, and then try to run a program that
> requires an X display. I want it to use the X server on my workstation. It
> doesn't. It just does nothing.
>
> Details: Three machines on my LAN are releva
The problem is that I ssh to a server, and then try to run a program that
requires an X display. I want it to use the X server on my workstation. It
doesn't. It just does nothing.
Details: Three machines on my LAN are relevant. Call the one I'm sitting at
O, and the others A and B.
O runs Sar
On Wed, Jan 25, 2006 at 11:49:39AM +0100, Stephane Durieux wrote:
> Hello
>
> I have a problem in a ssh script:
> ssh host << EOF
> for o in /directory/*
> cp -pr /directory/* /other_location
>
> the problem is that variable o isn t created in fact. It seems that the it
> is created
On Wed, Jan 25, 2006 at 11:49:39AM +0100, Stephane Durieux wrote:
> Hello
>
> I have a problem in a ssh script:
> ssh host << EOF
> for o in /directory/*
> cp -pr /directory/* /other_location
That's not the whole script, is it?
You need EOF on a line by itself at the end.
You're
Hello I have a problem in a ssh script: ssh host << EOF for o in /directory/* cp -pr /directory/* /other_location the problem is that variable o isn t created in fact. It seems that the it is created on the remote machine (normal) but cannot be printable on the local. what is the reason
Hello,
I want to make chroot on ssh. My option:
http://chrootssh.sourceforge.net and
http://debian.home-dn.net/sarge/openssh .
After the implementation, when I use /./ in /etc/passwd, I don't can
login locally or remotely. The system returns: Permission denied
(publickey,keyboard-interactive).
I'm using shadow so i guess i need the other config.
Anyway it's working.
Thanks
Pete
--- Stephan Seitz <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 19, 2004 at 06:36:32AM -0700, Pete
> RedHair wrote:
> >It is now working without any problems.
>
> Fine.
>
> >Stephan reported about some changes need
On Mon, Apr 19, 2004 at 06:36:32AM -0700, Pete RedHair wrote:
It is now working without any problems.
Fine.
Stephan reported about some changes needed to do in
the sshd_config, should i keep them, are they to be
You'll need them, if you don't have your passwords in /etc/shadow but
in LDAP or Samba
Yep, it's writen there, thanks for your help.
It is now working without any problems.
Stephan reported about some changes needed to do in
the sshd_config, should i keep them, are they to be
default in sarge ?
Thanks again Colin, and Stephan
Pete
--- Colin Watson <[EMAIL PROTECTED]> wrote:
> On M
On Mon, Apr 19, 2004 at 06:11:07AM -0700, Pete RedHair wrote:
> Thanks for your reply .
>
> I was forgetting putty since it worked fine with woody, however i did
> upgraded putty and now it works ok, even after the changes i made in
> sshd_config which didn't let me login.
>
> Guess i missed the
Thanks for your reply .
I was forgetting putty since it worked fine with
woody, however i did upgraded putty and now it works
ok, even after the changes i made in sshd_config which
didn't let me login.
Guess i missed the problem tracking when i assumed
everything was ok with my old version of put
On Mon, Apr 19, 2004 at 04:43:48AM -0700, Pete RedHair wrote:
> What happens is that i get the usual window when an application
> crashes saying "putty.exe generated errors and is being closed by
> windows, you need to restart the program" (it's something like this i
> had to translate since my win
Sorry.
What happens is that i get the usual window when an
application crashes saying "putty.exe generated errors
and is being closed by windows, you need to restart
the program" (it's something like this i had to
translate since my windows is not english.
Also if i open an ssh connection to a wo
On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote:
> I've upgraded two Debian Woody boxes to "testing" (sarge).
>
> I use putty from a windows 2000 PC to login to these linux boxes, but
> after the upgrade i can't login anymore.
>
> What happens is that after typing the username and pa
I've tried that and now i can't login at all i get
"access denied".
PasswordAuthentication no (was yes)
ChallengeResponseAuthentication yes (was no)
UsePAM yes (was yes)
Could'nt find it on BTS, i'll check again.
Thanks
Pete
--- Stephan Seitz <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 19, 2004 at
On Mon, Apr 19, 2004 at 03:15:44AM -0700, Pete RedHair wrote:
I've upgraded two Debian Woody boxes to "testing"
(sarge).
Is there anything wrong with the new version of the
ssh server or is there anything more i need to do to
get ssh to work ?
Did you find your problem in the BTS? The new ssh uses
I've upgraded two Debian Woody boxes to "testing"
(sarge).
I use putty from a windows 2000 PC to login to these
linux boxes, but after the upgrade i can't login
anymore.
What happens is that after typing the username and
password putty generates errors.
Is there anything wrong with the new versi
On Fri, Feb 21, 2003 at 01:23:45PM +0100, Rudy Gevaert wrote:
> ssh_exchange_identification: Connection closed by remote host
this looks like a hosts.allow or hosts.deny issue on the remote box...
sean
msg32175/pgp0.pgp
Description: PGP signature
Hi,
I was busy closing ports on my server this week, and nmap shows the
following ports are still open:
schamper:/home/rudy# nmap -sS kain.rug.ac.be
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
Interesting ports on kain.rug.ac.be (157.193.88.9):
(The 1552 ports scanned but not shown be
OK, Thank you, I have removed "PARANOID" from the client's
/etc/host.deny and now I can connect. Only scp is not working, but this
seems to be a problem with my ssh installation:
scp file user@indy:~/
jorg@indy's password:
scp: warning: Executing scp1 compatibility.
scp: FATAL: Executing ssh1 in
also sprach Joerg Johannes <[EMAIL PROTECTED]> [2002.09.09.1636 +0200]:
> Hmm, OK. I have an alias set in /etc/hosts
show it!
> If I do ssh indy
> I get the above error, when I do ssh real.silly.long.host.name
> I get connected without problem.
what's the output of
ping -nc1 indy | head -1
On Mon, Sep 09, 2002 at 09:40:13AM +0200, martin f krafft wrote:
> also sprach Joerg Johannes <[EMAIL PROTECTED]> [2002.09.09.0939 +0200]:
> > What does it mean when a ssh host tells me
> >
> > ssh_exchange_identification: read: Connection reset by peer
>
> what's the output of
>
> host
>
>
also sprach Joerg Johannes <[EMAIL PROTECTED]> [2002.09.09.0939 +0200]:
> What does it mean when a ssh host tells me
>
> ssh_exchange_identification: read: Connection reset by peer
what's the output of
host
host
if they don't match, then the PARANOID setting in
/etc/hosts.{allow,deny} i
Hi List
What does it mean when a ssh host tells me
ssh_exchange_identification: read: Connection reset by peer
???
It worked until some days ago, and I did not change configuration on
either machine. The host is an sgi running OpenSsh, and me (client), I'm
running
ssh3.4p1-2
On Sat, 26 Jan 2002 23:26:34 -0300
Javier Sieben <[EMAIL PROTECTED]> wrote:
>
> Hello All
>
> I'm with a strange problem. I have two Debian boxes (the first
> is called primer and the second is called segundo under anillo.org.ar
> domain). I can connect via ssh from primer to segundo, but
Hello All
I'm with a strange problem. I have two Debian boxes (the first
is called primer and the second is called segundo under anillo.org.ar
domain). I can connect via ssh from primer to segundo, but can't from
segundo to primer. The configs are the same in both boxes.
The out
I have a problem that just popped up since an "update".
I have a "backup" procedure that runs from one box to another,
piping via ssh.
What appears to happen is that when the remote side (the debian
box) has written 10240 bytes, it just dies. 10240 bytes
exactly, every time.
I've included
Quoting Brian Nelson <[EMAIL PROTECTED]>:
Hi Brian,
I usually get that message when rsync isn't installed
on my "remote" computer.
Perhaps double check rsync is installed on both machines.
Using ssh with rsync is cool.
I usually setup a seperate key to go along with ssh and rsync.
The key created
"nate" <[EMAIL PROTECTED]> writes:
> Brian Nelson said:
> > I'm trying to run rsync over ssh with a command such as:
> >
> > $ rsync -v -e ssh some_file another_computer:.
> >
> > or any other permutation of the command, but I get the
> > not-so-verbose error message:
> >
> > bash: rsync: command
Brian Nelson said:
> I'm trying to run rsync over ssh with a command such as:
>
> $ rsync -v -e ssh some_file another_computer:.
>
> or any other permutation of the command, but I get the
> not-so-verbose error message:
>
> bash: rsync: command not found
> unexpected EOF in read_timeout
sounds lik
I'm trying to run rsync over ssh with a command such as:
$ rsync -v -e ssh some_file another_computer:.
or any other permutation of the command, but I get the not-so-verbose
error message:
bash: rsync: command not found
unexpected EOF in read_timeout
Presumably, the command in question is ssh,
* Rodolf Sarimanok ([EMAIL PROTECTED]) spake thusly:
> Hi,
> Can someone xplain me why, when I do ssh, I have this message? How to solve?
>
> "Disconnecting: Bad packet length 1349676916"
Protocol mismatch, usually. Try "ssh -1" and "ssh -2". Also make sure
that you have "Protocols 2,1" in /etc/s
1 - 100 of 126 matches
Mail list logo
