Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:27:09Zhttps://gitlab.torproject.org/legacy/trac/-/issues/26494Resolve containers<->logs circular dependency2020-06-13T15:27:09ZNick MathewsonResolve containers<->logs circular dependencyRight now, libtor-logs and libtor-containers each use functions from one another. That should not stand. My preferred solution is to divide a smartlist-core from the rest of containers.Right now, libtor-logs and libtor-containers each use functions from one another. That should not stand. My preferred solution is to divide a smartlist-core from the rest of containers.Tor: 0.3.5.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/25714switch Travis to using Rust stable2020-06-13T15:24:09ZTaylor Yuswitch Travis to using Rust stableRight now our Travis use Rust nightly instead of stable. Now that we are standardizing on a stable Rust (see #24765), we should have Travis use stable so we catch accidental uses of nightly features.Right now our Travis use Rust nightly instead of stable. Now that we are standardizing on a stable Rust (see #24765), we should have Travis use stable so we catch accidental uses of nightly features.Tor: 0.3.4.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/legacy/trac/-/issues/25675fix CID 14336432020-06-13T15:23:56ZTaylor Yufix CID 1433643Coverity found `control_free_all()` was accessing `flush_queued_event_pending` without locking. This was actually an old latent bug dating back to when we added multithreading to this queue, but Coverity somehow didn't notice the other ...Coverity found `control_free_all()` was accessing `flush_queued_event_pending` without locking. This was actually an old latent bug dating back to when we added multithreading to this queue, but Coverity somehow didn't notice the other unlocked accesses.Tor: 0.3.4.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/legacy/trac/-/issues/25550improve continuous integration support2020-06-13T15:23:20ZTaylor Yuimprove continuous integration supportTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/25549Add tor CI config for AppVeyor2020-06-13T15:24:58ZIsis LovecruftAdd tor CI config for AppVeyorAt the Rome meeting, it was discussed (apparently, I wasn't there that time) to have an AppVeyor config for tor. As I understand it (and please feel free to correct this ticket!), the idea is to have multiple CI systems running (which i...At the Rome meeting, it was discussed (apparently, I wasn't there that time) to have an AppVeyor config for tor. As I understand it (and please feel free to correct this ticket!), the idea is to have multiple CI systems running (which is a thing we already do!). For example, currently, we have [Jenkins](https://jenkins.torproject.org) and we also have TravisCI for personal (Github-based) forks (as per #22636): Jenkins tests (essentially) (Debian package-based) builds on `master` and known (supported) tor versions, while Travis tests _anything any developer pushes_ (albeit only for GCC/Clang on Linux, because everything else is unsupported/slow).
We should setup an AppVeyor config for testing tor on Windows. Ideally, it should match the testing behaviour of our Jenkins/Travis builds, so that we don't get spurious errors on one system or another.Tor: 0.3.4.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/25507Write a guide for groups planning to submit big patches to Tor.2020-06-13T15:23:05ZNick MathewsonWrite a guide for groups planning to submit big patches to Tor.This is a master ticket for a document to explain to people or groups who are thinking of landing large branches in the Tor source. It should explain how to do this in an effective and smooth way, go over our practices, and try to preven...This is a master ticket for a document to explain to people or groups who are thinking of landing large branches in the Tor source. It should explain how to do this in an effective and smooth way, go over our practices, and try to prevent as much frustration as possible.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/25498module: Basic modularization preparation2020-06-13T15:23:00ZDavid Gouletdgoulet@torproject.orgmodule: Basic modularization preparationTicket #25494 was created to do some initial work in modularization in tor that is the code part. Then #25495 is about identifying the list of modules in a structured list which from there we'll open tickets to do the work to extract dif...Ticket #25494 was created to do some initial work in modularization in tor that is the code part. Then #25495 is about identifying the list of modules in a structured list which from there we'll open tickets to do the work to extract different modules.
This ticket is a sponsor task and should be about what else we need then the list of modules before we start extracting modules.Tor: 0.3.4.x-finalDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/25257Orbot relay problem.2018-02-28T20:58:42ZTracOrbot relay problem.good afternoon
There is problem on newest version of orbot app. At the settings, relay port, i wrote 443 port. After I do it, The tor relay isn't start. I returnet previous port, and it goes normally. Please, solve this issue, because i ...good afternoon
There is problem on newest version of orbot app. At the settings, relay port, i wrote 443 port. After I do it, The tor relay isn't start. I returnet previous port, and it goes normally. Please, solve this issue, because i haven't opened port 9001 on my mobile data. I have opened port 443.
Thanks.
Translate on Polish.
Dzień dobry.
Mam problem z przekaźnikiem tora na telefonie z androidem w aplikacji orbot. Po zmianie portu w ustawieniach na 443 tor w ogóle się nie uruchamia. Cały czas widnieje napis: "Orbot is starting". Po przywróceniu domyślnego portu wszystko działa poprawnie. Proszę o rozwiązanie problemu, ponieważ na mobilnej sieci mam otwarty port 443 a częściej korzystam z mobilnego pakietu.
Dziękuję.
**Trac**:
**Username**: bogusNathan FreitasNathan Freitashttps://gitlab.torproject.org/legacy/trac/-/issues/24990Write a proposal for a post-quantum lattice KEX2020-06-13T15:21:07ZIsis LovecruftWrite a proposal for a post-quantum lattice KEXAs part of #24985, we'll need a solid, reviewed proposal for which post-quantum key exchange we intend concretely to use.
My current idea for the key exchange is to use q=12289 and n=1024 (the lattice parameters from [NewHope](https://e...As part of #24985, we'll need a solid, reviewed proposal for which post-quantum key exchange we intend concretely to use.
My current idea for the key exchange is to use q=12289 and n=1024 (the lattice parameters from [NewHope](https://eprint.iacr.org/2015/1092) and other designs), along with the constant-time sampling protections I devised while working on [prop#270](https://gitweb.torproject.org/torspec.git/tree/proposals/270-newhope-hybrid-handshake.txt), ripping out the Voronoi-cell based reconciliation mechanism and instead using a variant of the XE5 reconciliation from the NIST [HILA5](https://mjos.fi/hila5/) submission (possibly tuning down the failure probability by increasing the noise, which raises the security level, since our key exchange is interactive and thus we don't care about having the 2^-128^ failure probability which allows HILA5 to be used for public key encryption schemes).Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24988Implement prop#269 "Hybrid Handshakes" (ntor2 module)2020-06-13T15:23:28ZIsis LovecruftImplement prop#269 "Hybrid Handshakes" (ntor2 module) As part of #24985, we'll need to implement prop#269. This should probably be in two parts:
1) Implement a new module which, given function pointers to two handshakes (one classic and the other post-quantum secure) which follow som... As part of #24985, we'll need to implement prop#269. This should probably be in two parts:
1) Implement a new module which, given function pointers to two handshakes (one classic and the other post-quantum secure) which follow some prescribed API, compose the handshakes together to produce a final shared secret
2) Implement "hybrid null" (as it's called in the proposal), which here I'm calling "ntor2"
This ticket is about part 2. It ultimately depends upon #24986 and #24987 as well, although it can be done (and even rolled out into production, if we chose to do so) before either are finished.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24987Implement prop#269 "Hybrid Handshakes" (composition module)2020-06-13T15:21:06ZIsis LovecruftImplement prop#269 "Hybrid Handshakes" (composition module)As part of #24985, we'll need to implement [prop#269](https://gitweb.torproject.org/torspec.git/tree/proposals/269-hybrid-handshake.txt). This should probably be in two parts:
1) Implement a new module which, given function pointers to...As part of #24985, we'll need to implement [prop#269](https://gitweb.torproject.org/torspec.git/tree/proposals/269-hybrid-handshake.txt). This should probably be in two parts:
1) Implement a new module which, given function pointers to two handshakes (one classic and the other post-quantum secure) which follow some prescribed API, compose the handshakes together to produce a final shared secret
2) Implement "hybrid null" (as it's called in the proposal), which here I'm calling "ntor2"
This ticket is about part 1. It depends upon #24986 as well.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24986Implement prop#249 "Large Create Cells"2020-06-13T15:21:05ZIsis LovecruftImplement prop#249 "Large Create Cells"As part of #24985, we'll need to implement [prop#249](https://gitweb.torproject.org/torspec.git/tree/proposals/249-large-create-cells.txt)'s design for large create cells.As part of #24985, we'll need to implement [prop#249](https://gitweb.torproject.org/torspec.git/tree/proposals/249-large-create-cells.txt)'s design for large create cells.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24985Preserve circuit-layer confidentiality against a quantum-capable adversary2020-06-13T15:21:04ZIsis LovecruftPreserve circuit-layer confidentiality against a quantum-capable adversary[Many](https://eprint.iacr.org/2015/008) [researchers](https://eprint.iacr.org/2015/287), ourselves included, have been aiming [for](https://gitweb.torproject.org/torspec.git/tree/proposals/249-large-create-cells.txt) [quite](https://git...[Many](https://eprint.iacr.org/2015/008) [researchers](https://eprint.iacr.org/2015/287), ourselves included, have been aiming [for](https://gitweb.torproject.org/torspec.git/tree/proposals/249-large-create-cells.txt) [quite](https://gitweb.torproject.org/torspec.git/tree/proposals/263-ntru-for-pq-handshake.txt) [some](https://gitweb.torproject.org/torspec.git/tree/proposals/269-hybrid-handshake.txt) [time](https://gitweb.torproject.org/torspec.git/tree/proposals/270-newhope-hybrid-handshake.txt) to protect Tor traffic against a hypothetical future adversary who has access to a quantum computer capable of breaking ECDH key exchanges which have occurred in the past and been recorded.
This is the parent ticket for organising the work into smaller, byte-sized chunks and tracking overall progress.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/24863Travis CI environment change breaks clang builds2020-06-13T15:20:20ZTaylor YuTravis CI environment change breaks clang buildsIt looks like an unannounced environment change in Travis CI's workers prevents LeakSanitizer from working correctly, breaking our Travis builds on clang. This seems to disable ptrace capabilities, which for some reason LeakSanitizer ne...It looks like an unannounced environment change in Travis CI's workers prevents LeakSanitizer from working correctly, breaking our Travis builds on clang. This seems to disable ptrace capabilities, which for some reason LeakSanitizer needs to run properly on our forking tests. (See https://github.com/travis-ci/travis-ci/issues/9033).
We can hope they fix this soon, or we can try to work around it by changing our `.travis.yml` to use a sudo-enabled build environment. (This has the drawback that some of our tests depend on running as non-root, but I think they all get skipped if running as root.)Tor: 0.3.2.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/23883document how to get Travis CI running on your fork of tor2020-06-13T15:16:00ZTaylor Yudocument how to get Travis CI running on your fork of torTor: 0.3.4.x-finalAlex XuAlex Xu