-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just some quick thoughts on this:
> 2. root key & signing subkey of EITHER: 2.1. DSA, 1024 or 2048 bits
> 2.2. RSA, >=2048 bits
I don't really agree. From your own link
(https://we.riseup.net/riseuplabs+paow/openpgp-best-practices#dont-use-pgp-mit-ed
Hi,
> Thanks Matt!
Thanks, too! :) I've used MIPS before, and might set up an old octane
again...so thanks for your effort! :)
Greetings,
Craig
Hi,
yes, it's no fun to update oldish gentoo Systems - especially ones that
should only receive security updates.
> My bugbear at the moment, is often a package is broken for more than one
> reason in my situation, and I find myself having to manhandle the
> package lists generated by the above t
Hi,
>> Would be great to have a few people test open-iscsi 2.0.872 before
>> moving it from overlay betagarden to the main tree. [...]
> In the good old days, stuff like this would just be added to the tree
> either hard masked or not keyworded, or both.
>
> Why not still do that?
+1
I had t
Hi list,
seeing Donnie link to a GSOC page on en.gentoo-wiki.com, I was wondering
about the status of our own, gentoo-hosted wiki. When gentoo-wiki.com
had its major failure, I was very frustrated and thus have some concerns
about planning GSOC or anything else there.
There are 17 people listed o
02.05.2010 17:23, Krzysztof Pawlik wrote:
> Interesting... to me that's not only stupid but also kinda useless - there's
> no
> difference between brute-forcing a password for user named 'foo' or 'root' -
> user name doesn't matter much.
> It's better to disable password-based remote login altoget
Hi,
in some environments you have to rename "root" to something else, just
to be compliant to a (maybe dumb) security policy. This might be the
case for PCI, and as far as I remember, it is necessary (not just
"recommended") for a BSI Grundschutz certification (meaning something
like "basic securi
