Avatar
Dr. Hax
d30ea98ea65e953f91ab93f6b30ea51eb33c506f87d49f600a139aef00aa9511
Cypherpunk. Infosec veteran of about 15 years (vulnerability research, exploit development and cryptography). Cypherpunks write code. :-) Signet maintainer. Self-custody your passwords... in hardware! https://hax0rbana.org/signet Want to see wider adoption so Bitcoin can be used as digital cash and not just an investment vehicle. XMR: 44RDkTFmTeSetwAprJXnfpRBNEJWKvA5dBH5ZVXA4DofgoZ9AgjyZdSa2fo7pMD3Qe3pdKga8X22y3Lyn1xYde5kPQPzVUu

Saw this at the grocery store the other day, thought #bitcoin #nostr would get a kick out of it.

The fine print not apassword, it is about how to enter people's ID. It just highlights that while it doesn't work, if it did, it'd only work if you give them ID.

Need some hacking/programming tunes? I got you covered:

https://invidious.privacyredirect.com/watch?v=Y91C2yTq8BQ

When you get accused of being a #hacker because you run #nmap, tell them that you are just a #network cartographer, trying to make sure your maps are accurate. 😛

If I open my wallet I can see the notes but that's just it, I don't open my wallet.

I just send zaps directly from Amethyst and on the notifications pane, I see when I've been zapped, by whom, related to which note, and the amount, but no lightning transaction message.

Yes.

A. F-Droid only allows completely open souce stuff and informs you about things like whether it has privacy concerning features like trackers, relies on connecting to a closed source server, etc.

B. Obtainium doesn't give you any of those guarantees, but you can pull from a lot of different locations including .APKs from Microsoft GitHub releases, and

C. Aurora only allows you to get things listed on Google's play store (same backend)

The issue was Sender -> Tor -> GMail -> Destination was being treated as if the mail came from Tor instead of from GMail because Google leaks the Sender's IP address and SpamAssassin apparently uses all the Received From headers by default .

It looks like by using notfirsthop and trusted_networks it can be configured to only use the Received From headers added by the Destination MTA.

This way there's no need to try to manually create and curate a list of all Tor exit nodes.

I'm imagining a Capture The Flag (CTF) game where the #challenge is to bypass some network control (aka #censorship) that is used in the real world.

Maybe you'd #VPN into an environment where the gateway has some annoying restriction and your mission was to #circumvent them.

The point wouldn't be the specific #tactic used to bypass a particular #control, but rather to get people thinking about how to bypass controls in general. That way when some new one comes along, you'll be able to probe, adapt and overcome!

At the same time, the group running it could learn more about what controls there are out there, especially ones that aren't commonly used in their country.

Does anyone here know how to get SpamAssassin to only look at the last hop instead of looking at every MTA that a message has gone through?

Failing that, do you know how to configure it to not punish Tor users?

I can find lots of guides on configuring rules, but nothing that answers these specific questions.

There is also I2P, which has been around longer, is battle tested, has a bigger community, and is basically the same thing.

I asked the developers why they made #Veilid instead of contributing to #I2P and they said they didn't know much about I2P.

#privacy

And they already have radios for remote detination. Pretty crafty, and as long as you don't care about killing nearby civilians and bombing funerals, I mean, why not go down this road, right?

For anyone who is seeing out of context references to pagers, walkie talkies, and explosions, here's what they've referring to: https://www.axios.com/2024/09/18/israel-detonates-hezbollah-walkie-talkies-second-wave-after-pager-attack

That was my initial thought, but the blocks were numbered sequentially. If it were a fork, I'd expect there to be two competing blocks with the same number.

Based on the comments and links in the replies, it seems like the most likely explanation is that someone's clock was significantly off.