Cryptography nerd
You need to set up a publicly accessible device (in this case the VPS) as your IPv6 gateway
So you set up your VPN connecting your network to the VPS (should probably be set up from the router) and set your router to advertise an IP adress for the VPS which is routable from your local network as the gateway address (and should probably also run DHCPv6 for your network)
(note, I have not set up this stuff myself so I can’t help with implementation details)
And if you don’t know who owns it, leaving a note to ask is simple.
I’ve been the one to leave stuff out that I didn’t have space for anymore, with a note on that it’s free to take
Not everything is hooked up to that
There are coils which can detect current through induction, so you can trigger on press without altering the resistance of the circuit
With an automated refactoring step to pretend it’s really not derivative work despite being extremely derivative
Some dumb shit I see is setting SPF so Google is a trusted origin for email “to solve issues with sending to Gmail addresses” when what you’re supposed to do is add your mail servers as trusted origin.
Directionality, how does it work?
CF has multiple options, you can use them as just a load balancer/firewall while handling your own TLS cert. I think most let them hold the cert so they can get CF caching services though
Robots can definitely flip burgers.
Some can even do it twice!
Exclusively using Discord as a support channel should get you banned from the internet
An application password, basically
I have a frozen license with them which they’ll reactivate once I give them the receipt information they didn’t send me when I bought it from them…
I have a lifetime license from another company that got deactivated for similar reasons, and support is useless because they demand information I wasn’t given when buying it from them directly
Not for distance, however when you start doing fuel calculations it gets counted in
That’s a second pre-image attacks when you’re targeting existing state (attacking hash values of existing data by creating a second file matching it). For some reason even with MD5 that’s still infeasible - but collision attacks where you don’t have a target output value, but instead have partial target inputs which need to have the same output hash, are however practical and fast.
Tldr, modern hash algorithms process data in fixed size blocks. For MD5 you take 128 bits at a time.
The core function in a hash is a little scrambler function (permutation) that takes two different inputs and gives you a single output back.
So it starts with a fixed value built into the algorithm, and then scrambles the first block of the message with it. Then it takes that scrambled piece and mixes that with the next block of the message, then takes THAT scrambled piece and mixes it with the next block. And so on until the end of the message. The last scrambled piece is the hash value.
Collision attacks target that core function by figuring out how to tweak multiple messages so that their scrambler outputs “collide”, ending up equal. So you can hash two tweaked messages and get the same hash value. These tweaks usually include a bunch of random looking bits to work.
Then for a multicollision we don’t just do it for two messages. We do it for every letter in the alphabet. For a HTML document we encode something like <div hidden garbage=xyz>a</div> and repeat for every letter. Every letter gets a distinct random looking value. Then we have many documents with the same hash and one letter different. We can show you a hash and then pick which letter to present you with in the document. All of them checks out.
But then we repeat the attack. We add another whole alphabet right after the first one! Now we have <div hidden_garbage=xyz>a</div> <div hidden_garbage_2=xyz>a</div>. And because the second letter is in a different block, that works just fine! Adding a second letter don’t change the first intermediate value, and you can attack the second intermediate value for the second letter separately. So you add the whole alphabet again (with new associated calculated garbage for every letter in the second position), and now after the second letter we have a new intermediate value which is the same regardless of which letter we pick in the second position.
So now we can independently pick a random letter in the first position and in the second position too! Every combination of two letters has the same hash because of the hidden calculated garbage after each letter!
Then we just repeat the multicollision attack on the whole alphabet over and over until your document is long enough to encode your message. And that message may include the document’s own hash.
Pretty Good Privacy (proprietary original)
GNU Privacy Guard (open source clone)
OpenPGP is the shared spec
I mean if you’re prepared to do it 2^128 times in a row…
Also so many head photos taken from an angle right in front of the face or a bit higher, distorting the shoulders in ways you don’t notice but which matters when the algorithm tries to splice everything together into an averaged model