Hi there,
This one time, Dale Amon wrote:
> Perhaps, but one should always change
>
> Protocol 1,2
>
> to just
>
> Protocol 2
>
> in both ssh_config and sshd_config. If someone
> only speaks P1, you really don't want to talk
> to them at all.
There's no debating that. The article
On Wed, Jul 31, 2002 at 08:12:00AM -0700, Anne Carasik wrote:
> Here's the link to the Phrack article.
>
> http://www.phrack.org/show.php?p=59&a=11
>
> It's a really good read, and what they are
> suggesting would affect the entire implementation
> of SSH, not just OpenSSH or SSH.com.
>
> It can
Here's the link to the Phrack article.
http://www.phrack.org/show.php?p=59&a=11
It's a really good read, and what they are
suggesting would affect the entire implementation
of SSH, not just OpenSSH or SSH.com.
It can't be fixed from the config file, as
they are not talking about the protocols 1
On Wed, Jul 31, 2002 at 01:58:59PM +0200, Robert van der Meulen wrote:
>
> Quoting Jay Kline ([EMAIL PROTECTED]):
> > I maay be wrong, but dont the SSH clients need that banner to be able to
> > identify what version to use?
>
> Yes; the major/minor combination tells the client which protocol ve
Quoting Jay Kline ([EMAIL PROTECTED]):
> I maay be wrong, but dont the SSH clients need that banner to be able to
> identify what version to use?
Yes; the major/minor combination tells the client which protocol versions
can be used. The latest phrack has some interesting information about that
a
Quoting Jay Kline <[EMAIL PROTECTED]>:
> > For OpenSSH you can change it during compile time ...
>
> I maay be wrong, but dont the SSH clients need that banner to be able to
> identify what version to use?
>
SSH-2.0-OpenSSH_3.1p1_AtHome_SecurID
I assume that it only uses the first phrase (SS
On Friday 26 July 2002 08:06 am, Jeffrey Koetsier wrote:
> It depends per software package.
>
> For OpenSSH you can change it during compile time ...
I maay be wrong, but dont the SSH clients need that banner to be able to
identify what version to use?
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
e a generic way to block telnet information (runing woody) - if i
> telnet to our
> mailserver at port 110 then i am told both the version of our pop3 handler
> and what local ip it is running on, the same goes for port 22 and 25
> (where ssh and postfix).
>
> Thanks
>
&g
Hi.
Is there a generic way to block telnet information (runing woody) - if i
telnet to our
mailserver at port 110 then i am told both the version of our pop3 handler
and what local ip it is running on, the same goes for port 22 and 25
(where ssh and postfix).
Thanks
___
Mvh./Yours sincerely
9 matches
Mail list logo
