Re: [tor-talk] Firefox OS - B2G support ?
Yeah, exact Mozilla is not working more on FFOS, but "the community" has now the project (smartphone part) in their hands ;) Now it's Boot2Gecko (1st name of the project...) and people is working on this OS everyday, so it will continue to live... https://developer.mozilla.org/en-US/docs/Mozilla/B2G_OS So it can be interesting to have another browser like Tor Browser available for this smartphone OS ;) > Mozilla has quietly killed the smartphone part of that project. > > They are still trying to use FfOS for IoT use cases, but the phone > project is no more. -- Petrusko PubKey EBE23AE5 C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5 signature.asc Description: OpenPGP digital signature -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
Re: [tor-talk] Tor-friendly email provider
On 9/22/2016 1:00 PM, Oskar Wendel wrote: gmx.com doesn't want me to register: "Your registration could not be processed at the moment. Please try again later." gmx.net seems to blacklist Tor, too: Registrierung leider nicht moglich! Sie haben versucht, sich mit der IP-Adresse 77.247.181.162 bei GMX zu registrieren. Diese IP-Adresse ist nicht zugelassen. Whatever it means, but it looks like "you are using Tor, so flick off". - From the link provided by nusenu: Sigaint doesn't allow pop3/smtp unless you buy a pro account, which is quite expensive... mailbox.org allows only 30 days for free. riseup.net is the provider I'm using currently, but I'm not happy with it and that's why I'm looking for another one... mail.ru is in Russian, too... any way to switch to English? mail2tor, according to the site, is not very reliable. bitmessage.ch doesn't seem to allow creating custom addresses. Doesn't look good, maybe it's time to learn Russian... I don't think GMX allows using Tor, but they don't offer anything special - as to privacy, security. They're not a lot different than most others - anymore. What is it about Riseup that you don't like? Just curious. I've not used it, but most people seem to like it. Unseen.is - located in Iceland is a more privacy conscious provider. I've created an acct using TBB in the past. They don't - or didn't - keep logs or store messages after you delete them. They offer end to end encryption - between Unseen users, using their own app loaded on computers. They'll keep encrypted messages on their server, if you want. It's proprietary encryption, which some don't like (can't be independently tested). They claim they intentionally never have the private key, so no LEAs can force them to decrypt or hand over messages. I'm not sure that independent testing of encrypton or software is as relevant today, if - - avoiding state players is a main concern. For protection against _non-government criminals_ (see what I did there?), independent testing is important. Even the largest universities' or security firms' resources are tiny compared to the time, money, talent and computing power that nations put towards cracking encryption, paying for or coercing back doors, or finding exploitable software bugs. I'm sure governments have made huge advances since Snowden's papers in 2013, that we probably will never hear about. -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
[tor-talk] Tor 0.2.9.3-alpha is released
Hi, all! There is a new alpha release of the Tor source code, with fixes for several important bugs, and numerous other updates. (If you are about to reply saying "please take me off this list", instead please follow these instructions: https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce/ . You will have to enter the actual email address you used to subscribe.) You can download the source from the usual place on the website. Packages should be up in a few days. (There is also a concurrent release of Tor 0.2.8.8; for stable announcements, please see tor-announce@ or the blog.) == Changes in version 0.2.9.3-alpha - 2016-09-23 Tor 0.2.9.3-alpha adds improved support for entities that want to make high-performance services available through the Tor .onion mechanism without themselves receiving anonymity as they host those services. It also tries harder to ensure that all steps on a circuit are using the strongest crypto possible, strengthens some TLS properties, and resolves several bugs -- including a pair of crash bugs from the 0.2.8 series. Anybody running an earlier version of 0.2.9.x should upgrade. o Major bugfixes (crash, also in 0.2.8.8): - Fix a complicated crash bug that could affect Tor clients configured to use bridges when replacing a networkstatus consensus in which one of their bridges was mentioned. OpenBSD users saw more crashes here, but all platforms were potentially affected. Fixes bug 20103; bugfix on 0.2.8.2-alpha. o Major bugfixes (relay, OOM handler, also in 0.2.8.8): - Fix a timing-dependent assertion failure that could occur when we tried to flush from a circuit after having freed its cells because of an out-of-memory condition. Fixes bug 20203; bugfix on 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing this one. o Major features (circuit building, security): - Authorities, relays and clients now require ntor keys in all descriptors, for all hops (except for rare hidden service protocol cases), for all circuits, and for all other roles. Part of ticket 19163. - Tor authorities, relays, and clients only use ntor, except for rare cases in the hidden service protocol. Part of ticket 19163. o Major features (single-hop "hidden" services): - Add experimental HiddenServiceSingleHopMode and HiddenServiceNonAnonymousMode options. When both are set to 1, every hidden service on a Tor instance becomes a non-anonymous Single Onion Service. Single Onions make one-hop (direct) connections to their introduction and renzedvous points. One-hop circuits make Single Onion servers easily locatable, but clients remain location-anonymous. This is compatible with the existing hidden service implementation, and works on the current tor network without any changes to older relays or clients. Implements proposal 260, completes ticket 17178. Patch by teor and asn. o Major features (resource management): - Tor can now notice it is about to run out of sockets, and preemptively close connections of lower priority. (This feature is off by default for now, since the current prioritizing method is yet not mature enough. You can enable it by setting "DisableOOSCheck 0", but watch out: it might close some sockets you would rather have it keep.) Closes ticket 18640. o Major bugfixes (circuit building): - Hidden service client-to-intro-point and service-to-rendezvous- point cicruits use the TAP key supplied by the protocol, to avoid epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc. o Major bugfixes (compilation, OpenBSD): - Fix a Libevent-detection bug in our autoconf script that would prevent Tor from linking successfully on OpenBSD. Patch from rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha. o Major bugfixes (hidden services): - Clients now require hidden services to include the TAP keys for their intro points in the hidden service descriptor. This prevents an inadvertent upgrade to ntor, which a malicious hidden service could use to distinguish clients by consensus version. Fixes bug 20012; bugfix on 0.2.4.8-alpha. Patch by teor. o Minor features (security, TLS): - Servers no longer support clients that without AES ciphersuites. (3DES is no longer considered an acceptable cipher.) We believe that no such Tor clients currently exist, since Tor has required OpenSSL 0.9.7 or later since 2009. Closes ticket 19998. o Minor feature (fallback directories): - Remove broken entries from the hard-coded fallback directory list. Closes ticket 20190; patch by teor. o Minor features (geoip, also in 0.2.8.8): - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2 Country database. o Minor feature (port flags): - Add new flags to the *Port
[tor-talk] Help
Hello David Bodnaraszek,
there was a similar issue 11 months ago:
https://trac.torproject.org/projects/tor/ticket/17453
" #17453 closed defect (fixed)
Crashing on Windows 10
[...]
Fault Module Name: d2d1.dll
Fault Module Version: 6.1.7601.17514
[...]
https://trac.torproject.org/projects/tor/ticket/17453#comment:7
So the workaround for users who don't want to wait for the next release is to
create the file Messenger/TorMessenger/Data/Browser/profile.default/prefs.js
with the following two lines:
user_pref("gfx.direct2d.disabled", true);
user_pref("layers.acceleration.disabled", true);"
Your version seems up to date:
"Nom du module défaillant : d2d1.dll, version : 10.0.10586.589,"
Either your version is défectueuse and you just save the old and replace it
with same version.
Or maybe you will downgrade the dll version until a more advanced version is
released (if you didn't got the issue with Tor before).
Please visit a site of your trust to get the version you need of d2d1.dll and
save your old for a backup before replacing it.
https://www.dll-files.com/d2d1.dll.html#
"d2d1.dll, File description: Microsoft D2D Library"
"10.0.10586.0"?
Aloha,
Toruser
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
