mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.0 2022-05-11T12:26:35Z 2022-05-11T12:26:35Z eta tor@eta.st 2022-05-11T12:26:35Z urn:sha1:864fd03917a0409c6a0380c258d96252359a559b - arti#445 highlighted the lack of good documentation around Arti's multiple runtime support, as well as it being difficult to determine what runtime was actually in use. - Improve the documentation to solve the first problem. - To solve the second problem, make Runtime require Debug (which is arguably a good idea anyway, since it makes them easier to embed in things), and print out the current runtime's Debug information when arti is invoked with `--version`. - (It also prints out other Cargo features, too!) fixes arti#445 2022-03-30T12:55:58Z Nick Mathewson nickm@torproject.org 2022-03-30T12:55:58Z urn:sha1:700e491813f84d76446193aef7121a329b774717 2022-03-30T12:44:25Z eta tor@eta.st 2022-03-30T12:44:25Z urn:sha1:fd081742fa13e8464ad46123d83617165587d4f4 Don't use SystemTime::now() Closes #306 See merge request tpo/core/arti!365 2022-03-14T19:59:33Z trinity-1686a trinity@deuxfleurs.fr 2022-03-05T18:49:38Z urn:sha1:4a44ef56c0743775d49eca138a253f11e93c7a35 2022-02-25T19:34:27Z trinity-1686a trinity@deuxfleurs.fr 2022-02-25T19:34:27Z urn:sha1:f9a4f23e8345f1f51e002433e83cda66129118cf 2022-01-26T19:06:58Z Nick Mathewson nickm@torproject.org 2022-01-26T18:59:37Z urn:sha1:bf8fa66d36298561cc868706f748049cec23f5eb This avoids a future confusion with the new `SpawnBlocking` trait in async_executors v0.5, and better describes what the trait provides. 2021-12-07T17:00:40Z eta tor@eta.st 2021-12-02T11:44:29Z urn:sha1:b14c5f370eef0a4fc1d2504ce54de1a921472567 `tor-rtcompat`'s `TlsConnector` trait previously included a method to create a TLS-over-TCP connection, which implied creating a TCP stream inside that method. This commit changes that, and makes the function wrap a TCP stream, as returned from the runtime's `TcpProvider` trait implementation, instead. This means you can actually override `TcpProvider` and have it apply to *all* connections Arti makes, which is useful for issues like arti#235 and other cases where you want to have a custom TCP stream implementation. This required updating the mock TCP/TLS types in `tor-rtmock` slightly; due to the change in API, we now store whether a `LocalStream` should actually be a TLS stream inside the stream itself, and check this property on reads/writes in order to detect misuse. The fake TLS wrapper checks this property and removes it in order to "wrap" the stream, making reads and writes work again. 2021-11-25T13:20:37Z Daniel Eades danieleades@hotmail.com 2021-11-25T13:14:05Z urn:sha1:db16d13df4779ac61005050dfe5ce05e3d5a1b5d 2021-11-04T15:04:59Z Nick Mathewson nickm@torproject.org 2021-11-04T15:04:59Z urn:sha1:83d9f2299ebfb4355ced1b3111b3e1f4bff62e43 2021-10-26T17:13:46Z Nick Mathewson nickm@torproject.org 2021-10-26T17:12:41Z urn:sha1:e64177d97e3623474f042df45efefa46d17a45a0 These are my fault; I merged the wrong version of !102. :p