a020c28ea6
core: update copyright dates
2015-01-01 09:23:23 +01:00
44de5bac65
core: update message displayed when passphrase is not set on /secure buffer
2014-06-28 14:50:15 +02:00
980a9abcfd
core: do not display content of passphrase on /secure buffer
2014-06-28 13:18:16 +02:00
76469269ce
core: fix uninitialized value in functions secure_{encrypt|decrypt}_data (in case of insufficient memory)
2014-02-22 20:20:57 +01:00
892aa79fb5
core: update copyright dates
2014-01-01 00:14:12 +01:00
1fa4701ed0
core: free secured data on exit
2013-11-23 16:29:51 +01:00
1417b7a823
core: remove unneeded warning when read of sec.conf fails (another warning is already displayed)
2013-11-09 10:13:09 +01:00
43e3ff3b1a
core: change the message displayed when passphrase is not given on startup
2013-08-02 23:18:09 +02:00
5a07051f20
core: remove use of function gcry_kdf_derive so that it compiles with libgcrypt < 1.5.0
...
The key built with salt + passphrase has changed, so old encrypted data
in file sec.conf can not be decrypted with this new version.
2013-08-02 23:15:21 +02:00
26fcc66953
core: update translations
2013-08-02 20:16:47 +02:00
351674699c
core: in case of empty passphrase, keep encrypted data in memory until the user runs /secure decrypt (with the good passphrase)
...
If user gives no passphrase (for example one space when prompted), the encrypted
data read in sec.conf will be stored in a separate hashtable.
While this hashtable contains something, it is not allowed to do any operation
on passphrase or secured data (and it is not allowed to reload sec.conf).
The user can decrypt data with /secure decrypt <passphrase>.
2013-07-30 12:16:44 +02:00
b3923b65f1
core: use variable "items_count" directly from hashtable without calling function hashtable_get_integer
2013-07-30 10:10:37 +02:00
a668775ae3
core: add option sec.crypt.passphrase_file
2013-07-28 10:59:00 +02:00
a490195032
core: add secured data with optional encryption in file sec.conf
2013-07-27 12:57:08 +02:00
Sébastien Helleu