NB: the git format itself is not licensed, so only the tooling needs to have a "correct" license.
[0] https://github.com/git/git/blob/master/COPYING is GPL2
2,339 karma · joined October 9, 2014
[ my public key: https://keybase.io/moviuro; my proof: https://keybase.io/moviuro/sigs/SORQVrWsris9gTK1VNIxMBB8nbS1pKzIU1UzhKxa2tM ]
PGP 0x2cd96fee343c6799b9ceafad62009a2e0c22d9ab
GIT/CS d++(-) s+: !a C++ UB++L++ P L++ E- W++ N? o? K? w- O? M- V? PS+ PE- Y+ PGP++ t+@ 5? X R tv-- b++ DI D G e+++ h(---) r++ y?
NB: the git format itself is not licensed, so only the tooling needs to have a "correct" license.
[0] https://github.com/git/git/blob/master/COPYING is GPL2
[0] https://github.com/flathub/com.valvesoftware.Steam/pull/646 ; yes, LOCALE_* env variables make games crash; also, yes, Feral has been totally unhelpful.
Then sadly I won't purchase it at full price. I expect a full experience at full price.
Feral and Paradox for instance only support one (1) distribution. If you fall outside that, you're on your own for support, but you get runnable binaries.
Prefixes shouldn't change, that's the whole point. And you can use fixed addresses for IPv6 just as you had for IPv4.
> each device needs a DynDNS client configured, whereas with IPv4 just the router needs one for my single public IP.
Sure, but if you're doing that at an industrial size, you should consider buying/renting a fixed IP (range). You don't do production at home now, do you?
> IPv6 on the LAN is quite a pita due to the massive "random" prefix
You probably mean suffix? Anyway, your systems can be configured to either not have that random suffix, and they can also be configured to still reply on their fixed address (the one that's not random). Maybe try using the fe80:: address if your prefix does change.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
Aren't ETags exactly meant for that though?
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/ET...
[0] https://en.wikipedia.org/wiki/TGV
[1] https://www.oui.sncf/tgv/services/internet-a-bord
[2] https://www.sncf.com/fr/offres-voyageurs/tgv-inoui/connectez...
Isn't that how the economics of consoles actually are?
The user has to pay for network connectivity (PSN or Gold), publishers have to get their games approved (which was introduced by Nintendo [0]), and then there's a single market for the console (included game store with cut or through authorized discs only).
[0] https://en.wikipedia.org/wiki/Nintendo_Entertainment_System (not as precise a source as I would like) (This was needed to avoid "low-quality" games from ever reaching the consumer, like https://en.wikipedia.org/wiki/E.T._the_Extra-Terrestrial_(vi...
Dell has them at least for their "pro" lineup (e.g. [0]), same for Lenovo [1] or HP [2]. Said "pro" lineup is meant to be serviceable.
It is however the first time that I see a first-party console tear-down.
[0] https://downloads.dell.com/manuals/all-products/esuprt_lapto...
[1] https://download.lenovo.com/pccbbs/mobiles_pdf/t470s_ug_en.p... page 109 onwards
However, that "can't accept emergency patients" is surprising. I don't care if the lights are out or if I can't digitally sign their papers: hospitals should be able to run even with no machines at all. Ideas for next time:
- Paper docs available (already printed) in case everything goes under (banks do that for example, for generic papers, like opening an account, etc.)
- Air-gapped backup machines that can be used on the MRI/scanner/ultrasound/whatever machine (that hardware hardly ever changes, so it's not like those air-gapped machines would be a pain to manage)
- Backup 4G-enabled laptop that can read the vitim's Carte Vitale (or equivalent [0]) (and which doesn't connect to the hospitals network whatsoever)
- Backup hardware (Scanner, Ultrasound machine) in case someone actually fries the regular ones thanks to their horrible security (we've had plenty of such articles on HN)
- Read-only machines. Once it works, unless it's for a patch, the OS and applications shoudln't be changed, at all.
- User awareness training. Ransomware rarely happens by accident: someone clicked a bad document in a phishing mail. (Unless, you know, Wannacry, but that's not the norm)
BTW, use the emergency info of your phone: https://www.androidcentral.com/how-add-emergency-information...; https://support.apple.com/en-us/HT207021
I would have said that too, but during the lockdown and stay-at-home period, it made a meaningful rise, and it fell back when I could go back to walking and doing sports. Fat percentage: made up? Probably not. Precise? Also probably not.
For selfhosting, there's `recipient_delimiter = +-.` in postfix' config. [0]
The most infuriating ones are those where you can subscribe with the '+', but the unsubscribe function errors on it.
[0] https://kodi.tv/
[1] https://play.google.com/store/apps/details?id=org.xbmc.kore
2. It's just a little dev step away: http://blog.cmpxchg8b.com/2020/07/you-dont-need-sms-2fa.html . Phish kits will evolve, UX will still be bad, and phishing will still happen.
Links or it doesn't exist.
Edit: I specified Android, but really, I just want a phone with a standard port (USB C) and my apps (WireGuard, NextCloud, Google Photos, etc.)
I'm getting a Pixel 5 on day one, for the camera, camera app and security updates.
[0] https://www.celsoazevedo.com/files/android/google-camera/
Sure, having an infinite, append-only log of domain names for which an HTTPS certificate ever was issued sounds like a GDPR issue. But if it also helps catch bad actors before they can even set up their phishing pages, I'm all for it.
[0] https://hg.mozilla.org/releases/mozilla-beta/raw-file/tip/se...
uuid -r
See https://linux.die.net/man/1/uuidSome snippets:
> OpenBSD believes in strong security. Our aspiration is to be NUMBER ONE in the industry for security (if we are not already there). Our open software development model permits us to take a more uncompromising view towards increased security than most vendors are able to. We can make changes the vendors would not make. Also, since OpenBSD is exported with cryptography, we are able to take cryptographic approaches towards fixing security problems.
> ASLR: OpenBSD 3.4 [Nov 2003] was the first widely used operating system to provide it by default.
> W^X: First used for sparc, sparc64, alpha, and hppa in OpenBSD 3.3. Strictly enforced by default since OpenBSD 6.0: a program can only violate it if the executable is marked with PT_OPENBSD_WXNEEDED and it is located on a filesystem mounted with the wxallowed mount(8) option.
> Kernel relinking at boot: the .o files of the kernel are relinked in random order from a link-kit, before every reboot. This provides substantial interior randomization in the kernel's text and data segments for layout and relative branches/calls. Basically a unique address space for each kernel boot, similar to the userland fork+exec model described above but for the kernel. Theo de Raadt, June 2017.
And there are some good reasons for not self-hosting: price/comfort, built-in tools, decent security without having to do your own, etc.