- Jun 08, 2021
-
-
zzz authored
- Generate and parse short record format - Encrypt and decrypt short records - Register handlers for 3 new messages ITBM/STBM/OTBRM - Send ITBM/STBM if all hops support it (disabled) - Reply with OTBRM at OBEP if STBM received (disabled) - Send STBM at IBGW if ITBM received (disabled) - Add logic for when to send new messages - ChaCha encryption of other short records - Fix compare logic in ITBM parser (ticket #2814) All is still preliminary, disabled, untested; proposal is still incomplete Still todo: - Fill in plaintext record for ITBM/OTBRM - OTBRM key/tag
-
- Jun 01, 2021
- May 23, 2021
-
-
zzz authored
-
- May 21, 2021
-
-
zzz authored
-
- May 20, 2021
-
- May 18, 2021
-
- May 15, 2021
-
- May 10, 2021
-
- May 05, 2021
-
- Apr 27, 2021
-
- Apr 25, 2021
-
- Apr 24, 2021
-
-
zzz authored
Jetty server high CPU when client send data length > 17408 This affects SSL connections only, which is not part of our default setup. Adapted from workaround at: https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w Put the new checks directly in the unwrap() method, rather than subclassing SslConnection, as that would require config file changes.
- Apr 23, 2021
-
-
idk authored
When checking whether to use Roaming appdata(like on older installs or on installs where people deliberately use Roaming appdata) also check whether clients.config exists and if it does, set home to Roaming appdata since people may be updating from routers before the migration to clients.config.d directories. This should fix #16
-
- Apr 20, 2021
-
- Apr 17, 2021
-
- Apr 12, 2021
-
- Apr 11, 2021
-
- Apr 09, 2021
-
- Apr 08, 2021
-
- Apr 06, 2021
-
- Apr 05, 2021
-
- Apr 04, 2021
-
- Apr 03, 2021
-
- Apr 02, 2021
-
- Apr 01, 2021
-