[dm-crypt] Shared library for cryptsetup

[Björn Påhlsson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Teddy Hogeborn wrote:
> So, here's a possible implementation of this:  The plugin runner is
> changed thus:
> 1. It starts all plugins in strictly alphabetical (strcmp) order.
> 2. If the file name of the current plugin begins with a number:
>    a) Start the plugin with an extra file descriptor, numbered 3,
>       opened, which is a pipe to the plugin runner.
>    b) BEFORE STARTING THE NEXT PLUGIN, read from the plugin's FD 3.
>       There, the plugin is supposed to write, in some well-defined
>       format (like a space-separated list of strings), what resources
>       it will *actually* use, *before* it has begun to use them.
>    c) If a resource conflict is detected, the plugin is killed.
> 
> I'm sure this idea is horrible, but it would solve the stated
> requirements.  Surely we can come up with something better than this
> if we give it some thought.

An alternative, which would be a Debian/Ubuntu-specific solution, could
be to split each current mandos plugin into separate Debian package and
let the "Conflicts:" fields handle any problems.  Basically, the
"mandos-client" package would then be "recommending" all the plugin
packages and "depend" on the "plugin-runner" package. As long both is
depending the Debian/Ubuntu-specific askpass, I think this solution is
the cleanest solution atm.

/Belorn
_______________________________________________
Mandos-Dev mailing list
Mandos-Dev at fukt.bsnet.se
http://mail.fukt.bsnet.se/cgi-bin/mailman/listinfo/mandos-dev

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

iEYEAREDAAYFAkq+GuIACgkQC+Cq+bUsy1JAsgCfVyNAzADhYLhcV/0r6F6q74fk
8mAAoJkwUhbKBc3HOqj5lav9DikUkFHI
=X3NC
-----END PGP SIGNATURE-----