The configuration API has been completely rewritten, to make it easier for applications to change Arti’s configuration as needed, and to reuse the user’s main Arti configuration file (if they want to). The Arti 0.0.2 release has a major refactor of the backend network code that implements circuits and channels, to better use the reactor architectural pattern and reduce the need for locks. ![]() Each release will break API compatibility until then, when we’ll start making an effort to keep the API a bit more stable. We’re planning to do releases every month or so until we put out an 0.1.0 release in March. We’re also trying to fill in small missing features and set the groundwork for future work on performance and reliability. With that in mind, we’re working on API completeness and ergonomics, and trying to get our breaking changes out of the way. With that done, our next major goal is our 0.1.0 milestone in March, where we’ll to have a (mostly) stable API that applications can rely on. It included a working SOCKS proxy client, a supported (but unstable) API for embedding, and all the basic features necessary for anonymous use of the Tor network. We put out our first official release of Arti last month. ![]() It’s nowhere near ready to replace the main Tor implementation in C, but we believe that it’s the future. Arti is our ongoing project to create a working embeddable Tor client in Rust.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |