Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
7
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
Nettle
nettle
Commits
1c7bddc1
Commit
1c7bddc1
authored
Feb 14, 2011
by
Niels Möller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Renamed some macro arguments.
Rev: nettle/nettle-meta.h:1.9
parent
90c7e8d6
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
9 deletions
+9
-9
nettle-meta.h
nettle-meta.h
+9
-9
No files found.
nettle-meta.h
View file @
1c7bddc1
...
...
@@ -52,33 +52,33 @@ struct nettle_cipher
nettle_crypt_func
*
decrypt
;
};
#define _NETTLE_CIPHER(name, NAME, keysize) { \
#name #keysize, \
#define _NETTLE_CIPHER(name, NAME, key
_
size) { \
#name #key
_
size, \
sizeof(struct name##_ctx), \
NAME##_BLOCK_SIZE, \
keysize / 8, \
key
_
size / 8, \
(nettle_set_key_func *) name##_set_key, \
(nettle_set_key_func *) name##_set_key, \
(nettle_crypt_func *) name##_encrypt, \
(nettle_crypt_func *) name##_decrypt, \
}
#define _NETTLE_CIPHER_SEP(name, NAME, keysize) { \
#name #keysize, \
#define _NETTLE_CIPHER_SEP(name, NAME, key
_
size) { \
#name #key
_
size, \
sizeof(struct name##_ctx), \
NAME##_BLOCK_SIZE, \
keysize / 8, \
key
_
size / 8, \
(nettle_set_key_func *) name##_set_encrypt_key, \
(nettle_set_key_func *) name##_set_decrypt_key, \
(nettle_crypt_func *) name##_encrypt, \
(nettle_crypt_func *) name##_decrypt, \
}
#define _NETTLE_CIPHER_SEP_SET_KEY(name, NAME, keysize) {\
#name #keysize, \
#define _NETTLE_CIPHER_SEP_SET_KEY(name, NAME, key
_
size) {\
#name #key
_
size, \
sizeof(struct name##_ctx), \
NAME##_BLOCK_SIZE, \
keysize / 8, \
key
_
size / 8, \
(nettle_set_key_func *) name##_set_encrypt_key, \
(nettle_set_key_func *) name##_set_decrypt_key, \
(nettle_crypt_func *) name##_crypt, \
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment