diff options
| author | iphydf <iphydf@users.noreply.github.com> | 2016-12-14 09:17:19 +0000 |
|---|---|---|
| committer | iphydf <iphydf@users.noreply.github.com> | 2016-12-14 11:35:43 +0000 |
| commit | bbdd7982563b7d8f89fcd3b7297b5fbdf21fc57f (patch) | |
| tree | ed7c949449b8ca3cae0b74299a328872af0092ec /toxencryptsave | |
| parent | 22fca79ad76147a07fcb3950a0a6ec1578ecc492 (diff) | |
Fix unresolved reference in toxencryptsave API.
Also, make sure this won't happen again by checking for it in
format-source.
Diffstat (limited to 'toxencryptsave')
| -rw-r--r-- | toxencryptsave/toxencryptsave.api.h | 2 | ||||
| -rw-r--r-- | toxencryptsave/toxencryptsave.h | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/toxencryptsave/toxencryptsave.api.h b/toxencryptsave/toxencryptsave.api.h index 20b8da06..93456235 100644 --- a/toxencryptsave/toxencryptsave.api.h +++ b/toxencryptsave/toxencryptsave.api.h | |||
| @@ -49,7 +49,7 @@ extern "C" { | |||
| 49 | * prefer the advanced API and reuse pass-key objects. | 49 | * prefer the advanced API and reuse pass-key objects. |
| 50 | * | 50 | * |
| 51 | * To use the second part, first derive an encryption key from a password with | 51 | * To use the second part, first derive an encryption key from a password with |
| 52 | * ${pass_Key.derive}, then use the derived key to encrypt the data. | 52 | * ${tox.pass_Key.derive}, then use the derived key to encrypt the data. |
| 53 | * | 53 | * |
| 54 | * The encrypted data is prepended with a magic number, to aid validity | 54 | * The encrypted data is prepended with a magic number, to aid validity |
| 55 | * checking (no guarantees are made of course). Any data to be decrypted must | 55 | * checking (no guarantees are made of course). Any data to be decrypted must |
diff --git a/toxencryptsave/toxencryptsave.h b/toxencryptsave/toxencryptsave.h index 584efaed..de53273e 100644 --- a/toxencryptsave/toxencryptsave.h +++ b/toxencryptsave/toxencryptsave.h | |||
| @@ -48,7 +48,7 @@ extern "C" { | |||
| 48 | * prefer the advanced API and reuse pass-key objects. | 48 | * prefer the advanced API and reuse pass-key objects. |
| 49 | * | 49 | * |
| 50 | * To use the second part, first derive an encryption key from a password with | 50 | * To use the second part, first derive an encryption key from a password with |
| 51 | * <unresolved>, then use the derived key to encrypt the data. | 51 | * tox_pass_key_derive, then use the derived key to encrypt the data. |
| 52 | * | 52 | * |
| 53 | * The encrypted data is prepended with a magic number, to aid validity | 53 | * The encrypted data is prepended with a magic number, to aid validity |
| 54 | * checking (no guarantees are made of course). Any data to be decrypted must | 54 | * checking (no guarantees are made of course). Any data to be decrypted must |