App store? Yeah we have one, it's called make.
1,316 karma · joined October 17, 2018
App store? Yeah we have one, it's called make.
That is, many physical media collectors do it to have nice box sets to display, or in an attempt to have off-line copies of media, but I have never met anyone who goes to the effort of ensuring long-term readability - which is understandable, it is a huge hassle. Unless you are copying the content to new physical media every so often it will eventually rot and become unplayable.
For example, for optical media the expected lifetime is only a couple of decades depending on the type of media [1]. I believe commercially pressed DVD and blueray are somewhere around 10-20 years.
[1] https://www.canada.ca/en/conservation-institute/services/con... , see table 2.
Google has literally billions of dollars in profits (in part because they use FFmpeg in a bunch of commercial products like Youtube and Chrome), and one of the largest software workforces in the world, including expertise on secure software and vulnerability remediation.
If anyone can afford to contribute back a fix instead of just raising a report, and has the ethical responsibility to do so, it's Google.
As with X.509, any serious usage will involve a hardware security module, so that compromise of the CA host does not allow the key to be leaked. You'd still have a very bad day, but it can be mitigated.
I do think it's a fairly significant flaw that SSH CA doesn't support intermediate CA's (or at least didn't last time I looked into it) to enable an offline root CA.
>Bonus points if the same CA is also used for authenticating users.
The SSH CA mechanism can be used for both Host and User auth, yes.
Keeping in mind, in a real use case this would be tied to something like active directory / LDAP, so you can automate issuance of ssh keys to users and hosts.
Systems configured to trust the SSH CA can trust that the user logging in is who they say they are because the principal has already been authenticated and vouched for by the identity provider, no more manually managing known_hosts and authorized_keys, or having to deal with Trust On First Use or host key changed errors.
You can also set the CA's endorsement of the issued keys to fairly short lifetimes, so you can simplify your keymat lifecycle management a great deal - no worrying about old keys lying around forever if the CA only issues them as valid for an hour / day / etc. .
Overall I think you still come out ahead on security.
It's bad enough I have to see ads outside the house and on tv/internet, I don't need to see them on my fucking appliances. We are living in hell.
The main downside is people will sometimes assume you mean SFTP (not having heard of FTPS or realising they are different), and then get upset when it doesn't work as they expect. However good tooling will support both e.g. Filezilla.
Not to say it isn't a valid way to debug, but there are definately better options available.
There'll be much admin moaning
And servers not glowing
and the NOC crew in tears
It's the most blunderful time of the year ♫
You certainly can. Not productively, but you can.
As the other commenter said, Halon hasn't been a thing for a fair while, but inert gas fire suppression systems in general are still popular.
I would expect it wouldn't be sufficient for a lithium ion battery fire - you'd temporarily displace the oxygen, sure, but the conditions for fire would still exist - as soon as enough nitrogen (or whatever suppressant gas is in use) dissipates, it'd start back up again.
Also as I understand thermal runaway is self-sustaining, since the lithium ion batteries have a limited capacity to provide their own oxygen (something to do with the cathode breaking down?), so it might continue burning even while the area is mostly flooded with inert gas.
I believe it would be similar to an EV car fire, that is, you'd have to flood the area with water and wait for it to cool down enough that thermal runaway stops. Maybe they can do better these days with encapsulating agents but I'd still expect the rack housing the UPS to be a write-off.
I am thinking that you would put a kettle of water inside, pressurise the container, and then boil the kettle (would need a power or gas line installed) and make the coffee using the handling gloves. Then depressurise the container and retrieve the beverage.
I'm no engineer so I would be interested to know if this would set me down a path of "you'll accidentally maim yourself", but I wouldn't think you'd need anything fancy or hazardous in terms of materials or engineering, given most human-made structures exist at 1atm.
Would probably need to be careful to let the coffee sit for a few minutes to avoid flash-boiling it though, unless you're adding cold milk.
It's not just physical items like munitions, but also things like transfers of information (blueprints, technical data, documentation, etc.) or services being performed, regardless of where (inside or outside the USA) or how (paper, electronic, verbal, etc.) it takes place.
Have a look at [1] § 120.50 (Export) and § 120.63 (definition of Foreign person).
>if someone looks at the T-shirt and transmits it out the country they'd be the exporter, not the person wearing the T-shirt.
I believe the person wearing the shirt would be considered the exporter, as that is the point where the information moves from (I'm assuming for the purposes of conversation) an USA citizen to a foreign person.
But again, I could be wrong. Safest bet is not to print the shirt to begin with :)
[1] https://www.ecfr.gov/current/title-22/chapter-I/subchapter-M...
Would it? I'm certainly not a lawyer or ITAR expert, but I would think that if you walked through a public space where you couldn't positively confirm that everyone present (and everyone who might view it transitively via video recordings, live streams, etc.) was OK to access the materiel on the shirt, that would be considered an export and you'd be in big trouble.
However I don't believe I've ever seen it used "in the wild".
This site [1] has some interesting info:
[1886] "The average weight of twenty eggs laid by fowls of different breeds is two and one-eighth pounds. The breeds that lay the largest eggs, average seven to a pound, are Black Spanish, Houdans, La Fleches, and Creve Coeures. Eggs of medium size and weight, averaging eight or nine to a pound, are laid by Leghorns, Cochins, Brahmins, Polands, Dorkings, Games, Sultans. Hamburgs lay about ten eggs to a pound. Thus there is a difference of three eggs in one pound weight. Hence it is claimed that in justice to the consumer eggs should be sold by weight." ---The Grocers' Hand-Book and Directory, Artemas Ward [Philadelphia Grocer Publishing:Philadelphia] 1886 (p. 67)
With similar figures given for 1911 as well. Which would suggest a normal egg in 1905 would be approximately 56g (1 pound/ 8 eggs = 0.125lb per egg).
E.g. if a game console manufacturer wants to retain owner-level control of their console, they can rent it to you for $X per month, which would include a Y% sales/VAT/GST/whatever tax.
And correspondingly if the device is sold to you, they should not be able to do things like disallow you from running custom software, remotely brick the device with a soft fuse, etc. and otherwise stop you from using it freely.
I think there is a middle ground (e.g. you can buy the console and either have it in "secure" mode as it ships from the factory, or choose to "root" the device and gain the ability to run custom code - perhaps this would invalidate the manufacturer's attestation keys from the secure enclave or burn a soft fuse as part of the process, so it no longer passes checks for DRM and so on). However that may not be economically viable as I understand the consoles are often loss leaders on the hardware and the profit is made on game sales and licensing.
I thought I saw something about 996 being made illegal in china a while back, and at a quick search it appears that was the case back in 2021.
Why is it suddenly becoming popular outside of China?
Why waste a whole byte on a bool that has one bit of data, when you can pack the equivalent of eight bools into the same space as an uint8_t for free?
IMO this should be the standard - software engineer should be a protected title, and everyone else would be titled some flavour of software developer or similar.
I haven't the time to read it myself at the moment, but the gist appears to be about "attention economy" and how technology affects our lives. There's a blurb and some discussion on goodreads [1].
[1] https://www.goodreads.com/book/show/38364667-stand-out-of-ou...
And if you fill the engine bay on an ICE car with battery packs during the conversion, the weight distribution will be extremely uneven and cause trouble with the suspension and related components, poor handling, etc.
The left, right, left, right part I can see, but surely up, up, down, down, would be difficult on most steering wheels :)
I don't know the details of the attack in the article, but my speculation would be that it would be vulnerable.
At least until they figure out how to put ads on it.
In terms of compute power this is true. However in terms of design and aesthetics I still find the Cray much more charming than the Pi (even if you start adding fancy cases and so on).
This should probably be the case - I am not a big fan of passkeys [1] but hopefully this will help make non-SMS, phishing resistant MFA available to the masses.
Still, Google are in a difficult position where on the one hand they have people angry about being locked out, and yet if they didn't they would have people angry about their accounts being compromised.
> If that means my account gets compromised, that's my problem.
It is also the problem of everyone on your contacts list, the operators of other services which use Google OAuth for login, anyone who might recieve spam from your compromised account, and so on.
Reducing harm by temporarily restricting the account when heuristics indicate it may be compromised is not unreasonable IMO.
>Note that there is no question who owns the account. That's what the password is for!
This is unfortunately not as true as we would like it to be.
Have a look at the list of compromised services on Have I Been Pwned [2] - not all of these include passwords, and many that do would be hashed (and hopefully salted) rather than plaintext, but it still happens often enough to be of great concern.
[1] WebAuthN / Passkey technology is fine in the general sense, and I am quite happy to use it with a hardware security key (such a Yubikey or Titan) or emulated in a password manager.
However I think the recent push towards having it tied to a TPM on a device such as a phone is a bit short-sighted, simply because these devices are prone to being lost or damaged. If you set up passkey MFA on the phone and don't enrol a backup method, then lose your phone, you have also lost the account. Probably these services should require 2+ MFA methods configured.