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
>
> $ 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
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
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
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
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
* 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
on Thu, Mar 29, 2001 at 11:59:13AM -0800, Peter Jay Salzman ([EMAIL PROTECTED])
wrote:
> can anyone explain why this isn't working? i'm trying to ssh into
> pc10.cs.ucdavis.edu. here is output using the verbose switch. it looks
> like the remote host hangs up when it's supposed to give the serv
Christian Dysthe <[EMAIL PROTECTED]> writes:
> Hi,
>
> We installed ssh on our new Debian 2.1 (slink) powered server. We do not have
> X
> on it at all, but I get this message every time I log on through ssh. The
> login
> works fine though.
>
> "Warning: Remote host denied X11 forwarding, per
On Mon, 31 May 1999, Christian Dysthe wrote:
> We installed ssh on our new Debian 2.1 (slink) powered server. We do not
> have X on it at all, but I get this message every time I log on through
> ssh. The login works fine though.
>
> "Warning: Remote host denied X11 forwarding, perhaps xauth pro
On Mon, May 31, 1999 at 07:33:57AM -0500, Christian Dysthe wrote:
> Hi,
>
> We installed ssh on our new Debian 2.1 (slink) powered server. We do not have
> X
> on it at all, but I get this message every time I log on through ssh. The
> login
> works fine though.
>
> "Warning: Remote host denied
>> "FK" == Ferenc Kiraly <[EMAIL PROTECTED]> writes:
FK> I have a fresh potato install and I cannot log in to
FK> the machine from a remote host using ssh. I get an
FK> error message like this:
FK> Warning: Remote host failed or refused to allocate a pseudo tty.
Maybe you installed glibc2.1? Ch
On Sun, 16 Aug 1998, George Bonser wrote:
:
: I have two systems that are fresh installs of Debian. I have installed ssh
: on both. I can use ssh to get from one to the other without a password. I
: can not go the other way. Both the /etc/ssh and the ~/.ssh directories and
: the home directo
-BEGIN PGP SIGNED MESSAGE-
On Tue, 13 May 1997, Rick Jones wrote:
> When I telnet to localhost from localhost I get the following:
>
> Trying to negotiate SSL
> [SSL starting]
> [SSL Connected - Cipher RC4-MD5]
> [SSL
> subject=/O=cyberdynamics.com/OU=panther/CN=telnetd/[EMAIL PROTECTED]
I wanted to know if there is a way to clean that up so it's displayed in
some kind of format, instead of being spewed on the screen like that?
I know it's ssltelnet. For some reason I was thinking it came in the ssh
package. Now that you have corrected me I remember it was a seperate
package.
This is generally construed as a feature. It is telling you that a) you
installed SSLtelnet and that b) it has successfully connected to a
system that also has SSLtelnet. What just happened is that public keys
were exchanged and everything from that point on is encrypted. Guess
what? No more pa
Rick Jones wrote:
>
> When I telnet to localhost from localhost I get the following:
>
> Trying to negotiate SSL
> [SSL starting]
> [SSL Connected - Cipher RC4-MD5]
> [SSL
> subject=/O=cyberdynamics.com/OU=panther/CN=telnetd/[EMAIL PROTECTED]
> [SSL
> issuer=/O=cyberdynamics.com/OU=panther/CN=tel
45 matches
Mail list logo
