p_ing

79 ms·

1441.
by p_ing 2y ago
> What happens when the encryption is broken in the future? Your great, great grandchildren will be embarrassed of the websites you visited.
1442.
by p_ing 2y ago
My take: Any prediction 10 years into the future about technology will be incorrect one to two years from the date of prediction thus making such predictions is not a good use one one's time or electrons.
1443.
by p_ing 2y ago
This is not the case on NT. The OVERLAPPED data structure allows for async file operations. https://learn.microsoft.com/en-us/windows/win32/fileio/synch...
1444.
by p_ing 2y ago
And in either case, it doesn't matter in the eyes of Microsoft. Drive manufactures couldn't be trusted -- and honestly, the amount of "awesome" software coming from component manufactures is pretty small. The drive manuf
1445.
by p_ing 2y ago
Both Crucial and Samsung, which produce a significant number of OEM drives for the likes of Dell, HP, etc.
1446.
by p_ing 2y ago
TPM is now in firmware and has been for quite a few years on Intel and AMD processors; Intel's on the PCH which is on-package and AMD's on-die. This isn't true for all implementations of TPM, but for AMD/Intel/Qualc
1447.
by p_ing 2y ago
Lest one forget NSAKey! /s This type of /r/ufos|/r/aliens speculation isn't particularly useful. It comes with no evidence of TPMs being backdoor'ed. Have they been compromised [at least pre-2.0]? Yes, in
1448.
by p_ing 2y ago
Intel has this via their Total Memory Encryption feature today. Yes, geared towards VMs in the Windows ecosystem. https://techcommunity.microsoft.com/blog/windowsosplatform/m... Memory compression has been around
1449.
by p_ing 2y ago
The Intel PCH is on-package exposed via [DMI] PCIe lane while AMD's fTPM is on-die. It would be unusual for any current device to have a discrete TPM, at least in the consumer space given current x86 processors have an fTPM.
1450.
by p_ing 2y ago
BitLocker no longer leverages SED by default due to vulnerabilities in drive manufactures firmware as of Sept 2019. > Changes the default setting for BitLocker when encrypting a self-encrypting hard drive. Now, the default is to use soft
1451.
by p_ing 2y ago
Since the NT kernel is async throughout, it solves this with periodic priority boosts for non-running but runnable threads. I swear, the kernel designers just need to look at NT :-P But we're well beyond a complete rewrite of old kerne
1452.
by p_ing 2y ago
> The bigger issue is that no OS was designed for expansive and flexible async functionality. The NT kernel was designed in this very way. All I/O in the NT kernel is async. It was one of the design principles.
1453.
by p_ing 2y ago
> io_uring "is largely a copy-paste of RIO" if you wanted to be childish. This was unnecessary. I'm not denigrating I/O Rings or io_uring. The NT kernel is more advanced than the Linux/BSD/macOS kernels in c
1454.
by p_ing 2y ago
Microsoft implemented I/O rings in an update to Windows 10 with some differences and it is largely a copy-and-paste of io_uring. It's important to note that the NT kernel was built to leverage async I/O throughout. It was par
1455.
by p_ing 2y ago
Sadly no PowerPC ThinkPads :-(
1456.
by p_ing 2y ago
Visually, it's on the bridge of the Enterprise D [0][1]. Everyone else has to use a bucket [2]. [0] https://cygnus-x1.net/links/lcars/blueprints/star-trek-the-n... [1] https://memory-alpha.fan
1457.
by p_ing 2y ago
The author 'LOL's at Windows keeping a game going while under heavy memory pressure, but this is the correct approach. Killing a random process due to OOM is not good, especially when it can lead to data loss. Windows does not dis