On Tue, 2 Jan 2018, Dan Schmidt wrote:
Drat! Somebody finally caught onto to my evil plan to covertly make Linux
servers insecure! Foiled again! You will this one, Tom, but I'll be
back!! Oh, I'LL BE BACK!!
You can almost hear him adjust his monocle while petting a white persian
cat. ;)
Drat! Somebody finally caught onto to my evil plan to covertly make Linux
servers insecure! Foiled again! You will this one, Tom, but I'll be
back!! Oh, I'LL BE BACK!!
On Tue, Jan 2, 2018 at 9:03 AM, Tom Ehlert wrote:
>
> > We did talk at length about it almost exactly a year ago. The tldr
> We did talk at length about it almost exactly a year ago. The tldr
> version is that you would need ssh2d386 and you have to have access
> to modify the ssh config on the server to support older ciphers.
there are GOOD reasons to not allow outdated protocols to be used.
on what planet have yo
> On 12/31/2017 10:47 AM, Robert Riebisch wrote:
>> From SSHDOS source code:
>> ###
>>if(remote_major != 1 && remote_minor == 0)
>> fatal("Unsupported remote protocol version\n");
>> ###
> What a weird check. So version 2.1 would work? Shouldn't the check be
not only a weird and buggy
We did talk at length about it almost exactly a year ago. The tldr version
is that you would need ssh2d386 and you have to have access to modify the
ssh config on the server to support older ciphers. All my attempts to get
a decent C coder interested in updating the project have failed.
https://
Hi,
On Sun, Dec 31, 2017 at 5:27 PM, Jerome Shidel wrote:
>
> Anyhow, I recall seeing a thread earlier discussing something similar. At
> least, I think it was similar.
> I was not very interested at the time and kinda only skimmed it. But, if I
> remember what I half glimpsed,
> it involved so
> Are you sure?
> Binaries are still from 2003 (sshdos.zip) or 2006 (ssh2dos.zip).
I am only sure that one package reports itself as SSHDOS v0.95, and it is not
the package that shipped with FreeDOS 1.2.
But, I haven’t used either. I don’t want to speculate on what the differences
between them
Hi Jerome,
> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.2/pkg-html/group-net.html
>
> At present, FDIMPLES is an offline only package manager and several
> packages (including sshdos & ssh2dos) have been updated since the
> release of FreeDOS 1.2.
Are you sure?
Binari
Hi David,
>> From SSHDOS source code:
>> ###
>>if(remote_major != 1 && remote_minor == 0)
>> fatal("Unsupported remote protocol version\n");
>> ###
>
> What a weird check. So version 2.1 would work? Shouldn't the check be
>
> if (!(remote_major == 1 && remote_minor == 0))
>
> ?
Not su
On 12/31/2017 10:47 AM, Robert Riebisch wrote:
> From SSHDOS source code:
> ###
>if(remote_major != 1 && remote_minor == 0)
> fatal("Unsupported remote protocol version\n");
> ###
What a weird check. So version 2.1 would work? Shouldn't the check be
if (!(remote_major == 1 && remote_mi
First,
I would suggest visiting the Official FreeDOS Online Software Repository.
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.2/pkg-html/group-net.html
At present, FDIMPLES is an offline only package manager and several packages
(including sshdos & ssh2dos) have been
Hi czezz,
> In both cases, connection fails and in the end I get message:
> "Unsupported remote protocol version".
>From SSHDOS source code:
###
if(remote_major != 1 && remote_minor == 0)
fatal("Unsupported remote protocol version\n");
###
So, the remote server has to support 1.0.
1)
Hi, I have installed SSHDOS package over FDIMPLES > Networkig > SSHDOS
To connect to my SSH server I executed this: sshdos.exe user 192.168.1.108 OR
sshd386.exe user 192.168.1.108 In both cases, connection fails and in the
end I get message: "Unsupported remote protocol version". I have
13 matches
Mail list logo
