1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Am 14.05.2014 02:39, schrieb Neil Bothwick: |
5 |
|
6 |
>> Doesn't that screw up the whole idea of checksumming etc ? |
7 |
> |
8 |
> Not to my mind. The bits are recorded and checksummed, that's what |
9 |
> matters. If a bit on a platter is flipped, the decrypted bits will |
10 |
> also change. |
11 |
|
12 |
But then the "container" of the btrfs would be corrupted, right? |
13 |
|
14 |
>> In my understanding the FS (=btrfs or zfs) should have the |
15 |
>> direct contact to the "metal" (=hdd/sdd) to be fully able to |
16 |
>> detect bitrot and stuff. |
17 |
> |
18 |
> It is a recommended method of encryption in the BTRFS FAQ. |
19 |
> |
20 |
> https://btrfs.wiki.kernel.org/index.php/FAQ#Does_btrfs_support_encryption.3F |
21 |
> |
22 |
> As btrfs does not support encryption itself, this or ecryptfs are |
23 |
> the only options. |
24 |
|
25 |
Yes, I saw that as well. Will give it a try sometimes soon ... |
26 |
|
27 |
S |
28 |
|
29 |
-----BEGIN PGP SIGNATURE----- |
30 |
Version: GnuPG v2.0.22 (GNU/Linux) |
31 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
32 |
|
33 |
iQIcBAEBAgAGBQJTcyLmAAoJEClcuD1V0PzmV2MP+wWqxS7BhG2RcWgXsDycgstu |
34 |
yosr450brlmx+NRD4PUq47yj+GTsum/9l2WdxAlDZA90f8CaJefnWK9csNLhGBMA |
35 |
BqFT69WNSJEmOJ2l8x2FHZJ1gjyMOQp16q7r0d1G7Asdoubhx/uRSeSjJEnk5gqu |
36 |
UVA77/jbJ1CJSAv4ATnGl67RHWew3KR99VZbbFs7Cr3fjbOZmqWpuSKbf6ZdylHO |
37 |
UatP/sc+ye09sSpUWW5Q4i8v8gF0XC/qy80iPLy84G0+IzDaNaoTfQY3Ff2+u9Nn |
38 |
OAhn8lT/HmMJiJUTp4YeAVjzLIx+Nq2NrAqEoaIqER1sfGH5bh2oK5yiJ+mW/8cQ |
39 |
4OBdcQXoXnDtyQvoT69EELq+vsm5nVi8ibb/msE9r9ImE2FJ+2mHKadFpluBGCnX |
40 |
xApAaxqkX4lPEphpysdlcq9GF1/eSyGRFM/3tDM/vefy9VokjhXHXAbZ2jhfSoTS |
41 |
PfWZpxi8sur3z/s/sIVaqMbLG8IdjOfoGKTgtzoYHVqvtlYxOubbvh52iI58CCL7 |
42 |
0LblkAeOSlk2UITYMV+yF3WB0naRjO41LngwwmxcJyRsJDvrzQkSEvhtWaJ9Qlh5 |
43 |
d/k6f2y/hDrpITLxf5C+I1/mg8WDtmgODczUTlSj+u6NCLMUT0onv5XdsEQXuGX6 |
44 |
7yFDEdLFjPEpGoMIBLO/ |
45 |
=dRlH |
46 |
-----END PGP SIGNATURE----- |