I'm here to request a Tor Browser for Debian to get compiled for ppc64le architecture.
Power architecture is the only open hardware, so i think it's important for a project like Tor to support this architecture, avoiding potential backdoor on closed system.
If you need a ppc64le machine it will provided a cloud access for free, ask to https://twitter.com/RaptorCompSys for building and testing Tor Browser
No secure comunications is really secure on closed system, so to support an open architecture should be a priority for a project who looking for a digital freedom
Trac: Username: power9
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Trac: Priority: Very High to Medium Owner: N/Ato tbb-team Keywords: N/Adeleted, tbb-rbm added Component: - Select a component to Applications/Tor Browser
Good to know. FWIW: there are Debian packages for that platform, though.
That's fine: Tor is open-source, so Debian can maintain a PPC build of Tor if they want.
We just won't put any effort into Tor on PPC, because:
If (nearly?) all users on a platform are insecure, it's also good candidate for Rejected.
PPC (The MUL instruction isn't constant-time, thus many common cryptographic operations on these systems are subject to even the most trivial side-channel attacks.)
The Tor Browser team can maintain a PPC build of Tor if they want. But PPC has trivial cryptographic side-channel attacks. So a PPC Tor Browser might not meet Tor Browser's security standards.
The listed CPUs are very old. POWER9 has constant time multiplication via the mulhd/mulhdu and mulld instructions (min latency 5, max latency 5); POWER8 has constant time multiplication via the vmul instructions (latency 7, no variance).
See the POWER8 processor user guide [1], Performance Profile section and the POWER9 processor user guide [2], Appendix A for details.
Good to know. FWIW: there are Debian packages for that platform, though.
Debian 9 regrettably removes support for the following architecture: PowerPC (powerpc) The following are the officially supported architectures for Debian 9: 64-bit little-endian PowerPC (ppc64el)
As I mentioned above, we do have constant time multiplication on ppc64le, plus ppc64le is a Debian supported architecture. Can we get Tor for ppc64le even if old 32-bit ppc is not supported?
...
The following are the officially supported architectures for Debian 9:
64-bit little-endian PowerPC (ppc64el)
...
As I mentioned above, we do have constant time multiplication on ppc64le, plus ppc64le is a Debian supported architecture. Can we get Tor for ppc64le even if old 32-bit ppc is not supported?
I think you might be asking about Tor Browser (the application).
Tor Browser depends on both tor (the network daemon) and firefox:
So firefox esr is on ppc64le debian, tor too, the mul is correctly supported on current power. So for the technical point of view is ok.
You wrote some post ago tor project can mantain a ppc64le build, now it seems is just depend on tor project will
Well, this is no trivial task (as you will see once starting to work on it). In fact, there are wishes for other platforms/architectures having a Tor Browser as well (see: #12631 (moved) for ARM devices). We don't have the resources right now to work those, though, on our own. However, as you see in #12631 (moved) there are folks that pick this up from time to time and we are amenable including it in our official build infrastructure once patches are ready. So, please step up and help us here.
If i had resources and knowledge my first post request was about looking for other people not a brand new request.
Someone of you wrote some post before "The Tor Browser team can maintain a PPC build of Tor if they want" now you wrote the opposite, i'm confuse, i still do not understand if you really can't support it or if you don't want to
Someone of you wrote some post before "The Tor Browser team can maintain a PPC build of Tor if they want" now you wrote the opposite, i'm confuse, i still do not understand if you really can't support it or if you don't want to
If someone else writes patches, and those patches are good, we will merge the patches, and Tor Browser will be built for PPC.
Here are the details:
You might be confused because Tor Browser and Tor are different things. They are maintained by different teams, and they have different support policies.
To answer your question, different people needed to talk about supporting both Tor and Tor Browser on PPC. That's why you can see different people talking about different options on this ticket.
We don't have the people we need to support PPC:
The Tor Browser team does not have time to make patches for PPC Tor Browser. But they will build PPC Tor Browser if someone else writes patches.
The Tor team does not have any time to make patches for PPC Tor, or any way to test those patches. But if someone writes a patch that is obviously correct, we will merge it.
If both these things happen, then the Tor Browser team can build a PPC Tor Browser.
Very very early branch at https://notabug.org/JeremyRand/tor-browser-build/commits/ppc64le-esr68 . Not yet at a point where I'd recommend trying to review it (e.g. it does not build yet), but posting this for transparency and to let interested people know that it's being worked on.