Re: Nothing new, kinda pathetic really
"it isn't that long since I was using the college Vax"
It is, but only when you stop to think about it. Welcome to the club.
40485 publicly visible posts • joined 16 Jun 2014
"Okta claims to have more than 15,000 customers, so if 2.5 per cent have been compromised that could be 375 organisations that now need to determine if all logons to their preferred clouds – and the actions taken by authenticated users – were legitimate and/or innocuous."
But all 15,000 will need to assume they were amongst the 375.
"the reviews on this marketplace may not be entirely frank and fearless."
Published reviews might not but the intended market will be quite capable of forming their own views.
However I wonder if Russian idiom lends itself to comments such as "You will be very fortunate to have this operating in your system."
"I'm talking about OVERALL i.e. for the whole world, not just you."
I only care about me and mine. I have no wish to be pulled down to some intermediate level because your mother uses the same email/password combination for all sites.
In fact, right there, you've indicated one possible area for improvement which needs not particular technological fix nor optimistic trust in providers such as Okta: make it illegal to specify an email address as a login ID. That in itself would make it easier for those who care to use multiple login IDs without juggling multiple email addresses.
Very simply put, you create an account with SomeOrg and agree with SomeOrg that "this magic token" is associated with that account. The token itself doesn't identify you
It's normal practice when you create an account to use an identity to do that. These days banks are very careful about establishing identity to cope with money-laundering legislation (unless, of course, you're handling sufficient funds to make money laundering worthwhile if not the object of the operation in which case the bank will be delighted to give you an account in the name of any off-shre shell company you choose).
Where was I? Ah, yes. Account. Identity. No, the token itself doesn't identify you. But the token is associated with account so we have Token > Account > Identity. That's what I'd call indirect addressing. For some purposes it might be enough or, depending on the purpose, too much.
"That's a lot of usable phones lying around in drawers just as identity backups"
Apart from any other consideration that's also a lot of phones identities lying about to be nicked if you're burgled. Plus when you really need them you'll find that the battery life has decayed to 2 seconds and nobody local stocks that odd battery size any more.
My first rule is to minimise the number of entities which I will trust. Apart from myself, who I usually do trust, that means entities which have earned my trust. So what do I make out of FIDO cites Apple's adoption of "Passkeys,"?
In the article that includes a link to documentation about Passkeys, at least that's what the link indicates. And it's a link that does nothing without javascript being enabled. Javascript, just to read documentation.
A body consisting of a list of the usual suspects offers as an example of what it's about something that requires javascript just to read what it's about? Of course I'm going to trust it. About as far as I can throw it.
Never underestimate the way things can change in the IT world and how fast irrespective of how entrenched things seem to be.
When I started in IT we were the upstarts in a DEC dominated world by using Unix and RDBMS. I think the latter was even looked on as the more radical. We were always going to be taken under the VMS wing in about six months' time.
"Like all businesses with captive markets, they're primarily interested in their balance sheets."
But is that market capture guaranteed? It consists largely of businesses that have their own bottom line to tend to. How much more intrusion into their affairs will it take for those customers to start to review the market? Anyone not firmly wedded to Windowsland knows very well that other desktop environments can be re-skinned to like more or less any version of Windows that takes your fancy. It's quite easy to envisage a PC vendor pre-installing Linux or BSD with a first run menu for a new user which offers a choice of any Windows UI from W2K to present.
In this context the spoiler of "It doesn't run my gamez" won't get far; this is a work machine. The other spoiler, the user with a massive investment in Excel macros, might end up finding themselves the corporate odd man out, just like the user who must have a Mac. There might even be a market in tools to convert those spreadsheets into one-off applications.
"You are obviously a time traveller who has come back from 5 years in the future."
From my PoV, just somebody who can see the way Microsoft would like to take things. The only questions for the likes of yourself seem to be how much of it will you let happen and how quickly and you seem to have answered the second already.
"Yes, it's because of a rather hard engineering problem to do with application A and application B both depending on application C, but each depending on a different version."
Not so much application C as library C.
This can be a problem if B claims* it needs a bleeding edge version of C whilst A & C are rather conservative versions that came with the OS.
The better solution is to have the non-distro version install in /opt together with any libraries its authors feel they might need to make a fuss about. For instance my /opt contains LibreOffice 7.2 (distro version is 7.0), Seamonkey, Signal & Zoom inter alia. It's a much more Unix-like way of doing things.
* It might not. The providers of B should have a slap on the wrist for this.
"The strength and weakness (imao more the latter than the former) of open source software is the freedom to go off and roll your own if you don't like the current version(s)."
Most people don't. When they do it's usually because someone has screwed up really badly. The exemplar of that would be OpenOffice suffering from the influence of Oracle. Even there is was mostly the OpenOffice devs who went off to found LibreOffice. Strength or weakness? Entirely the latter, I think.
Perhaps you could give us an example of your A>B>C>D process which actually turned out to be a in real life.
In the meantime, enjoy your adverts in your file manager - you're not going to be able to fork it.
Being able to fork something isn't only a menas of recovering from screw-ups, it's a disincentive to screw up in the first place.
Where does your setup.exe come from? Which setup.exe is it? Did your setup.exe include a few dlls you may have already got from elsewhere just in case you didn't? If so how do you keep track of the different ones? You're dealing with a multi-step rpocess - first find your setup.exe. Download it. Keep it separate from all your other setup.exes so you know what's what. Then run it. That's not the easy way.
For sheer laziness apt install some-package wins hands down, especially if there are other dependencies which are needed.
"a postal address (where the mail gets delivered) and a visiting address (where the office of the person you want to meet actually is)"
And that's only modern addresses. Historical addresses can have quite different concepts. Maybe you think that shouldn't be a problem. It is when you're dealing with genealogical S/W written by someone who thinks addresses were always like modern addresses in whatever country they live in (usually the USA).
"so yes, you couldn't delete a file if the disk was too full because it needed space to write the new tree nodes"
I've never checked to see if Linux does this but old-style Unix would declare disk full to non-root programs with some margin left for root. I've appreciated that when an overnight job went rogue and filled up a partition with junk messages.
"I don't want to store a huge geographic database on my PC"
I assume your PC isn't providing some sort of service to other customers. What you choose to do on your PC and what a service provider choose to do are two different things. If you were running your state's emergency services you might well think it worth having that state's mapping locally resident or else second source Google Maps with OSM (or vice versa).