| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hiya Anthony, |
| 5 |
First off, it certainly sounds interesting and making it more |
| 6 |
accessible (simple ebuild setup and so on) seems like a good plan even |
| 7 |
if it doesn't get picked up officially. The best way to start |
| 8 |
development would probably be an overlay, which will make it easy to |
| 9 |
bring into the tree if/when a developer wants to pick it up officially. |
| 10 |
You might also want to look into integrating your "ramification" |
| 11 |
process into catalyst the gentoo release building tool (the release |
| 12 |
engineering team can probably tell you more about that than I can). |
| 13 |
Also, reading the TinHat front page and mention of ram dumping, you |
| 14 |
might be interested in [2]. It suggests not leaving the key in RAM when |
| 15 |
it's not necessary, but shoving it into the CPU cache... |
| 16 |
Mike 5:) |
| 17 |
|
| 18 |
[1] http://www.gentoo.org/proj/en/releng/catalyst/ |
| 19 |
[2] http://frozencache.blogspot.com/ |
| 20 |
-----BEGIN PGP SIGNATURE----- |
| 21 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 22 |
|
| 23 |
iEYEARECAAYFAkmEcQgACgkQu7rWomwgFXp+3ACghLB+686vqMLqcEm9Ye3gM1JN |
| 24 |
KKQAoJ4R3dyx5KcVeg6+9OugRsCA0nha |
| 25 |
=MCQf |
| 26 |
-----END PGP SIGNATURE----- |
Archives