If nothing else, use it in combination - the encryption of OPAL drives is always active anyway, all that changes when the feature is "active" is whether the key is stored as-is on the controller or whether its protected by a passphrase.
9,034 karma · joined January 12, 2017
If nothing else, use it in combination - the encryption of OPAL drives is always active anyway, all that changes when the feature is "active" is whether the key is stored as-is on the controller or whether its protected by a passphrase.
The real mitigation is the memory encryption feature of modern CPUs. Being on-die means tweezers won't reach, and being just a key means the wipe is instant and very difficult to mess with even if it survived a power cycle.
Their main purpose is to generate and store keys that cannot leave the device, instead performing signing operations as needed internally and only returning the result, and only if attestation passed. This is a lot better than just having private keys on disk.
People just forget that security isn't absolute, and each solution has a threat model it is appropriate for. In case of full disk encryption, neither a TPM nor user input can protect against evil maid on its own for example - the TPM will unlock for anyone, while user input might be collected by a modified and malicious bootloader. Having both, however, works well.
"TPM" is a bit dated as a term as it's all directly built into the processor nowadays, including for smartphones and such. Another modern feature in that catalogue is memory encryption, which rules out the attack described by OP as the rebooted machine would be unable to read old memory content.
Maybe their lens is variable focal length, providing more magnification in the center at a presumed cost of clarity.
Things quickly become quite a lot less trivial than it initially seemed, and then you end up needing an actual toolkit.
You can certainly pick a more minimal one than a browser, but any application now requires a non-trivial toolkit.
> Qt6 does include a JS engine, but hopefully it's a bit more isolated.
I wouldn't expect Qt and Gtk's JavaScript engines to be better isolated than Chrome. They're just more avoidable.
So, it is not a question for car or not car, but SUV vs. compact, and several copies of the SUV at that as everything bundles the bloody thing. Normally I prefer static linking, but it's a bit much for a browser.
To get over 12 hours of battery life out of a 60 Wh battery - which isn't impressive nowadays with laptops rocking 20+ hours - you need to stay below 5 watts of battery draw on average, and considering that the machine will likely do some actual computation occasionally, you'll need to idle closer to 2-3 watts at the battery including the monitor and any conversion losses.
The really big gains in battery life are from cutting tens to hundreds of mW off things at the bottom by keeping hardware off and using fixed function hardware like e.g. avoiding rendering and doing direct scanout and using partial panel self refresh. Execution units do not turn on and off instantly so pinging them even briefly is bad, and the entire system needs to be aligned with the goal of only using them when necessary for them to stay off.
Efforts like libliftoff to do efficient plane offload to avoid render steps in the display server can save in the area of half a watt or more, but it's not a whole lot of help if applications don't do their part.
Bigger GPUs than your iGPU (or even just later iGPUs) will also likely see even bigger impacts, as their bigger shader units are likely much hungrier.
(As an aside, I am not a fan of kitty - they have really weird frame management and terrible recommendations on their wiki. Foot, alacritty or if ghostty turns out good, maybe even that would be better suggestions. Note that comparing to foot can give a wrong image, as CPU-based rendering pushes work to the display server and gives the illusion of being faster and more efficient than it really is.)
Also, if you do damage tracking, make sure to report it to the display server so they can avoid doing more expensive work blending several sources together, and in case of certain GPUs and certain scanout modes, also more efficient scanout. Depending on your choice of APIs, that would be something like eglSwapBuffersWithDamage, wl_surface_damage_buffer, and so forth.
Without, even if you only redrew your spinner, your display server ends up having to redraw what might be a full screen 4k window, as well as every intersecting window above and below until an opaque surfaces are hit to stop blending.
Missing damage tracking, always painting everything (even when the window is a full 4k monitor), etc. kills performance and input latency when dealing with realistic redraw workloads like text editing, blinking cursors and progress bars. Much too often to terminals worry only about the performance of `cat /dev/urandom`...
Binding with port 0 as argument for AF_INET binds a random available port, not port 0. This is documented behavior of Linux and likely every other OS implementing a BSD-style socket interface.
Also note that ufw is just a tiny, non-standard wrapper for the much more powerful nftables/iptables interfaces
If at some point all new cars have full self-driving capabilities with widely accepted performance, then it's not impossible that after a decade of that as status quo, cars end up shipping with manual driving only being an override for specific maneuvering, and eventually having regular licenses lose rights to manual driving on public roads.
It is only valuable in the sense that it is a very limited resource.
Entirely different concept. Not to mention that ants are very, very far from dogs, dolphins and humans. There is no reason to think that a dolphin would have to share their behavior, nor that a human wouldn't share their behavior - do people really choose to be selfless when they dedicate their life to a company, or are they just mindlessly following the march like the ants? There will be the occasional ant that doesn't do as told, leaving the question of where there are more humans or ants breaking showing independence and breaking out of rank.
For reference, there exist many types of ants that have abandoned the normal ways of ant colonies.
> I didn't say it would reply with words.
It would be even more impressive if it managed to communicate without words - Telepathy is not exactly expected in dogs.
If your dog replies, you either have a truly exceptional dog with human-like vocal cords, or need to see a psychiatrist.
That we are more intelligent is nothing more than an evolutionary decision - our ancestors decided to lead lifestyles where trading base energy consumption for higher mental capabilities made sense.
Other creatures are not on auto-pilot, even if their thought process ranges from simpler to outright primitive. When dolphins endanger themselves to chase away sharks to save humans they go against instincts and self preservation (and thereby anything you'd consider autopilot). On the other hand, humans are the ones that have turned averse to danger and anything out of the ordinary, preferring to stick to "auto-pilot" for safety.
In fact, I'd argue that the supposed response from your dog sounds quite like a human: as long as you keep paying me, I'll do the same mindless daily routine without question.
> I do in fact want a properly functioning service to use my name in a vocative case. ... I also don't want to know to specify the correct version myself, as it's trivially derivable through established rules of the languages.
There would be nothing to discuss if this was trivial.
> Not doing that is plainly grammatically wrong and borderline impolite.
Do you know what's more than borderline impolite? Getting someone's name wrong, or even claiming that their legal name is invalid and thereby making it impossible for them to sign up.
If getting a name right and using a grammatical form are mutually exclusive, there is no argument to be had about which to prioritize.
The only generic solution I can think of would be IPA notation, but it would be entirely unreasonable to expect someone to know the IPA for their name, just as it would be unreasonable to expect a random third party to know how to read IPA and replicate the sounds it described.
You cannot pronounce the name regardless of whether it is written in ASCII. Pronouncing a name requires at the very least knowledge of the language it originated in, and attempts at reading it with an English pronunciation can range from incomprehensible to outright offensive.
The only way to correctly deal with a name that you are unfamiliar with the pronunciation of is to ask how it is pronounced.
You must store and operate on the person's name as is. Requiring a name modified, or modifying it automatically, is unacceptable - in many cases legal names must be represented accurately as your records might be used for e.g. tax or legal reasons later.
The pidgin project is 25 years old, and libpurple is 17 years old. It's entirely fair that a rework is required, and much appreciated that this work is continuing.
No you cannot:
1. Compression algorithms buffer a lot and will have have tendencies to perform large burst writes and in particular large writes on final flush. Instantaneous measurements will therefore not be particularly useful.
2. Compression ratio refers to the average across an entire file, as entropy is not uniform across the input unless you are compressing just noise or just zeros. Some sections might compress extremely well while others do not and end up consuming more space than the input due to overhead.
In this case we’re also dealing with an instrument SVTOL landing in terrible weather which cannot be flown with just an artificial horizon, repeated electrical failures in a short timespan, a disbelief that the aircraft correctly reverted from SVTOL to winged flight mode with all relevant instruments to confirm out - as the site says, “extremely challenging cognitive and flight conditions”. And, a manual that says if the aircraft goes out of control at low altitude, you must eject.
At a high altitude cruise it could have been flown just fine by the horizon while things get diagnosed and possibly diverted to a landing suite suitable for the remaining equipment.
You can keep an otherwise fully functional aircraft in stable level flight using a horizon, but that’s neither interesting nor relevant. This was not a lightweight aircraft cruising above the clouds with nothing around it.
This is not true. The standby display is just a tiny artificial horizon by the pilot's right knee, so when HUD and primary display is out, all you're left with is your speed, altitude and attitude. This cannot in any way or form be considered "the same information" as the primary flight display of an F35B, and leaves you without a lot of control.
Whether you can limp along with such backup system depends entirely on what is going on at the time the primary flight displays go dark. In a fighter jet, that display may in some cases just tell you what angle and velocity you are going to die at. Furthermore, in challenging conditions you might have to make a decision very quickly and might not have time tuning yourself into the standby display and its degraded information.
This type of degraded backups exist in many aircrafts - you don't want the pilot of an Airbus you're in to be confronted with the plane dropping to mechanical law, or even direct law if taking off or landing, even if these modes are technically flyable and well documented.
He only had “basically working” comms, which seems to suggest that it too was degraded, and the instruments referred to as being available is just the tiny artificial horizon display in front of his right knee.
Even if he fucked up severely and needlessly burned an insanely expensive asset at the cost of tax payers, that’s a fuckup from an individual actually qualified for and skilled at flying the thing, unlike everyone at this site.
The whole lot of us would probably have the plane go up in flames before we even got into it.