done. some didn’t work with archive.org I used archive.fo instead, some of them redirects to onion when it detects tor ip so I couldn’t save them, some didn’t work on both services
1 Like
These are currently down:
ipfhnseo4hgfw5mg.onion#Fairfax Media https://securedrop.fairfax.com.au
strngbxhwyuu37a3.onion#The New Yorker The New Yorker
xmrto2bturnore26.onion#https://xmr.to
tinhat233xymse34.onion#https://thetinhat.com
vivmyccb3jdb7yij.onion#0xacab.org
I expect the last three to become online soon
1 Like
Probably same operator:
n3txnhg64swyjlty.onion#http://ev0ke.net
ygzf7uqcusp4ayjs.onion#[tor-dev] Graphs - Estimated Traffic Capacity
Do we group them separately or together with torproject?
Btw, I have grouped nrktipspgpsyoqwo.onion#NRKbeta with Espen Andersen yesterday
1 Like
Please repost then.
Group the two above but not group with torproject.
Okay.
The first 3 addresses are back online
I just contacted thetinhat about the situation, apart from 0xacab.org riseup’s 2 other addresses are also down
nzh3fv6jc6jskki3.onion#riseup.net
cwoiopiifrlzcuos.onion#black.riseup.net
1 Like
All addresses that are currently down:
pool 1:
dcdoialeklnkb6fg.onion#ICIJ
a5gvhrpulvq33b3q.onion#The Oregonian
efeip5ekoqi4upkz.onion#MormonLeaks
mz33367mcdrcdi7s.onion#Dagbladet
ipfhnseo4hgfw5mg.onion#Fairfax Media
pool 2:
eljwdzi4pgrrlwwq.onion#https://citizen-cam.de Searx instances · searx/searx Wiki · GitHub
pool 3:
nzh3fv6jc6jskki3.onion#riseup.net
cwoiopiifrlzcuos.onion#black.riseup.net
vivmyccb3jdb7yij.onion#0xacab.org
Should we group Devuan and heads together? heads developer parazyd is also a Devuan developer:
https://www.devuan.org/os/team/
https://files.devuan.org/devuan_jessie_rc/embedded/README.txt
https://files.devuan.org/devuan_jessie_rc/virtual/README.txt
New addresses?
o2jdk5mdsijm2b7l.onion#https://search.gibberfish.org
nxhhwbbxc4khvvlw.onion#https://searx.gotrust.de
anonymous1:
Should we group Devuan and heads together? heads developer parazyd is also a Devuan developer:
Yes.
I added Gibberfish search since it has an organization behind it, not sure about the other one:
there is nothing on the main domain
it’s likely not malicious but I don’t know how long it will stay alive
do we find out by giving it a chance or not?
@Patrick we didn’t add these addresses since they don’t reply with date headers
lqdnwwwmaouokzmg.onion#https://searx.laquadrature.net
searx.cwuzdtzlubq5uual.onion#https://searx.fossencdi.org
Can we use these addresses since they seem to work?
http://lqdnwwwmaouokzmg.onion/static/themes/oscar/img/logo_searx_a.png
http://searx.cwuzdtzlubq5uual.onion/static/themes/courgette/css/style.css
How do you want to do this? Should I re-paste the ones I like in a post and ping you to add them in git?
@HulaHoop No need to touch git for this one. @anonymous1 is extending its already existing pull request. ( Add new addresses by anonmos1 · Pull Request #19 · Kicksecure/sdwdate · GitHub ) (Reviewing those is a separate task.)
You’d just read his posts here. The latest posts by @anonymous1 I haven’t answered are these ones:
- Suggest Trustworthy Tor Hidden Services as Time Sources for sdwdate - #92 by anonymous1
- Suggest Trustworthy Tor Hidden Services as Time Sources for sdwdate - #93 by anonymous1
And the website / organization suggested, you’d just say yes we take it or not.
1 Like
Its up now. Please go head and add.
I guess if they point to permanent webpage assets that are unlikely to be renamed then yes. We can always detect if they change them and break later.
1 Like
@Patrick a number of websites hosted by cloudflare have onion addresses too. Since Cloudflare is a GPA its something we better watch out for. I wanted to know how to detect domains hosted by them.
1 Like
Are you sure that Cloudflare hosts them? As far as I know, Cloudflare is a man-in-the-middle, redirecting (non-static) requests to original server. Those onion addresses should be safe
I don’t know and I don’t know how to confirm either way. Do you know of any info that can help answer this?
Last time I saw CF were thinking about creating .onion sites for cutomers automatically and redirecting Tor users to them. Since they are a MITM-as-a-service I’m skeptical that they won’t be in the equation somewhere
The first would be to make it easy, or maybe even automatic, for CloudFlare customers to create a .onion version of their sites. These .onion sites are only accessible via the Tor network and therefore less likely to be targeted by automated attacks. This was Facebook’s solution when faced with the same problem. We think it’s elegant.