Re: The situation at hand and in the future

[David Masover <ninja@slaphack.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Markus Törnqvist wrote:

| Let's see what the Namesys guys have to say about this, but somehow
| this must be reasonably solved.
|
| Maybe they're sitting on some spec and just haven't had the time
| to tell us.

Hope springs eternal.  Namesys guys?

| Have you, by any chance, had time to look at the code?

| Maybe I should take a vacation and learn C really well and read all
| the Reiser4 code :)

I know C tolerably well, I just need to spend the time learning
reiser4's code.  This is currently impossible.  I'm in high school and
on the verge of failing math (due to laziness, not lack of ability).
However, summer vacation is in a little over a week.

| But it seems possible that you can't do both with the same plugin.
| If it's echo zlib or echo blowfish, unless there's echo zlib+blowfish,
| which would actually be much cooler with symlinks.

Easy:

$ ln -s cryptos/zlib crypto/1
$ ln -s cryptos/blowfish crypto/2

Not as graceful when only one is wanted, though.

| I heard once that using many encryptions may reduce the level of security.
| I don't know if there's any real truth behind this. But if there is,
| maybe it should be impossible to support two cryptos, only a crypto
| and a compression.

I'd rather allow people to be as stupid as they choose, but this would
make the above syntax a bit less ugly:

$ cd ..metas/crypto
$ ln -s ciphers/blowfish cipher
$ echo 256 > bits
$ cd ../compress
$ ln -s codecs/zlib codec
$ echo 9 > level

This allows us to allow things like bzip2 instead.  Default should
probably be zlib, at whatever its default compression level is, on files
which are encrypted.  (Non-encrypted files have no default compression.)

|>question -- can we as users choose what order plugins of the same layer
|>are run?  You'd have to be an idiot to want to encrypt before you
|>compress -- an idiot, or someone who's thought of something we haven't.
|
|
| I'd probably vote for myself being an idiot, but I prefer the terms
| inexperienced and ignorant ;)
|
| But people have a tendency of think of stuff that other people haven't
| so nothing should be discarded straight away.

So maybe we want some sort of way of stacking these?  I'm not sure how
to do this gracefully and still use the above syntax -- I've seen it for
less than a weekend and I'm already attached to it :D

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQLtLeHgHNmZLgCUhAQKrHw//Wnw7IBuPdPiIHpDKvMiMqqiroSnxkZ+q
oiY4zFg+0Gxtzt2+gVww0MQFH+4jjs7EgmrtJ+Bl3XbAEJDTzYADUdVVB8KlCQDa
TCyj3+xNkRLY6+D9iHUTaITnQVQYge4WNQ6QURhmmA/azrc9RvOofrCALl3oiqdG
IozXlw+fhSaSocHsrIsVf7bUB5UjQ5mRyW/y+sGYTcwxq/bw2OdVUzsHwQZ1g9Cy
9J+xqrDDmEF5uoGwXZvES7NXXxdE7N+XAhJAStEBz23PoN3JYM591WuLI18espfr
omvMmVMYFumn49e4dVIq7w0gHBseCSrjhsRTOMgnv+3hlafrjDXQswt247aAtqbY
x9J6sgqpI6tJYkbiT8AHXQHZkF0nzpyfjH2g1L+D6xRkfJsxdi6lNVUQkwwD9tNA
WltES/jbII6/Aie6VXgky3uDJNZT87oVv0mfzre4QzAWUq1XvWN1omIztODnYDpz
5Q4kPOdUT9AgkLI+dbi0l58VjSTAPhGDLIeJoZpqCLJeTP+YVZAwks96o9AqsNl2
SKAR2Ol11Xm2MlHeXeUD81Y4S0dL/wlwz2SaNgex8l2vjaMdm/RCwkyq+9FnMvR6
n5/YX2FF7/raM+T//Uq6NqDE7a6gu+AV4/FO13WNcu5DdNO1SVbH4IoTUqe1Iyxv
oKIoaUdEWY0=
=MuFR
-----END PGP SIGNATURE-----