aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Massive refactoring of the various handshake typesNick Mathewson2013-01-03
| | | | | The three handshake types are now accessed from a unified interface; their state is abstracted from the rest of the cpath state, and so on.
* Refactor the CREATE_FAST handshake code to match the others.Nick Mathewson2013-01-03
|
* Split onion.[ch] into onion{,_fast,_tap}.[ch]Nick Mathewson2013-01-02
| | | | | | | | | | I'm going to want a generic "onionskin" type and set of wrappers, and for that, it will be helpful to isolate the different circuit creation handshakes. Now the original handshake is in onion_tap.[ch], the CREATE_FAST handshake is in onion_fast.[ch], and onion.[ch] now handles the onion queue. This commit does nothing but move code and adjust header files.
* Wrangle curve25519 onion keys: generate, store, load, publish, republishNick Mathewson2013-01-02
| | | | | | | | Here we try to handle curve25519 onion keys from generating them, loading and storing them, publishing them in our descriptors, putting them in microdescriptors, and so on. This commit is untested and probably buggy like whoa
* Move curve25519 keypair type to src/common; give it functionsNick Mathewson2013-01-02
| | | | | | This patch moves curve25519_keypair_t from src/or/onion_ntor.h to src/common/crypto_curve25519.h, and adds new functions to generate, load, and store keypairs.
* Refactor strong os-RNG into its own functionNick Mathewson2013-01-02
| | | | | | | | | | | Previously, we only used the strong OS entropy source as part of seeding OpenSSL's RNG. But with curve25519, we'll have occasion to want to generate some keys using extremely-good entopy, as well as the means to do so. So let's! This patch refactors the OS-entropy wrapper into its own crypto_strongest_rand() function, and makes our new curve25519_secret_key_generate function try it as appropriate.
* curve25519-donna-c64: make endian-neutralness fns staticNick Mathewson2013-01-02
|
* Implementat the ntor handshakeNick Mathewson2013-01-02
| | | | | | The ntor handshake--described in proposal 216 and in a paper by Goldberg, Stebila, and Ustaoglu--gets us much better performance than our current approach.
* Add a wrapper around, and test and build support for, curve25519.Nick Mathewson2013-01-02
| | | | | | | | | | | | | | | | | | We want to use donna-c64 when we have a GCC with support for 64x64->uint128_t multiplying. If not, we want to use libnacl if we can, unless it's giving us the unsafe "ref" implementation. And if that isn't going to work, we'd like to use the portable-and-safe-but-slow 32-bit "donna" implementation. We might need more library searching for the correct libnacl, especially once the next libnacl release is out -- it's likely to have bunches of better curve25519 implementations. I also define a set of curve25519 wrapper functions, though it really shouldn't be necessary. We should eventually make the -donna*.c files get build with -fomit-frame-pointer, since that can make a difference.
* curve25519-donna-c64: work on bigendian and alignment-happy systemsNick Mathewson2013-01-02
| | | | | | | | There was one place in curve25519-donna-c64 that was relying on unaligned access and relying on little-endian values. This patch fixes that. I've sent Adam a pull request.
* Make curve25519-donna work with our compiler warnings.Nick Mathewson2013-01-02
|
* Add fallback implementations for curve25519: curve25519_donnaNick Mathewson2013-01-02
| | | | | This is copied from Adam Langley's curve25519-donna package, as of commit 09427c9cab32075c06c3487aa01628030e1c5ae7.
* Add a data-invariant linear-search map structureNick Mathewson2013-01-02
| | | | I'm going to use this for looking op keys server-side for ntor.
* Add a unit test for the old KDF while we're at itNick Mathewson2012-12-06
|
* Implement HKDF from RFC5869Nick Mathewson2012-12-06
| | | | | | | | | | | | | This is a customizable extract-and-expand HMAC-KDF for deriving keys. It derives from RFC5869, which derives its rationale from Krawczyk, H., "Cryptographic Extraction and Key Derivation: The HKDF Scheme", Proceedings of CRYPTO 2010, 2010, <http://eprint.iacr.org/2010/264>. I'm also renaming the existing KDF, now that Tor has two of them. This is the key derivation scheme specified in ntor. There are also unit tests.
* Add benchmark to test onionskin performance.Nick Mathewson2012-12-06
|
* Add a crypto_dh_dup, for benchmark supportNick Mathewson2012-12-06
|
* Merge remote-tracking branch 'asn/bug7592_take2'Nick Mathewson2012-12-04
|\
| * Return connection_exit_connect() if payload creation failed.George Kadianakis2012-12-05
| | | | | | | | | | | | Fixes bug #7592; bugfix on 882b389668067a29bb539d0f5bd5cb2f83b93012. The bug is not present in any released versions of Tor.
* | fix some typosRoger Dingledine2012-12-03
|/
* Merge branch 'bug7013_take2_squashed'Nick Mathewson2012-11-27
|\
| * Introduce tor_addr_port_parse() and use it to parse ServerTransportListenAddr.George Kadianakis2012-11-27
| |
| * Add a torrc option to specify the bind address of managed proxies.George Kadianakis2012-11-27
| |
* | Make sure that the error in ADDRMAP events is well-formedNick Mathewson2012-11-23
| | | | | | | | | | "error=Unable to launch resolve request" is not a nice thing to tell the controller. Bugfix on 0.2.0.19-alpha (c11c48fc).
* | Minor documentation fixNick Mathewson2012-11-23
| |
* | Note limitation of parse_rfc_1123_timeNick Mathewson2012-11-23
| | | | | | | | | | RFC1123 suggests that we should handle two-year times, and a full range of time zones, and other stuff too. We don't.
* | In comments and logs, say "UTC" not "GMT"Nick Mathewson2012-11-23
| | | | | | | | | | | | | | Fix for #6113. Note that the RFC1123 times we generate still all say 'GMT'. I'm going to suggest this is not worth changing.
* | Refer to RFC 4648 instead of the obsolete RFC 3548Nick Mathewson2012-11-23
| | | | | | | | Affects comments only. For ticket 6849.
* | forward-port the 0.2.3.25 changelog and release notesRoger Dingledine2012-11-20
| |
* | Merge branch 'bug7493_redux'Nick Mathewson2012-11-18
|\ \
| * | Initialize ipv{4,6}_traffic_ok in entry_connection_newNick Mathewson2012-11-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This one is necessary for sending BEGIN cells with sane flags when self-testing a directory port. All real entry connections were getting their ipv{4,6}_traffic_ok flags set from their listeners, and for begindir entry connections we didn't care, but for directory self-testing, we had a problem. Fixes at least one more case of 7493; if there are more lingering cases of 7493, this might fix them too. Bug not in any released version of Tor.
* | | when counting available descs, say whether we're counting exitsRoger Dingledine2012-11-16
|/ /
* | Give useful warning when both IPv4 and IPv6 are disabled on a socksportNick Mathewson2012-11-15
| |
* | Allow IPv4 traffic on default and old-style-config SocksPorts.Nick Mathewson2012-11-15
| | | | | | | | | | | | | | | | Looks like when i was writing the code to set the ipv4_traffic flag on port_cfg_t, I missed some cases, such as the one where the port was set from its default value. Fix for 7493. Bug not in any released Tor.
* | Merge branch 'ipv6_exits'Nick Mathewson2012-11-15
|\ \
| * | Set IPv4/IPv6 flags correctly when being a SOCKS clientNick Mathewson2012-11-15
| | |
| * | Remove some XXXX commens in dns.cNick Mathewson2012-11-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, I was freaking out about passing an unspec address to dns_found_answer() on an error, since I was using the address type to determine whether the error was an error on an ipv4 address lookup or on an ipv6 address lookup. But now dns_found_answer() has a separate orig_query_type argument to tell what kind of query it is, so there's no need to freak out.
| * | Fix up some comments in connection_edge.cNick Mathewson2012-11-15
| | |
| * | Add a changes file for IPv6 exitsNick Mathewson2012-11-14
| | |
| * | Add manual page entries for new IPv6-exits optionsNick Mathewson2012-11-14
| | |
| * | Add another missing function docNick Mathewson2012-11-14
| | |
| * | Initial support for AAAA requests on DNSPort.Nick Mathewson2012-11-14
| | | | | | | | | | | | | | | | | | This is imperfect, since it sends back whatever we would send to a socks RESOLVE request, when in reality we should send back whatever was asked for.
| * | Let tor-resolve generate PTR requests for IPv6 addressesNick Mathewson2012-11-14
| | |
| * | Accept reverse resolve requests for IPv6 addressesNick Mathewson2012-11-14
| | |
| * | Add IPv6 support to tor-resolve so it can hear about IPv6 answersNick Mathewson2012-11-14
| | |
| * | Make DNS resolve requests work for IPv6Nick Mathewson2012-11-14
| | | | | | | | | | | | | | | | | | | | | * If there's an IPv4 and an IPv6 address, return both in the resolved cell. * Treat all resolve requests as permitting IPv6, since by the spec they're allowed to, and by the code that won't break anything.
| * | Fix a bug in policy_is_reject_star() that was making IPv4 exits breakNick Mathewson2012-11-14
| | | | | | | | | | | | | | | | | | | | | | | | IPv4-only exits have an implicit "reject [::]/0", which was making policy_is_reject_star() return 1 for them, making us refuse to do hostname lookups. This fix chanes policy_is_reject_star() to ask about which family we meant.
| * | Add some missing doxygen for ipv6 exit codeNick Mathewson2012-11-14
| | |
| * | Actually send back correctly-formed IPv6 CONNECTED cellsNick Mathewson2012-11-14
| | | | | | | | | | | | | | | We had some old code to send back connected cells for IPv6 addresses, but it was wrong. Fortunately, it was also unreachable.
| * | Remove some unused defines in dns.cNick Mathewson2012-11-14
| | |
generated by cgit v1.2.3 (git 2.45.0) at 2024-11-23 07:33:44 +0000