HackerTrans
TopNewTrendsCommentsPastAskShowJobs

dcomp

no profile record

comments

dcomp
·10 ay önce·discuss
I think the algorithm is probably incorrect. A number starting with 0 should be treated lexically not numerically. Otherwise you have a situation where img_1_01.jpg and img_01_1.jpg does not have a complete ordering.
dcomp
·2 yıl önce·discuss
there's a setting in the developer options called OEM unlock which allows the bootloader to be unlocked

It is still shipped locked. Unlocking wipes the device.

It also doesn't work if your device is carrier locked.
dcomp
·3 yıl önce·discuss
I think the plan is for each GP's prescribing system/appointment system to export enough data that you can just use the NHS app for your needs. i know I can book appointments through it. Obviously doesn't help when the GP is still sifting through paper records. But those are few and far between.
dcomp
·3 yıl önce·discuss
I'm only slightly familiar with the specific features ACPI provides. But isn't the solution the following

For every "feature" provided by the SMM or bios.

Export a UUID ( eg NVME resume implementation1) Have that feature have an enable and disable function. Have each feature have a dependency on each iorange / firmware device it needs access to.

If the kernel know how to implement the feature it can just disable the feature and then as long as it follows the dependency tree and can see nothing else accesses those ranges. It can know that it has exclusive use. If it doesn't have exclusive use it must use the firmware to access those ranges if possible or fall back to no support

If the firmware has a feature without a disable function. The kernel knows it can never access that hardware directly/safely.

You could even have a "lock device" that if you take you know that SMM won't access those io ranges whilst you have the lock.

Obviously this all requires vendor support
dcomp
·3 yıl önce·discuss
I thought there was already common terminology for probability of side effects [0]

Very common = greater than 1 in 10

Common = 1 in 100 to 1 in 10

Uncommon [formerly 'less commonly' in BNF publications] = 1 in 1000 to 1 in 100

Rare = 1 in 10 000 to 1 in 1000

Very rare = less than 1 in 10 000

Frequency not known = frequency is not defined by product literature or the side-effect has been reported from post-marketing surveillance data

[0] https://bnf.nice.org.uk/medicines-guidance/adverse-reactions...
dcomp
·3 yıl önce·discuss
I'm getting office365 nagging me to change the pdf viewer on android after each download in chrome about 15 minutes after the download. Can't find the setting to stop it.
dcomp
·3 yıl önce·discuss
For those wondering, this is a joke from the LTT WAN Show [0]

[0] https://www.youtube.com/live/CSOF8RFrihM?feature=share&t=982...
dcomp
·3 yıl önce·discuss
I've switched to tailscale because their nat busting is actually hard to do "by hand"
dcomp
·3 yıl önce·discuss
Most likely an early disconnection fee during the minimum term. Nearly everyone has a minimum term with virgin media as they only apply promotional discounts if you have a 12,18 or 24 month minimum term and the price shoots up as soon as you roll over onto the monthly.

[1] https://www.virginmedia.com/legal/fibre-optic-services-terms...
dcomp
·4 yıl önce·discuss
Technically they could force root nameservers (based in the US) to intercept/proxy the whole gtld.

So all except n (netnod (EU)) and i (WIDE (JP))
dcomp
·4 yıl önce·discuss
> The only thing that concerns me now is the Rust code in kernel is not GPLv2. Not sure if that's intentional.

The only code that isn't GPLv2 is the alloc crate. Which is basically a copy of upstream with some changes. All the kernel specific stuff is GPL
dcomp
·4 yıl önce·discuss
From what I understand a rust panic will just call BUG(). There is no support for unwinding as such.

Most likely you would have to use .get() which returns an Option rather than [] array index which panics.
dcomp
·4 yıl önce·discuss
It's quite scary that the House of lords (unelected peers), previously seen as undemocratic may be the only thing stopping the commons from rushing through legislation as they don't have to pander to public option. Which I guess was always their purpose
dcomp
·4 yıl önce·discuss
To be fair they have been monitoring deaths before [0], just the first time there's a national warning to the public.

Quite a few schools have decided to use this warning to close as they are unable to manage heat on their premises [1]

[0] https://www.gov.uk/government/publications/phe-heatwave-mort...
dcomp
·4 yıl önce·discuss
And for further context its the first RED (danger to life) warning [0] (for the purposes of heat, other red warning have been issued [1])

[0] https://www.metoffice.gov.uk/about-us/press-office/news/weat... [1] https://www.metoffice.gov.uk/weather/learn-about/past-uk-wea...
dcomp
·4 yıl önce·discuss
dcomp
·5 yıl önce·discuss
Probably because you can't dispute for any reason. But if there wasn't enough notice. If you don't give 10 working days notice (unless initiated by the person). An immediate refund can be requested.

Bad service isn't a reason for a refund. And if the person doesn't say "This debit was in error. I wasn't given notice" or similar the bank will usually say this is a legitimate direct debit [0] https://www.directdebit.co.uk/DirectDebitExplained/pages/dir...
dcomp
·5 yıl önce·discuss
In a high security situation. It would not be a password, but a smartcard which authenticates the device before providing its key, and the device authenticating the smartcard.

Edit: For the purposes of the Networked Evil Maid Attacks. Mutual Authentication (of device and user) is currently the purpose of research. It has not needed to be implemented yet as the regular Evil Maid is still possible due to the fact that Secure Boot is currently the easier target to circumvent. Once Secure Boot becomes harder to circumvent and old "assumed" buggy kernels are revoked from running. Networked Evil Maid counter measures will need to be implemented as standard
dcomp
·5 yıl önce·discuss
You have a disk encrypted laptop. That key is protected by a password.

Secure boot means that when you log in you can trust that the disk decryption screen is not a disk encryption key exfiltration screen waiting for you to enter your password so that a disk backup taken earlier can be decrypted.

How?

The disk encryption is based on a key in the TPM which only is decrypted with your password. That TPM gets wiped when you disable secure boot. The result is that when you enter your password either you get a correct decryption key or your disk encryption key has already been wiped. Assuming it's not possible to run untrusted code before the disk encryption key login screen with secure boot enabled.

kernel lockdown is part of the parcel for making sure that untrusted code does not run that can exfiltrate the disk decryption key.