David Mackintosh (david.macki...@xdroop.com)

On Tue, Oct 14, 2008 at 11:13:18PM +0100, Karanbir Singh wrote:

> And Just to remind everyone that no, this is still not a general
> conversation about stuff list.

How off-topic is it to ask precisely what is on-topic for this list
if questions and discussions of the included components belong on the
support mechanisms for those individual parts, and the rest (ie anaconda
and friends) probably belongs in the upstream vendor's forums?

What does that leave?  The color of the logo?

(I like the blue.)

Strictly speaking, yes; however in practice, the number of bots (or,
indeed, external users who are not me) who the magic web page to hit
(my actual page is not named as the example on the web page is!)
before attacking the ssh connection is zero; therefore since the goal
was to prevent stupid robots from brute-forcing my ssh and filling my
logs, it isn't necessary.  

I mean, strictly speaking you'd next have to insist on a proper SSL
connection to the web server, otherwise you are at risk of someone
sniffing the username and password used in the .htaccess process.
And then after that, you'd have to insist on some kind of security on
the remote system to ensure that your passwords are not being
captured.  Etc, etc.  

This is what I do.

http://wiki.xdroop.com/space/Linux/Limited+SSH+Access

This is pretty much what I do.  I also keep stock "reference" images
for each OS I support and copy from the reference image every time I
need to deploy a new VM.

I like the idea of Xen, but the documentation is a little thin
especially when it comes to installing useful things like Windows
VMs; I don't have the time to solve the problem properly, and I hope
that in a year or two I can change this.

On Tue, Feb 12, 2008 at 10:26:54AM -0800, Tim Alberts wrote:
> So how do I do this?

edit /etc/sysctl.conf

> option routers 10.0.0.1 10.0.0.2;

Not as far as I know.