| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2017-07-28 | Fix a small memory leak when parsing unix: ports twice | Nick Mathewson | |
| Fixes bug 23053; CID 1415725. | |||
| 2017-07-27 | Merge remote-tracking branch 'public/bug20247_029' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-26 | Merge branch 'maint-0.2.8' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-26 | Merge branch 'maint-0.2.7-redux' into maint-0.2.8 | Nick Mathewson | |
| 2017-07-26 | Merge branch 'maint-0.2.6' into maint-0.2.7-redux | Nick Mathewson | |
| 2017-07-26 | Merge branch 'maint-0.2.5' into maint-0.2.6 | Nick Mathewson | |
| 2017-07-26 | Merge branch 'maint-0.2.4' into maint-0.2.5 | Nick Mathewson | |
| 2017-07-26 | Fix build warnings from Coverity related to our BUG macro | Nick Mathewson | |
| In the Linux kernel, the BUG() macro causes an instant panic. Our BUG() macro is different, however: it generates a nonfatal assertion failure, and is usable as an expression. Additionally, this patch tells util_bug.h to make all assertion failures into fatal conditions when we're building with a static analysis tool, so that the analysis tool can look for instances where they're reachable. Fixes bug 23030. | |||
| 2017-07-26 | Merge branch 'bug22915_029_2' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-26 | Suppress clang4-specific -Wdouble-promotion warnings | Nick Mathewson | |
| Wow, it sure seems like some compilers can't implement isnan() and friends in a way that pleases themselves! Fixes bug 22915. Bug trigged by 0.2.8.1-alpha and later; caused by clang 4. | |||
| 2017-07-17 | Add a changes file for bug22636. | Isis Lovecruft | |
| 2017-07-14 | Merge branch 'bug22916_027' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-13 | Fix compiler warnings with openssl-scrypt/libscrypt test on clang | Nick Mathewson | |
| Clang didn't like that we were passing uint64_t values to an API that wanted uint32_t. GCC has either not cared, or has figured out that the values in question were safe to cast to uint32_t. Fixes bug22916; bugfix on 0.2.7.2-alpha. | |||
| 2017-07-07 | Merge branch 'maint-0.2.8' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-07 | Merge branch 'bug22838_028' into maint-0.2.8 | Nick Mathewson | |
| 2017-07-07 | mingw fix: avoid "unused var" warning. | Nick Mathewson | |
| This is a backport of 19615bce64cd381a925bc3910120ac39ca918e7c to fix bug 22838. | |||
| 2017-07-07 | Merge branch 'maint-0.2.6' into maint-0.2.7-redux | Nick Mathewson | |
| 2017-07-07 | Merge branch 'maint-0.2.5' into maint-0.2.6 | Nick Mathewson | |
| 2017-07-07 | Merge branch 'maint-0.2.4' into maint-0.2.5 | Nick Mathewson | |
| 2017-07-07 | Merge branch 'maint-0.2.8' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-07 | Merge branch 'maint-0.2.7-redux' into maint-0.2.8 | Nick Mathewson | |
| 2017-07-07 | Mention TROVE-2017-007 in changes file for 22789 | Nick Mathewson | |
| 2017-07-05 | Merge branch 'maint-0.2.8' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-05 | Merge branch 'maint-0.2.7-redux' into maint-0.2.8 | Nick Mathewson | |
| 2017-07-05 | Merge branch 'maint-0.2.6' into maint-0.2.7-redux | Nick Mathewson | |
| 2017-07-05 | Merge branch 'maint-0.2.5' into maint-0.2.6 | Nick Mathewson | |
| 2017-07-05 | Merge branch 'maint-0.2.4' into maint-0.2.5 | Nick Mathewson | |
| 2017-07-05 | Allow setsockopt(IPV6_V6ONLY) in sandbox. | Nick Mathewson | |
| Fixes bug 20247. We started setting V6ONLY in 0.2.3.13-alpha and added the sandbox on 0.2.5.1-alpha. | |||
| 2017-07-05 | Merge branch 'bug22801_028' into maint-0.2.9 | Nick Mathewson | |
| 2017-07-03 | Fix assertion failure related to openbsd strtol(). | Nick Mathewson | |
| Fixes bug 22789; bugfix on 0.2.3.8-alpha. | |||
| 2017-07-03 | Fix -Wfloat-conversion C warnings on mingw in clamp_double_to_int64. | Nick Mathewson | |
| We just have to suppress these warnings: Mingw's math.h uses gcc's __builtin_choose_expr() facility to declare isnan, isfinite, and signbit. But as implemented in at least some versions of gcc, __builtin_choose_expr() can generate type warnings even from branches that are not taken. Fixes bug 22801; bugfix on 0.2.8.1-alpha. | |||
| 2017-06-28 | Merge remote-tracking branch 'teor/bug21507-029' into maint-0.2.9 | Nick Mathewson | |
| 2017-06-28 | Merge remote-tracking branch 'teor/bug21576_029_v2' into maint-0.2.9 | Nick Mathewson | |
| 2017-06-27 | Merge branch 'maint-0.2.7-redux' into maint-0.2.8 | Nick Mathewson | |
| 2017-06-27 | Merge branch 'maint-0.2.6' into maint-0.2.7-redux | Nick Mathewson | |
| 2017-06-27 | Merge branch 'maint-0.2.5' into maint-0.2.6 | Nick Mathewson | |
| 2017-06-27 | Merge branch 'maint-0.2.4' into maint-0.2.5 | Nick Mathewson | |
| 2017-06-27 | Merge branch 'maint-0.2.8' into maint-0.2.9 | Nick Mathewson | |
| 2017-06-27 | Fix an errant memset() into the middle of a struct in cell_pack(). | Nick Mathewson | |
| This mistake causes two possible bugs. I believe they are both harmless IRL. BUG 1: memory stomping When we call the memset, we are overwriting two 0 bytes past the end of packed_cell_t.body. But I think that's harmless in practice, because the definition of packed_cell_t is: // ... typedef struct packed_cell_t { TOR_SIMPLEQ_ENTRY(packed_cell_t) next; char body[CELL_MAX_NETWORK_SIZE]; uint32_t inserted_time; } packed_cell_t; So we will overwrite either two bytes of inserted_time, or two bytes of padding, depending on how the platform handles alignment. If we're overwriting padding, that's safe. If we are overwriting the inserted_time field, that's also safe: In every case where we call cell_pack() from connection_or.c, we ignore the inserted_time field. When we call cell_pack() from relay.c, we don't set or use inserted_time until right after we have called cell_pack(). SO I believe we're safe in that case too. BUG 2: memory exposure The original reason for this memset was to avoid the possibility of accidentally leaking uninitialized ram to the network. Now remember, if wide_circ_ids is false on a connection, we shouldn't actually be sending more than 512 bytes of packed_cell_t.body, so these two bytes can only leak to the network if there is another bug somewhere else in the code that sends more data than is correct. Fortunately, in relay.c, where we allocate packed_cell_t in packed_cell_new() , we allocate it with tor_malloc_zero(), which clears the RAM, right before we call cell_pack. So those packed_cell_t.body bytes can't leak any information. That leaves the two calls to cell_pack() in connection_or.c, which use stack-alocated packed_cell_t instances. In or_handshake_state_record_cell(), we pass the cell's contents to crypto_digest_add_bytes(). When we do so, we get the number of bytes to pass using the same setting of wide_circ_ids as we passed to cell_pack(). So I believe that's safe. In connection_or_write_cell_to_buf(), we also use the same setting of wide_circ_ids in both calls. So I believe that's safe too. I introduced this bug with 1c0e87f6d8c7a0abdadf1b5cd9082c10abc7f4e2 back in 0.2.4.11-alpha; it is bug 22737 and CID 1401591 | |||
| 2017-06-16 | Permit the fchmod system call. | Nick Mathewson | |
| Fixes bug 22516; bugfix on 0.2.5.4-alpha. | |||
| 2017-06-09 | Merge branch 'maint-0.2.8' into maint-0.2.9 | Nick Mathewson | |
| 2017-06-09 | Merge branch 'maint-0.2.7-redux' into maint-0.2.8 | Nick Mathewson | |
| 2017-06-09 | Merge branch 'maint-0.2.6' into maint-0.2.7-redux | Nick Mathewson | |
| 2017-06-09 | Merge branch 'maint-0.2.5' into maint-0.2.6 | Nick Mathewson | |
| 2017-06-09 | Merge branch 'maint-0.2.4' into maint-0.2.5 | Nick Mathewson | |
| 2017-06-09 | Update geoip and geoip6 to the June 8 2017 database. | Karsten Loesing | |
| 2017-06-08 | Merge branch 'maint-0.2.7-redux' into maint-0.2.8 | Nick Mathewson | |
| 2017-06-08 | Merge branch 'maint-0.2.6' into maint-0.2.7-redux | Nick Mathewson | |
| 2017-06-08 | Merge branch 'maint-0.2.5' into maint-0.2.6 | Nick Mathewson | |
| 2017-06-08 | Merge branch 'maint-0.2.4' into maint-0.2.5 | Nick Mathewson | |
 |
index : tor | |
| Transit encryption and privacy out of the box | The Tor Project |
| summaryrefslogtreecommitdiff |