Date: Sun, 28 Jun 2009 07:03:48 +0200 From: Polytropon <freebsd@edvax.de> To: Daniel Underwood <djuatdelta@gmail.com> Cc: Jos Chrispijn <jos@webrz.net>, freebsd-questions@freebsd.org, Jon Radel <jon@radel.com> Subject: Re: Best practices for securing SSH server Message-ID: <20090628070348.8a07299b.freebsd@edvax.de> In-Reply-To: <b6c05a470906271817r1fac21dfrfcea512d8ed5f16c@mail.gmail.com> References: <b6c05a470906221816l4001b92cu82270632440ee8a@mail.gmail.com> <4A4639B0.8080602@webrz.net> <4A467089.1040404@radel.com> <b6c05a470906271817r1fac21dfrfcea512d8ed5f16c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 27 Jun 2009 21:17:11 -0400, Daniel Underwood <djuatdelta@gmail.com> wrote: > Exactly. For example, the "server" in question is a desktop machine > at work. I regularly see transfer rates of 13MB/s. It's at a major > university, which is by itself another high-risk factor, precisely > because there are so many (often weakly protected) high-speed > connections. That's a valid point, and I'd like to add that there is some consideration: Servers are usually protected with proper means. This goes especially for UNIX servers. Desktops, on the other hand, can more easily be taken over (especially non-UNIX machines), so if an attacker got his foot inside a network, it's very useful to him. There are even trading platforms where criminals buy and sell whole networks of compromised PCs. Of course, everything happening inside such networks should be seen as what it is: a threat to security. Just imagine some "clever guy" uses telnet inside such a network to configure the server... -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090628070348.8a07299b.freebsd>