full-disclosure - Possible First Crypto Virus Definitely Discovered!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <200406081246.12693.james.bliss@comcast.net>
From: james.bliss at comcast.net (James Bliss)
Subject: Possible First Crypto Virus Definitely Discovered!

> Whatever ssl is, I don't know but it's using the so-called "ssl" port on
> the web servers. I don't think it has anything to do with whatever ssl
> was back in the old days of UNIX. It has a lower port number and that
> means it's an older port! Probably from the 1970s!
>
> Besides, why should I see any encrypted traffic on any port other than
> SSH? I don't expect to see encryption on anything other than the SSH
> port 22 (which is a very old port).

You are kidding, right?  SSL = Secured Sockets Layer.  It probably includes 
encryption.  It would not be too _SECURE_ if it was plain text.

SSH = Secured Shell

Notice the use of _SECURED_ in both their names?