[dundee] Linux Security & Botnets
Lee Hughes
toxicnaan at yahoo.co.uk
Fri Jan 25 23:23:20 GMT 2008
you forgot to mention, stick in a lead box and throw it into the sea. ;-)
passwords , should be something you know, and something you own?
I like to think they should be some you are, but I don't want my eye's
gouged out, my dna cloned, or my fingers cut off, or computer invading
my privacy even more.
you've got to have open ports for servers, public servers without open
ports.... not much use are they.
rookit are rare(ish) as the level of expertise to write one is high. don't think
close source o/s rootkits are any harder to write , they just take longer
to figure out, and are probably of more value because only a handful of people
actually know what the kernel is supposed to be doing.
We need a whole new thinking on computer hardware, in fact linux on bios
would be interesting, because you initial kernel can be loaded from a secure chip.
nice.
All the solutions for boot integrity seem to focus on DRM for client machines,when in fact it's more appropriate for servers to have this
technology.
If something becomes common , it becomes a target. you want to be
secure? run you web server on old amiga, or c64, exploits for these
platforms are somewhat hard to d/l from internet hacking sites.
Laters
Lee
Arron M Finnon <afinnon at googlemail.com> wrote: Well i think that the majority of my ethical hacking brothers and
sisters will tell you, that our view on securing your system is to
follow these simple steps;
Firstly pull the networking cable out of your machine
Secondly leave it that way
thirdly for added safety you may choose to cut all the power cables to
your computer.
All that the above is jokingly said, the truth is security is more in
the mind of the user than in the keystrokes of your hacker. No matter
how much you spend on security, no matter how strong you think you are,
if you still write your password on the post-it note on your desk, the
cleaners always going to have access. The changing of passwords on a
regular basis, i suppose can be advised, however once access has been
obtained the backdoor will always be open so to speak. However security
is done by action, and the more steps you take to be secure the securer
your ultimately going to be. The reality of it is, that by default the
services we want our computers and networks to have require the systems
to open ports, and other means of access.
Rootkits suck for the people that are affected, however from a geek
stand point they do some amazing things and what they are capable of
now, would scare the most ardent of security minded users. However the
true problem with rootkit research is by default rootkits are hard to
find, no one admits to having been affected, and few writers will
release them, due to lets just say losing their commercial advantage.
I now that you guys will have a wealth of experience on this subject and
i'm sure another EH will say something completely different to me, good
job there's a few of us on the list.
f1Nux hashing your salts, and signing off
_______________________________________________
dundee GNU/Linux Users Group mailing list
dundee at lists.lug.org.uk http://dundee.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/dundee
Chat on IRC, #tlug on dundee.lug.org.uk
---------------------------------
Support the World Aids Awareness campaign this month with Yahoo! for Good
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.lug.org.uk/pipermail/dundee/attachments/20080125/8be04b73/attachment.html
More information about the dundee
mailing list