Re: Will this be a problem for embedded device certs?
You do what Samsung likely did on June 19 and have all such devices enter a boot loop. Problem fixed.
205 posts • joined 29 Mar 2008
Yes, let's adopt Poettering's shutdown strategy: change the event sequence in udev to suit systemd without giving a thought to anyone else. This had the lovely side effect of breaking shutdown completely if a LUKS partition was in use on SysV init.
(As in - upgrade from Debian Jessie to Stretch and find you can't shut down anymore. Lovely. I've used Debian since the 2.x days, but that was the last straw. Swicthed to Devuan and have not had a reason to look back. And Beowulf runs fine on a Raspberry Pi too.)
... interesting enough to tolerate its infantile syntax is the remoting capability. But then MS had to go out and neuter that when used against their own services because allowing it would crumple their servers*.
Want to set a simple property on all your O365 e-mail accounts? Sorry. Only on the 1st 100 or so. For the rest, you need to transport the entire collection to your side, change the property, then send the whole lot back. What should have taken a few seconds now takes an hour.
* anno 2018.
Growing up, Concorde made 2 ambassador flights to my local airport (Oostende).2nd time i was old enough to go see it on my own, The first thing of note was that it came with an Air France-liveried Renault R4 carrying a spare tire for the tail landing gear.
The crowd control barriers were only arms length from the undercarriage. When time came to depart, the ground crew pushed the barriers back to barely outside the intake line of the engines. I was standing under the left wingtip when the engines started spooling up. (Glorious days :-) Can't image that happening these days...)
Sorry for the late response. I installed 71 (the day before this article) and that is what it says on two splash pages on its first run.
Looks like the change was introduced with 67, but 71 is the first one stating a Sync account is the only way to retain access to your information across versions.
It may be possible to wrangle the Profile Manager to regain access, but for how long? And how many regular users even know that thing exists?
Agent Tick does have a valid point. What is not mentioned in TFA is that with 71 (and beyond), each update will create a new profile. The only way to retain access to saved passwords, autofill, etc. is by handing your data to Mozilla. There is no provision to do a local import from an older FF version.
There are indications printers also reject genuine but out-of-region Epson cartridges. (Going by the eBay/Amazon comments of US based users of non-retail packaged cartridges of Asian origin. Of course, those may be fakes, but the one set I did end up with looked pretty convincing. No idea if they worked or not as I ended up returning them because the seller had misrepresented them as regular retail items.)
CGI made a complete hash of the Vermont health insurance "marketplace" application. The contract was terminated as it became obvious CGI was incapable of coming up with something that didn't fall over as soon as it encountered real world loads. They still walked off with $66M
Not sure I'm following that one. Even a wildcard cert would not cover www.example.com and example.com simultaneously. AFAIK, unless example.com is included as the Subject Alt Name on the www.example.com cert, the browser should complain if example.com responds to www.example.com. So, user goes to example.com -> complaint, user goes to www.example.com -> no complaint, even though the address bar says example.com. As if the SSL situation was not confusing enough already :-/
I would say this tin rattling dovetails nicely with neutering independent extensions. Mozilla can now do things outside developers can no longer readily accomplish.
Did they ever fess up how much they paid for Pocket? I can't help but wondering how much that acquisition is contributing to Mozilla's cash crunch.
For me, having Pocket take over the entire UI and the normal bookmarks menu mangled when 60 ESR replaced 52 was the last straw. For now, I have fallen back on Waterfox, but it has become very obvious how much of a competition killer Mozilla's extension store is.
This decision may embolden Spotify (and likely others) to file suit in the US instead of just the EU over Apple's corresponding 30% vig of any in-app purchase (and the prohibition for the vendors to tack the difference onto the price.) They have deeper pockets than any solo developer or customer and the damage to Apple from losing that subscription income is likely to be more serious than losing x% on the less frequent (maybe even one-time) purchase of applications.
From the article:
"We’ve listed a set of changes to the proposal that we believe are necessary to keep Privacy Badger functioning as it does now and to allow us to implement planned changes in the near future," they wrote in their letter to Google's Chromium team.
There's really no other way for this to work. Implementing an intrusive public facing change like that in Chrome only would essentially create 2 separate browsers. And even if it was for Chrome only, that probably covers 99% of all installations. That doesn't leave a lot of incentive for developers to continue supporting Chromium.
"the browser is stable and the fact you're reading this indicates that sites such as The Register's own content management system run without issue."
Thank you for that revelation! I've always attributed that to Waterfox. My bad...
Now, does all this mean Chromium is now an essential and inextricable part of Windows, or is Edge now uninstallable? Inquiring minds and all that...
FYI, there may be pain on the Debian Jessie -> Devuan Jessie -> Devuan ASCII path.
There are no issues with a clean install but an upgrade may result in mixing parts of consolekit and elogind. It was reported during testing but things are not entirely resolved. My Xfce lost the reboot/shutdown controls and from the CLI, a shutdown hangs at "Will now halt". Been digging into it since the upgrade, but no success yet.
The biggest problem is not so much systemd itself, but the usurpation of udev. On Stretch without systemd, that has already broken LUKS. The inclusion of hardware dependencies in the network interface names wreaks havoc when rolling out network configs with something like Ansible. (Instead of the familiar eth#, udev now produces names like enp3s13 where the numbers reflect the position on the PCI bus.)
Biting the hand that feeds IT © 1998–2020