Re: annoying brute force attack attempt using ssh

• To: "For users of Fedora" <fedora-list@xxxxxxxxxx>
• Subject: Re: annoying brute force attack attempt using ssh
• From: "Bill Crawford" <billcrawford1970@xxxxxxxxx>
• Date: Thu, 15 May 2008 12:31:53 +0100
• In-reply-to: <alpine.LFD.1.10.0805151221500.16737@xxxxxxxxxxxxxxxxxxxx>
• References: <alpine.LFD.1.10.0805151207590.16737@xxxxxxxxxxxxxxxxxxxx> <92d7c0020805150416o759718c8j1d5976d6459d449f@xxxxxxxxxxxxxx> <544eb990805150419i19e9c510o1a9c69cb290ed1d3@xxxxxxxxxxxxxx> <alpine.LFD.1.10.0805151221500.16737@xxxxxxxxxxxxxxxxxxxx>
• Reply-to: For users of Fedora <fedora-list@xxxxxxxxxx>

2008/5/15 Scott van Looy <scott@xxxxxxxxxxx>:

>> You appended the rule, AFTER the ones which allow ssh through?

> That should work though IIRC...I'm stopping a specific IP from connecting

If you've already allowed it, that rule is too late to stop it. One of
the other replies pointed out a better way (use -I instead of -A).

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

• Follow-Ups:
  • Re: annoying brute force attack attempt using ssh
    • From: Scott van Looy

• References:
  • annoying brute force attack attempt using ssh
    • From: Scott van Looy
  • Re: annoying brute force attack attempt using ssh
    • From: Łukasz Jagiełło
  • Re: annoying brute force attack attempt using ssh
    • From: Bill Crawford
  • Re: annoying brute force attack attempt using ssh
    • From: Scott van Looy

• Prev by Date: Re: annoying brute force attack attempt using ssh
• Next by Date: Re: annoying brute force attack attempt using ssh
• Previous by thread: Re: annoying brute force attack attempt using ssh
• Next by thread: Re: annoying brute force attack attempt using ssh
• Index(es):
  • Date
  • Thread