• 0 Posts
  • 22 Comments
Joined 11 months ago
cake
Cake day: August 17th, 2023

help-circle
  • Nothing stopped the person from calling road service to wire the car up, save for the fact that a child was involved.

    But there was. And ensuring the kid is safe takes top priority, and the last thing anyone wants to hear is another case of emergency responders dragging their feet while another kid dies. Smash your way safely into that car, THAT is what they are trained to do.

    Firefighters deal with a lot of shit and receive lots of training. I would argue that most firefighters know about the issues being laid out, and policy, not lack of knowledge, dictates a process to be carried out. I really don’t think this is a situation they should be vilified over if it saves lives.

    Edit: If it wasn’t clear, nobody is complaining about getting off work and finding out their car is dead, and having to call the fire department to show up with the jaws of life.










  • Close, but you are still trusting the device you own. If I were to compromise that device, I could capture that key and use it. Again, this is my limited understanding, but a zero trust solution works in such a way that the actual keys are not stored anywhere. During setup, new temporary keys are generated. A keypass binds to the temporary key for use of authentication. The temporary key can be revoked at any time for any reason, whether it’s due to a breach or routine policies. It can be as aggressive as it needs, and the implication is that if someone else (either you or an attacker) got issued a new temporary key then the other would not receive it. Using an incorrect temporary key would force an initialization again, using the actual keys that aren’t stored anywhere.

    The initialization process should be done in a high trust environment, ideally in person with many forms of vetting. But obviously this doesn’t take place online, so there is the risk that your device is not trusted. This is why the process falls back on other established processes, like 2FA, biometrics, or using another trusted device. How this is done is up to the organization and not too important.

    But don’t get too hooked on the nuances of passwords, keys, passkeys,etc. The entire purpose is to limit trust, so that if any part of the process is compromised, there is nothing of value to share.

    Disclosure: Worked in military and this seems to be a consumer implementation of public/private key systems using vector set algorithms that generate session keys, but without the specialized hardware. It’s obviously different, but has a lot of parallels, the idea in this case is that the hardware binds to the private/public keys and generates temporary session keys to each unique device it communicates with, and all devices can talk with members of it’s own vector set. Capturing a session key is useless as it’s constantly being updated, and the actual keys are stored on a loading device (which is subsequently destroyed afterwards, ensuring the actual key doesn’t exist anywhere and is non recoverable, but that’s another thing altogether). My understanding of passkey systems is solely based on this observation, and I have not actually implemented such a solution myself.


  • From my understanding it’s the concept of trust. Basic passwords are complete trust that both ends are who they say they are, on a device that is trusted, and passing the password over the wire is sufficient and nobody else tries to violate that trust. Different types of techniques over time have been designed to reduce that level of trust and at a fundamental level, passkeys are zero trust. This means you don’t even trust your own device (except during the initial setup) and the passkey you use can only be used on that particular device, by a particular user, with a particular provider, for a particular service, on their particular hardware…etc. If at any point trust is broken, authentication fails.

    Remember, this is ELI5, the whole thing is more complex. It’s all about trust. HOW this is done and what to do when it fails is way beyond EIL5. Again, this is from my own understanding, and the analogy of hardware passwords isn’t too far off.





  • You are exaggerating. You can complete the entire MSQ up to EW in less than 3 days in-game playtime. Source: You can find raiders with alts that have sprout icons, and I’ve done it myself twice.

    But I get it, you need to know exactly what to do and skip cutscenes. You also can’t do any side questing and once you leave an area, never look back. Which most would rightly criticize me for suggesting. The story is good.

    Honestly, if the concern is anything other than the story, it’s probably not the game for you anyways.

    I’d also like to point out that most content is built to be relevant, so you’ll be doing content with the rest of the player base in just a few hours of playtime. We have the opposite queue problem in contrast to other games: You aren’t waiting for other new players to show up to complete content; you are waiting for the servers to fit you into a party that hundreds of other players of various levels want to also do.



  • From a birdeye view, nothing. And that’s not what the designation attempts to address. It’s not even about how fast the hardware is, as encryption doesn’t require lots of processing power and key delivery systems are relatively simple devices.

    It’s about control. Encryption in general is robust and nobody directly tries to break the algorithm. Most breaches are done by bypassing the encryption entirely. By adding a hardware component, it makes it very difficult to do so. It also creates a one-way bridge for key delivery - once you put keys into the device you cannot remove it. The only option is to delete it. Most of the devices are also hardened - they emit no signals, resist interference, and have various preventions that will dump keys and software in the event the device is tampered with. Add to the fact that because it’s physical in nature and not some boogeyman subsystem buried deep in a server, you can point to it, tell someone to guard it, and put it in a vault. Most also have an accessible wipe button, which makes it easy to prioritize what gets destroyed if the need calls for it. There are many more things, but I think I made my point.

    It’s still hard for the consumer market to have a physical component for encryption. Even for those that do, it’s still not robust enough. You can get legitimate military-grade encryption, with all its bells and whistles, but it’s incredibly expensive and requires specific requirements by the NSA. But afaik, there is no cheap alternative, and most of what you see being advertised is just marketing gibberish.




  • No. The fallacy is believing that the stories of military service will straighten people right up is flawed. Certainly it has the potential to do that, but you ignore:

    1. Most people already know empathy before joining.
    2. The worst of the worst get kicked out.
    3. Lessons will stick after the fact.

    What you get is survivorship bias. Of course the people who aren’t getting entry level discharged or dishonorable discharge have the qualities needed to have or learn empathy, following orders and working as a team.

    Fact is, military isn’t a perfect fit for everyone, and forcing people to do so runs against cohesiveness, morale and effectiveness. It should only be used in the most dire of situations.

    Mirroring this onto service industries wouldn’t be effective at all for the people that need it. I would argue it would make it worse, as these people would see it more of a punishment than a lesson, and only serve to drag down and consume resources for the vast majority of individuals who don’t need the lessons.