Re: problem compiling KDar with libdar CVS

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

Denis Corbin wrote:
|[...]


I made a confusion between the API and the command-line syntax. Sorry.
The API has three different arguments :
~   crypto_algo crypto,
~   const std::string & pass,
~   U_32 crypto_size,

the pass and crypto_size arguments are used only if crypto is different
than crypto_none

| Note that the pass has the
| structure described in the dar man page (option -K), "[algo:]pass" .
| where algo is bf, blowfish, scram or scrambling (more will follow I hope
| before the end of november) with "bf" = "blowfish", "scram" =
| "scrambling". If the password must contain a ':' the algo must be
| specified (in the form <algo>:<password_with_column>), so you can safely
| always specify the cypher used.
|
|[...]

here too below, I made the same confusion. To correct the idea, if pass
is an empty string and crypto is not crypto_none then libdar could ask
the password to the user thanks to the user_interaction::pause(...) method.

|
| I like the idea, but throwing an exception is not a reversible operation
| ~ from the stack point of view (you cannot continue execution where it
| has been thrown). I suppose you mean that libdar should rather use a the
| user_interaction::pause(...) method to ask the password to the user, it
| the pass argument was something like "bf:" or "scram:" where just the
| algorithm (the cypher) is given ?
|
|[...]
|
| Cheers,
| Denis.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBigKVpC5CI8gYGlIRAm37AJ0YtxRGIk3npMOplMNqhQGl+hlbDACfbYga
gTjklmjFWYag/+88z7FiUbM=
=LEIW
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click