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
Hi,
> Hi, I just tried to 'lh display', but it always ends in conventional
> memory (code, codepages are perhaps in XMS):
...
> I myself explain this that the UPX-ed program is probably going to UMB,
> but after its decompression, its resident part will no longer fit there
> for some reason and i
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://
