280 karma · joined November 7, 2019
Activity: Alice (a supervisor), raises a transaction >X, Bob is a supervisor, Eve is not.
Problem: “Who can approve the transaction?”
(As humans the answer is obviously Bob, but for typical implementation approaches to AuthZ policy, this is challenging to determine. Typically it’s done out of band and then makes a decision when requested by Bob (allow) or Eve (deny))
https://gdpr-info.eu/art-17-gdpr/
Implementing this as a rollback-able delete will not be compliant.
Do better.
Of course you can also plant rice on flat fields (and China does as well), but this does skew the comparative ratios of acres of land use : people fed.
The article even states Microservices are not suitable for startups - the conversation in this thread has been able service oriented architectures which is a much broader topic.
That being said, there's no end-to-end verification of the server, so any DNS-poisoning or proxy-MITM-ing of traffic that presents a certificate trusted by the browser will validly present the Passkey implementation a domain that matches a validly provisioned key, allowing session hijacking or the start of oracle attacks on the private key itself.
Also: phishing the recovery passwords to add a new device to the synched keychain is definitely a thing.
I haven't seen anything in the FIDO alliance or vendor (Apple, Google, MS) documentation to suggest that they're cross-signed public keys - can you point to some that I may have missed?
The reason why I ask is on the face of it, it doesn't make sense to implement in this way: It would mean that each new device would have its own keypair per service and cross signed by at least one other trusted device. Which could be fine, but now each service needs to store n public key pairs (one per device) after validating that the new key has been signed by a known key.
Then, when a new device is added to the Keychain (in apple's case), that device needs to generate m new keypairs for m services, have them cross-signed and then proactively registered for each service.
It does make sense to implement it as the person you're replying to suggests, where a shared private key is shared over an authenticated, end-to-end encrypted process - with the corresponding weakness that if the authentication method for adding new devices to an existing Keychain is compromised, so are all passkeys.
Hence the question.
2) Passwords that can be stored in the meatsack attached to the keyboard aren't as random as we'd like to think them to be, where as a secure pseudo-random function will generate keypairs with unguessable entropy.
Expanding on 2) While salting and non-uniform iteration counts of hashes prevents instant compromise from rainbow tables, they only slow down adversaries generating hashes from password guesses, as the salt and iteration count will typically be leaked from the same table as the password hash.
Its worth noting that while it definitely is infeasible to attempt to crack 100K+ users passwords from a password hash leak, using password spraying and especially password stuffing approaches will inevitably lead to compromise one or more accounts relatively quickly. At the other end of the spectrum, if a known high-value account can be identified, dedicating the distributed cloud resources to cracking a specific password can be a net-profitable undertaking.
No. Pilots weren’t even aware of MCAS’ existence until after the second fatal crash.
That’s a huge problem, compounded by
> Boeing cheaped out and made MCAS depend on a single AoA sensor.
https://en.m.wikipedia.org/wiki/Maneuvering_Characteristics_...
But respond favourably to, in sufficient numbers, that it remains profitable for the shovelling class? You betcha.
You seem very worked up and calling people names is ironically something a puerile teenager in high school would do.
Go outside, get some fresh air and perspective and come back to being a productive member of this community.
That fact does nothing to disprove the existence of autonomous vehicles.
Go outside, friend.
Prices definitely lowered, but the difference being that while there was also supplier upheaval as artisan/bespoke producers were replaced by mass production - the industrialists were enormously and sustainably profitable and could in turn employ those displaced from the failed producers.
Aggregate demand arguably increased with the move of labour from rural agriculture to urban manufacturing.
A deflationary cycle annihilates demand by definition and fixed costs then eat producers alive - leading to wealth destruction, unemployment, debt writeoffs and credit tightening. Which in turn leads to more demand annihilation.
Its not. Keep reading.
https://learn.microsoft.com/en-us/aspnet/core/tutorials/min-...
It’s .NET 101 stuff.
Productive devs want the request/response wrapper objects and routing constructs to handler methods to get work done and can still drop down into fine-grained request/response crafting as and when required.
https://learn.microsoft.com/en-us/dotnet/core/install/linux
Also VS Code, an open source IDE with first class support for .NET languages: