full-disclosure - Where to start

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1078831388.23556.99.camel@adesk>
From: full-disclosure at illuminated.nl (Aschwin Wesselius)
Subject: Where to start

Hello,

First appologies for having trouble doing something simple as sending
e-mail. Evolution is new for me.......

Now I'm on this list, I think I could ask you people a question (or
two)....

Does a good security-officer have to know everything about every hole? I
myself don't think so, but where do people start?

If I see lists and forums about network-security it seems that everybody
knows a lot and has a huge reference base. Is this true?

I want to learn more about security stuff, but I can't find the real
basics to build upon anywhere. When there are posts on lists they
presume that everybody has a certain knowledge level and are aware of
best practices. But is this true?

Just because there are discussions, it seems that there is not one
overall and central way of keeping track of evolving issues. How do
people keep track easily with up to date best practices and not get
distracted by "old" advisory?

Any comments are welcome.

Aschwin Wesselius