Yes, back when I lived in Tampa, FL. Our amateur radio packet network was interlinked where there were no RF paths, over the internet, I at one point had buckets full of attempts to the point that we even called the FBI about it, and since the device was used as part of the emergency system, even more reason to do so, they asked to be sent logs and any other info we could send them, which they did. This was back 10 years ago. I was already getting ready to change the port number, the FBI agent I was working with on it also told me to do the same but asked that we "hold off" to get a few more logs which we did, as soon as we changed the port, it was massive peace and quiet. To me using a non-standard port for SSH in this day and age when you can just makes sense. Oh yes the agent told me that they had learned a lot from those logs but that they could not say much, back then most of them were Chinese.
On Sat, Dec 27, 2014 at 10:09 AM, Rich Shepard <[email protected]> wrote: > On Tue, 23 Dec 2014, Jim Garrison wrote: > > > I never get ANY ssh cracking attempts by the simple expedient of running > > SSH on a non-standard port. I used to get hundreds of attempts a day but > > reconfigured SSH to listen on a specific port above 20000 and now never > > see any attempts. > > Jim, > > Works like a charm; don't know why I didn't do this years ago. > > Thanks, > > Rich > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > -- Chuck Hast -- KP4DJT -- Glass, five thousand years of history and getting better. The only container material that the USDA gives blanket approval on. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
