Rename the hybrid_encrypt/decrypt functions; label them as dangerous
We need to keep these around for TAP and old-style hidden services, but they're obsolete, and we shouldn't encourage anyone to use them. So I've added "obsolete" to their names, and a comment explaining what the problem is. Closes ticket 23026.
Showing
- changes/bug23026 4 additions, 0 deletionschanges/bug23026
- src/common/crypto.c 11 additions, 4 deletionssrc/common/crypto.c
- src/common/crypto.h 2 additions, 2 deletionssrc/common/crypto.h
- src/or/onion_tap.c 2 additions, 2 deletionssrc/or/onion_tap.c
- src/or/rendclient.c 2 additions, 2 deletionssrc/or/rendclient.c
- src/or/rendservice.c 1 addition, 1 deletionsrc/or/rendservice.c
- src/test/test.c 2 additions, 1 deletionsrc/test/test.c
- src/test/test_crypto.c 2 additions, 2 deletionssrc/test/test_crypto.c
- src/test/test_introduce.c 2 additions, 2 deletionssrc/test/test_introduce.c
Loading
Please register or sign in to comment