

Microsoft SSH agent persistently stores your unencrypted private keys in the registry. They’re still there unlocked and usable after you reboot.


Microsoft SSH agent persistently stores your unencrypted private keys in the registry. They’re still there unlocked and usable after you reboot.


No my dude, they’re trying to keep the stuffed pie holes off their internet.


you originally said
they cannot tell who’s using a VPN
I was replying to that specific statement only. Lists of IP ranges are updated regularly and publicly available. Web sites hosted in Utah will have to make use of them to ID check visitors to comply.
I agree with you that web sites hosted outside of Utah should just block Utah IP addresses with a “contact your representative” message."


wouldn’t reveal to a website where the traffic is coming from
that’s… exactly the point here. If you’re connecting thru a VPN then the web site is supposed to ID you because you might be circumventing their local ID laws.


It’s actually quite trivial to detect most VPN providers. There’s publicly available IP lists


Yeah indexes of VPN provider IP ranges (and VPS providers and such) already exist. If you want to get around that you need to find a residential ISP SOCKS proxy provider.


The bill targets “operating system providers” and it’s called GrapheneOS. So yes, they would be subject to this law if they are based in USA.


@grok is this true?


There’s nothing as permanent as a temporary fix.


But only the toilet has an open hole in the middle for your butt to hang down through, and you’re usually not spending any time trying to push out a turd on any seat that’s not a toilet.


took me too long to figure out to read it as re-styling rather than resty-ling.


I replaced Pixel launcher with Lawnchair. Very similar UX but let’s you do things like set the search bar to just open your default browser.


could you not just get a data-only SIM?


you learn more by having to read a whole page to find a sentence and then write your full sentence answer by hand than you do by hitting ctrl-f, ctrl-c, ctrl-v on the keyboard. You miss out on the surrounding contextual information.


If it’s open source it can be verified that it’s not storing the data.
And I 100% agree that software scanning an ID is an overall bad way to verify. With a CC# validation at least that shows up on my statement, but if my kid is sneaky enough to get mine out of my wallet I have no way of knowing.


I feel like #1 and #2 are problems whether its client side or server side. As for #3 I would lean in the direction of there being a one-time check with no persistent knowledge. Like when you flash your ID to the bartender to order a drink. A client app that scans the ID and returns the answer to the requestor.
But I don’t think there is any way to reliably implement this sort of thing. I think it should really just be left to parental control and monitoring.


Some kind of cryptographic signing of the executable could probably help with that.
Ultimately I don’t believe there can ever be a foolproof solution and the emphasis should be on client-side parental controls.


This goes in a better direction than web sites doing it themselves, I think. The government put out an open source tool that runs locally and the browser just gets a yay/nay return code from it.


I just bought a few WD drives direct, but their web site has a problem with validating virtual credit card numbers. I’m the few days it took to resolve it the price went up. Fortunately since I had the support ticket I was able to get refunded the difference.
copied from my mastodon