On Sun, 21 Jun 2009 00:17:30 +0300 (AST) fabian wrote: > The problem was solved after using a non standard port for ssh. You haven't solved the problem, because you haven't solved this problem: > but wonder how it was gettin through my firewall You should be finding this out. Traffic of unknown origin is a bad thing. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: ssh security
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: ssh security
- From: Frank Cox <theatre@xxxxxxxxxxx>
- Date: Sat, 20 Jun 2009 15:35:54 -0600
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <55a06c61748974c9e0ddbc6a547b139e.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
- Organization: Melville Theatre
- References: <284d4979339219c87a541981179ec01e.squirrel@xxxxxxxxxxxxxxxxxxxxxx> <20090619170147.GA31402@xxxxxxxxxxxxxxxxxxxx> <570458.34395.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <55a06c61748974c9e0ddbc6a547b139e.squirrel@xxxxxxxxxxxxxxxxxxxxxx>
- References:
- ssh security
- From: Cisco-Education
- Re: ssh security
- From: Bill Campbell
- Re: ssh security
- From: Linux Advocate
- Re: ssh security
- From: fabian
- ssh security
- Prev by Date: Re: ssh security
- Next by Date: Re: card reader not responding
- Previous by thread: Re: ssh security
- Next by thread: Re: ssh security
- Index(es):
 |