32032141

Right. The first CVE gets you for example, cross window access. The second gets you system access outside of the sandbox.

What an absolutely worthless website.

"Your browser does not support WebGL"

They're basically all exactly this though, no matter what you're paying this is generally what is underneath. Competent encryption in hardware is difficult, so everybody is doing it in software, and then why id the software hardware specific to begin with?

This isn't for personal use, so no calls. The data rate is probably around 2-5c/MB for Canada (though its not on the pricing list, that seems to be average), which puts it above even Rogers consumer plans. Google Fi is intended for consumer use and is 1c/MB in Canada (up to a cap, and then unlimited).

This is for Internet of Thing usage, the customer is a company who is making Internet Widgets with some need to be able to communicate no matter where their Internet Widget is operating, without necessarily having to configure or prepare for the destination.

I've been wondering for a while what the purpose of all the NB band LTE stuff is even for. The going rate is often around 40c/MB in most countries (lower on Twilio by the looks of it, but the same order of magnitude), which seems like there's some very specific high value-per-byte application intended. Some of the technologies people are touting for very long battery life have transmission latencies of 10+ seconds as a trade off, which makes the applications for it even more restricted.

It feels like the result is going to be that literally every device you can purchase will have a always connected LTE lojack attached. Imagine trying to firewall or restrict the network in your business when literally everything has its own backbone, it'll be a complete nightmare.

Just use ProxyJump. You basically should never be using agent forwarding.

I didn't realise Firefox came with that sort of backdoor.

I don't really see a situation in which someone has local file read access on your machine, but doesn't otherwise have you completely owned.

I genuinely don't understand downvoting a series of very realistic comments about what using a Yubikey is actually achieving in these situations.

I personally don't see the point in them at all, in implementation and reality you get basically zero use out of the things.

Services that support them either have them locked down so hard that if you lose a single Yubikey (there's often no backup second key option), you're very screwed. Others go the other option, and have too easy to reset systems, SMS fallbacks, or other total bypasses of the security tokens.

For SSH and GPG, authentication keys are generally the least of your concern. The content you're controlling are much more valuable than the authentication itself. Can an attacker just wait until you SSH somewhere, and leverage that access? Can they wait until you'd press the button for another benign purpose and use that authentication in a malicious way? The answer is almost always yes, which reduces the value of these sort of devices substantially. They don't protect against local compromise, in which case a keyfile sitting on your local host is just as secure and a lot more convenient.

2^32 milliseconds.

" I've only gotten a handful of viruses or malware "

This is a variation of the bad toupee fallacy. You won't notice viruses and malware, almost by definition.