@jernej__s @0xabad1dea On the Workstation the time is correct, though, and that is part of the same AD domain.
B
berglerma@mastodon.social
@berglerma@mastodon.social
Posts
-
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought. -
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought.@0xabad1dea Yeah you can't toggle that either. You can press the "Sync now" button, but that doesn't do anything
-
I keep being panicked about it being later than I thought, only to be confused five minutes later when I check again and it's not as late as I thought.@0xabad1dea I have a work laptop like that. It's 10 minutes ahead, even though it claims to automatically set the time via NTP. What's worse, because these settings are managed by an organization, Windows doesn't even let me set the clock manually to fix it.
Luckily, I also have a workstation that doesn't suffer from that issue that I use 99% of the time. The laptop is only needed for a few in-person meetings, but when I'm using it I'm also always thrown off by the wrong time.
-
So I’ve just had a quick play with this and yes, it works.@gsuberland @mkoek @GossiTheDog Unless Microsoft made another mistake this shouldn't be possible. Accessing disk encryption keys should always use what is called a "salted session", where the communication between TPM and application is encrypted, precisely to prevent passive attacks on the bus.