mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-24 12:23:32 +01:00
18085abfcc
If a tor client gets a descriptor that it can't decrypt, chances are that the onion requires client authorization. If a tor client is configured with client authorization for an onion but decryption fails, it means that the configured keys aren't working anymore. In both cases, we'll log notice the former and log warn the latter and the rest of the decryption errors are now at info level. Two logs statement have been removed because it was redundant and printing the fetched descriptor in the logs when 80% of it is encrypted wat not helping. Fixes #27550 Signed-off-by: David Goulet <dgoulet@torproject.org>
6 lines
301 B
Plaintext
6 lines
301 B
Plaintext
o Minor bugfixes (hidden service v3):
|
|
- Don't warn so loudly when tor is unable to decode a descriptor. This can
|
|
now happen as a normal use case if a client gets a descriptor with
|
|
client authorization but the client is not authorized. Fixes bug 27550;
|
|
bugfix on 0.3.5.1-alpha.
|