Feedback Technical Grievances

  • 🏰 Deploying update to the Tatarus security page. If you encounter issues, post here.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
LoogerLike said:
Something I just encountered is the homepage and watched threads page both use 90%+ of my CPU when they're open, but the threads themselves work fine. Using Brave on a pretty crappy computer, but my browser usually only uses around 5% with several tabs open.
Click to expand...
The homepage uses CPU because Sneedchat probably uses a polling loop or something similar, if you delete the sneedchat element in the inspector its cpu usage goes down. You could probably install an extension to always block that element, I don't know which extension would be best suited for this, to not make the protection that Tor browser offers any worse.
The watched threads page doesn't use any cpu when I try it.
 
Null said:
It's not configured on the shield layer because how would that work. That has to be a long term control plane feature
Click to expand...
The header (or meta tag) is ignored if not using Tor Browser. If you are using Tor, its presence will transparently "upgrade" the connection like a regular Location: redirect.

Edit to add: maybe provide a manual link to the onion on the Tartarus page, if you don't want to put the meta tag there?
 
Null said:
The certificate is not revoked
Click to expand...
Firefox in its standard configuration (correctly) identifies that it is, based on the CRL.

TBB does not, because by default it has security.pki.crlite_mode set to 0, so it does not check CRLs.

We can easily download the certificate as follows:
torsocks openssl s_client -connect kiwifarmsaaf4t2h7gc3dfc5ojhmqruw2nit3uejrpiagrxeuxiyxcyd.onion:443 2>/dev/null </dev/null | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > kf_cert.pem

Running
openssl x509 -noout -serial -in kf_cert.pem
then gives us the serial number:
serial=2CC37E0EB02945335D5239EB1201DB7B
(Or, from viewing the cert in the FF/TBB UI):
1786489197986.png

Download the CRL:
torsocks wget http://crl.harica.gr/HARICA-DV-TLS-Sub-R1.crl

And convert it from binary:
openssl crl -in HARICA-DV-TLS-Sub-R1.crl -text -noout|grep -i -B 0 -A 4 2CC37E0EB02945335D5239EB1201DB7B

Code: 
    Serial Number: 2CC37E0EB02945335D5239EB1201DB7B
        Revocation Date: Jul 25 11:01:22 2026 GMT
        CRL entry extensions:
            X509v3 CRL Reason Code: 
                Superseded

Or use a tool like https://ssl.24bitsystem.com/tools/crl-checker
1786489307838.png
The HARICA CRL marks this certificate as revoked.

Apparently, because it has been superseded by a more recently issued certificate? I assume switching to the new one would resolve the issue.
 
okay, well harica tells me it's in good standing, so I don't know. everything's breaking all the fucking time. very glad to hear about how everything's broken all the fucking time.

revoked cert replaced.
 
Last edited:
Billy Beeple said:
The header (or meta tag) is ignored if not using Tor Browser. If you are using Tor, its presence will transparently "upgrade" the connection like a regular Location: redirect.

Edit to add: maybe provide a manual link to the onion on the Tartarus page, if you don't want to put the meta tag there?
Click to expand...
it's not fucking ignored homie it's fucking working on brave but it doesn't appear on the tartarus proxy layer that is the fucking problem because tartarus does not have manual configuraiton to pass an .onion url on a per-domain basis because why the fuck would it. bookmark the fucking .onion. this is an ultra-luxury request that can be made obsolete with client bookmarks.
 
just fyi our current outstanding issue is that we have no future because i can't get reliable ddos mitigation. we're just piggybagging people feeling sorry for us at the moment. nothing else really matters.
 
Null said:
it's not fucking ignored homie it's fucking working on brave but it doesn't appear on the tartarus proxy layer that is the fucking problem because tartarus does not have manual configuraiton to pass an .onion url on a per-domain basis because why the fuck would it. bookmark the fucking .onion. this is an ultra-luxury request that can be made obsolete with client bookmarks.
Click to expand...
I'm missing why you can't edit the HTML of the Tartarus page to include a meta tag (or regular a href to the onion). Possibly because I'm dense.

I'm not saying to do it conditionally, I'm saying clients that can make use of it will make use of it, and others will ignore it. And the clients that can make use of it (people trying to do clearnet-over-Tor) aren't going to get in otherwise, so what does it hurt?
 
Billy Beeple said:
I'm missing why you can't edit the HTML of the Tartarus page to include a meta tag (or regular a href to the onion). Possibly because I'm dense.
Click to expand...
Tartarus is shared between any website that uses it, and it's a nonprofit service, not Kiwi Farms toilet paper to wipe its ass with, so it is wholly inadequate to simply change the HTML. There's plans for a CONTROL PLANE that allows PER DOMAIN CONFIGURATION but that does not exist so it's a core configurable CODING CHANGE for USER CONVENIENCE that can be replaced by USING BOOKMARKS.

But don't worry bud I'm changing the whole fucking thing with a stopgap just for you because you can't work out the bookmarks.
 
Null said:
But don't worry bud I'm changing the whole fucking thing with a stopgap just for you because you can't work out the bookmarks.
Click to expand...
Got it. I don't have a problem, but was trying to suggest a usability improvement for the pathetic losers in this thread that got hung up. I was wrong, you're right--fuck those retarded ass bitches. They're probably undercover H1B troons anyways.

(If Tartarus was open source, or if you want to reach out by DM, I'd be happy to submit a patch. You can -1 it if you think it might help undercover retarded H1B troons get in.)
 
It is under development security software that is being used in production. I am very pro FOSS, the software will be FOSS, but making it FOSS now is a very bad idea.

My #1 priority is DDoS mitigation but I am currently patching in your request and delaying ending my work for the day just for you. I hope this is a satisfactory solution to your requests.
 
At exactly 1400px width, the default letterboxing for Tor Browser, the forum's main content is left-aligned and not center-aligned. Any other width is aligned correctly. Occurring on both clearnet (green) and onionsite (purple). Tor Browser and Brave.
 
Diggus Bickus said:
It's what I've been doing, and for some reason it still gives me this error. I'm unsure if it's my net or what have you.
Click to expand...
Can you do anything at all to provide me more information
 
Null said:
Can you do anything at all to provide me more information
Click to expand...
It's honestly the best I could've provided as accessing through TOR gave me that error, but through clearnet is fine.

A small update today, after tinkering with the router a little bit and resetting it twice, I've managed to bruteforce to be able to use the .onion so I figured it was my net, being detected by Tartarus.
 
no, it's not, because the onion version has different checkers.

please make sure "THE ONION" is LITERALLY .onion and NOT .st over Tor.
 
Null said:
just fyi our current outstanding issue is that we have no future because i can't get reliable ddos mitigation. we're just piggybagging people feeling sorry for us at the moment. nothing else really matters.
Click to expand...
I know that we've suffered a historic attack and all, but it's been a while since the last major DDOS attempt was made, I think the niggers involved are either broke or the botnet supplier was busted. Either way, if they were able, they'd certainly be doing it right now.

Just because the proof of concept exists doesn't mean it's feasible.
 
You must log in or register to reply here.
Back
Top Bottom