... | ... | @@ -8,4 +8,75 @@ |
|
|
|
|
|
### Nice to Have
|
|
|
- circuit dispay stuffs
|
|
|
- etc |
|
|
\ No newline at end of file |
|
|
- etc
|
|
|
|
|
|
### Used commands
|
|
|
|
|
|
- AUTHENTICATE
|
|
|
- SETEVENTS stream
|
|
|
- GETINFO (info.getInfo, getInfo)
|
|
|
- net/listeners/socks // torbutton_local_tor_check
|
|
|
- circuit-status // circuit display
|
|
|
- ip-to-country // circuit display
|
|
|
- status/bootstrap-phase // retrieve bootstrap status
|
|
|
- GETCONF
|
|
|
- bridge // circuit display
|
|
|
- ONION_CLIENT_AUTH_VIEW
|
|
|
- ONION_CLIENT_AUTH_ADD
|
|
|
- ONION_CLIENT_AUTH_REMOVE
|
|
|
- SIGNAL NEWNYM // for new identity
|
|
|
- SAVECONF // tor settings, enable/disable network
|
|
|
- SETCONF // tor settings, enable/disable network
|
|
|
- firewall, proxy, bridge settings
|
|
|
- bootstrapping
|
|
|
- SOCKS errors for onion errors (at the moment)
|
|
|
|
|
|
### Applications team TODO:
|
|
|
|
|
|
- Get requirements for accessing rdsys via meek/moat (Moat.jsm functionality)
|
|
|
- arti_client crate is for intended for actual use by external programs
|
|
|
|
|
|
- arti is the command line, but we shouldn't need it (unless we want to run the SOCKS proxy)
|
|
|
|
|
|
- everything else is not "safe" to use (it might change) and we should ask to rework the way it's exported
|
|
|
|
|
|
## Notes taken during the session
|
|
|
|
|
|
### Integration
|
|
|
|
|
|
We should start shipping Arti ASAP, just to start testing soon.
|
|
|
|
|
|
An idea is to build it together with Firefox.
|
|
|
It could also help saving a few MB in the installer.
|
|
|
|
|
|
Arti targets 1.56 at the moment, Firefox 102 targets 1.62.0 so it is okay.
|
|
|
|
|
|
We could add a preference or an environment variable to switch at runtime (rather than at build level).
|
|
|
|
|
|
We could add Arti to Firefox, but still use the SOCKS proxy (the API is not stable though).
|
|
|
We should aim at doing something better eventually.
|
|
|
Multiprocess could be a problem.
|
|
|
|
|
|
Events are implemented in async rust. We will need to think on how to unwrap that for FFI.
|
|
|
|
|
|
### Clients
|
|
|
|
|
|
Setconf:
|
|
|
|
|
|
1. you need a copy of your current build
|
|
|
2. use the set functions
|
|
|
3. create a new client?
|
|
|
|
|
|
You can use a new client for isolation, but there are (better?) alternatives, such as tokens, or the SOCKS usernames are still looked at.
|
|
|
|
|
|
Clients are very lightweight because they are handlers.
|
|
|
|
|
|
They share information about the directory authorities and other things.
|
|
|
|
|
|
Newnym: you drop the client and create a new one.
|
|
|
|
|
|
### Not working settings
|
|
|
|
|
|
Arti does not support outbound proxies at the moment.
|
|
|
|
|
|
It supports firewall, you can specify a list of reachable address and also ports if I understood correctly. |
|
|
\ No newline at end of file |