I would be seriously swamped if I didn't have cfengine setup to do a lot of the grunt work (ie. patches, copying config files around, checking that daemons are still runnning, etc).
When I need to do one-off things, I generally turn to fanterm and/or shell scripts.
I knew perl once. then learned to use bash more effectively.
CVS, awk, sort, vim all necessary tools in my toolbox.
I've seen tools that brute-force 64bit, but can only do a dictionary attack on 128. I would guess that someone has written a brute force tool for 128, but it is a larger keyspace to check.
I do agree with you though that anyone that cares for security should be running some sort of a vpn over the wireless link.
Re:disable system services on startup
on
Linux Tuning Tricks?
·
· Score: 2, Informative
Actually, the K* scripts are run when you leave that runlevel. Your shutdown will be slower as the system is trying to shutdown daemons that aren't running.
I usually move the scripts from S* to s*. This way I can tell quite easily what I've disabled by hand.
The numbers are 12345-1 for rev 1, 12345-2 for rev 2, etc, etc. The dash helps keep the confusion down; periods sometimes get lost in frantic searches for the right patch.
This is cool because you don't have to remember that patches 294845 and 392843 and 492835 and 420293 are kernel patches. You just remember that patch 452593 is the kernel patch for Foo version 2. Incremental patch revisions provide better fixes, or similar fixes that show up elsewhere.
Makes a hell of a lot of sense once you get used to it.
Its been a while since I have really looked at the compile-time options for samba, but I believe there is a --with-netatalk option that may minimize some of the locking issues between the two packages.
I have been running a server with Apache-ssl for several years now w/o any problems. The patch does change some program names (ie httpd -> httpsd, apachectl -> httpsdctl) which can break some apache scripts.
The biggest difference I remember hearing between mod_ssl and Apache-SSL is that mod_ssl team was more focused on new features and the Apache-SSL team was more focused on stability/speed. Things may have changed in the last year or so however.
Both Apache/SSL solutions use the OpenSSL programs and libraries to generate certificates. I use Verisign as my CA. Never had a problem with either the initial request renewed certificates.
Slashdot Mirror
I would be seriously swamped if I didn't have cfengine setup to do a lot of the grunt work (ie. patches, copying config files around, checking that daemons are still runnning, etc).
When I need to do one-off things, I generally turn to fanterm and/or shell scripts.
I knew perl once. then learned to use bash more effectively.
CVS, awk, sort, vim all necessary tools in my toolbox.
I do agree with you though that anyone that cares for security should be running some sort of a vpn over the wireless link.
http://groups.yahoo.com/group/bookwormsgatheringsp ot/
I usually move the scripts from S* to s*. This way I can tell quite easily what I've disabled by hand.
The numbers are 12345-1 for rev 1, 12345-2 for rev 2, etc, etc. The dash helps keep the confusion down; periods sometimes get lost in frantic searches for the right patch.
This is cool because you don't have to remember that patches 294845 and 392843 and 492835 and 420293 are kernel patches. You just remember that patch 452593 is the kernel patch for Foo version 2. Incremental patch revisions provide better fixes, or similar fixes that show up elsewhere.
Makes a hell of a lot of sense once you get used to it.
Its been a while since I have really looked at the compile-time options for samba, but I believe there is a --with-netatalk option that may minimize some of the locking issues between the two packages.
The biggest difference I remember hearing between mod_ssl and Apache-SSL is that mod_ssl team was more focused on new features and the Apache-SSL team was more focused on stability/speed. Things may have changed in the last year or so however.
Both Apache/SSL solutions use the OpenSSL programs and libraries to generate certificates. I use Verisign as my CA. Never had a problem with either the initial request renewed certificates.