summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * Remove no-longer-needed tokio runtime helper macroNick Mathewson2022-01-261-27/+18
| |
| * Unify TokioRuntime and TokioRuntimeHandleNick Mathewson2022-01-264-66/+54
| | | | | | | | | | | | | | | | | | Having separate types here doesn't justify the (very limited) benefit of distinguishing between the case where we have created an executor that we own and the case where we have a handle to an already-running tokio executor. Part of #301.
| * Remove a now-incorrect comment in tor-proto.Nick Mathewson2022-01-261-3/+0
| |
| * Remove misspellings of "rusttls".Nick Mathewson2022-01-261-2/+2
| |
* | Merge branch 'coverage-tracking' into 'main'eta2022-01-273-10/+49
|\ \ | | | | | | | | | | | | | | | | | | Add test coverage tracking with CI/CD Closes #250 See merge request tpo/core/arti!221
| * | Install bs4 in coverage jobArturo Marquez2022-01-261-0/+2
| | |
| * | Use `maint/with_coverage.sh` in coverage jobArturo Marquez2022-01-261-5/+6
| | |
| * | Add changes in `maint`Arturo Marquez2022-01-262-10/+24
| | | | | | | | | | | | Follows up on changes from https://gitlab.torproject.org/trinity-1686a/arti/-/merge_requests/2/diffs#bc2cc73a8917fa6fed183148df69119665eb4e55
| * | Remove lcov from coverage jobArturo Marquez2022-01-071-3/+0
| | |
| * | Change output type to `cobertura`Arturo Marquez2022-01-071-8/+4
| | |
| * | Use python3.9 in coverage jobArturo Marquez2022-01-061-1/+1
| | |
| * | Add pip3 show to coverage jobArturo Marquez2022-01-061-0/+1
| | |
| * | Add pip3 to coverage jobArturo Marquez2022-01-061-1/+2
| | |
| * | Remove build in coverage jobArturo Marquez2022-01-061-1/+0
| | |
| * | Use stable image and download nightly in coverageArturo Marquez2022-01-061-1/+3
| | | | | | | | | | | | | | | Following suggestion here: `https://gitlab.torproject.org/tpo/core/arti/-/issues/250#note_2764010`
| * | Add cargo build to coverage jobArturo Marquez2022-01-061-0/+1
| | |
| * | Change targetArturo Marquez2022-01-061-3/+3
| | |
| * | Add `coverage` jobArturo Marquez2022-01-061-0/+25
| | | | | | | | | | | | | | | | | | Following instructions at: `https://www.collabora.com/news-and-blog/blog/2021/03/24/rust-integrating-llvm-source-base-code-coverage-with-gitlab/`
* | | Merge branch 'config' into 'main'eta2022-01-261-0/+122
|\ \ \ | |_|/ |/| | | | | | | | doc/CONFIG-NOTES.md: config proposal See merge request tpo/core/arti!248
| * | CONFIG-NOTES: finish a sentenceIan Jackson2022-01-201-1/+1
| | |
| * | CONFIG-NOTES: Suggestions from MR revieweta2022-01-201-2/+2
| | |
| * | doc/CONFIG-NOTES.md: config proposalIan Jackson2022-01-191-0/+122
| | |
* | | Merge branch 'rustls_v2' into 'main'Nick Mathewson2022-01-2513-253/+859
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | tor-rtcompat: Add support for a rustls backend Closes #86 See merge request tpo/core/arti!260
| * | | More comments on the limitations of tor-rtcompat's TLS APINick Mathewson2022-01-252-3/+29
| | | | | | | | | | | | | | | | | | | | Also, more comments on why these limitations are safe within the context of Tor, but you wouldn't want to use them elsewhere.
| * | | Comment-only: document sni_hostname more.Nick Mathewson2022-01-251-3/+5
| | | | | | | | | | | | | | | | | | | | Previously we expected the reader to automatically know why it was called "SNI", which really isn't fair.
| * | | Refactor native_tls usage into its own moduleNick Mathewson2022-01-258-241/+130
| | | | | | | | | | | | | | | | | | | | This change uses the async-native-tls crate for everything, and deletes some duplicated code.
| * | | tor-rtcompat: Add support for rustls.Nick Mathewson2022-01-259-9/+539
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is based on @janimo's approach in !74, but diverges in a few important ways. 1. It assumes that something like !251 will merge, so that we can have separate implementations for native_tls and rustls compiled at the same time. 2. It assumes that we can implement this for the futures::io traits only with no real penalty. 3. It uses the `x509-signature` crate to work around the pickiness of the `webpki` crate. If webpki eventually solves their [bug 219](https://github.com/briansmith/webpki/issues/219), we can remove a lot of that workaround. Closes #86.
| * | | Add a C program to make Tor-style X509 link certificatesNick Mathewson2022-01-241-0/+159
|/ / / | | | | | | | | | | | | We should never use this for anything but making the testing certificates we use for making sure our TLS implementation works.
* | | Merge branch 'ticket_277' into 'main'eta2022-01-243-4/+47
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | More documentation about refining build process and getting help Closes #277 See merge request tpo/core/arti!259
| * | | README,CONTRIBUTING: More links.Nick Mathewson2022-01-212-3/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Explain how to report bugs and how get accounts on the bugtracker; add link to the troubleshooting document. Part of #277
| * | | TROUBLESHOOTING.md: More information+links about build process.Nick Mathewson2022-01-211-1/+28
| | | | | | | | | | | | | | | | Part of #277
* | | | Merge branch 'error-plan' into 'main'eta2022-01-241-0/+230
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Error plan See merge request tpo/core/arti!257
| * | | | Error plan: typos/fixeseta2022-01-211-3/+3
| | | | |
| * | | | Errors: fold in people's views so is mostly unattributed nowIan Jackson2022-01-201-15/+28
| | | | |
| * | | | Errors: sort out markdown formattingIan Jackson2022-01-201-16/+30
| | | | |
| * | | | Errors: c&p raw text of consensus conclusions from pad to gitIan Jackson2022-01-201-0/+203
| | | | |
* | | | | Merge branch 'ticket255' into 'main'eta2022-01-2410-46/+339
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Refactor our Runtime implementations to allow replacement parts Closes #255 See merge request tpo/core/arti!251
| * | | | | Refactor Runtimes to use separate TLS implementations internally.Nick Mathewson2022-01-199-46/+135
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will make it easier to implement them using some other TLS provider as well, without having to duplicate all of our code.
| * | | | | Add a macro to help with opaque Runtime wrappers.Nick Mathewson2022-01-192-0/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We're soon going to have our different Runtime types be built as CompoundRuntime instances. We don't want to expose that detail, though, so we'll use this macro to make them implement the right traits.
| * | | | | Add a CompoundRuntime type for runtime construction.Nick Mathewson2022-01-192-0/+134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This type can solve two problems at once. First, it lets users replace parts of an existing runtime implementation without replacing the whole thing. For example, you can use it to override your TcpProvider implementation to solve problems like #235. Second, we can use it internally to tor-rtcompat to define Runtimes piece-by-piece. Mostly we'll use this to separate our Tls implementations from our implementations of the rest of the Runtime.
* | | | | | Merge branch 'conn-prefs-rename' into 'main'Ian Jackson2022-01-215-21/+21
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | | | | | | | | | | | | | StreamPrefs: rename from ConnectPrefs See merge request tpo/core/arti!256
| * | | | | Rename TorClient::set_stream_prefsIan Jackson2022-01-211-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In line with the rest of the renaming. As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/256#note_2771617
| * | | | | StreamPrefs: Re-alphabetise imports following renameIan Jackson2022-01-211-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Placates rustfmt
| * | | | | StreamPrefs: rename from ConnectPrefsIan Jackson2022-01-215-20/+20
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The docs even say this is about stream. As @nickm writes in https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/252#note_2771289 we generally call end-to-end connections that are tunneled over Tor "Streams" to distinguish them from everything else in the Tor protocols that could possibly be called a "Connection". That seems to apply here too.
* | | | | Merge branch 'always-isolate' into 'main'Ian Jackson2022-01-201-4/+58
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | Provide isolate-all-streams function Closes #279 See merge request tpo/core/arti!252
| * | | | isolation: Rename isolate_every_stream from ..._connectionIan Jackson2022-01-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/252#note_2771291
| * | | | isolation: Rename (internal) EveryStream enum variantIan Jackson2022-01-201-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/252#note_2771289
| * | | | isolation: Much better wording for always isolate settingNick Mathewson2022-01-201-1/+6
| | | | |
| * | | | isolation: Provide isolate-every-connection optionIan Jackson2022-01-201-0/+16
| | | | |
| * | | | isolation: Provide new_isolation_group methodIan Jackson2022-01-201-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the usual case, set_isolation_group is awkward. This is perhaps slightly duplicative with TorClient::isolated_client(). If so then perhaps the *latter* should be abolished.