Topic
Digital Identity and Credentials
Within the Topic facet, Digital Identity and Credentials topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
IETF
The Email Was Signed. The Mail App Put the Button There.
A flight update arrives with a familiar name, a plausible itinerary and a button to change the booking. The signature can establish who signed the message or its embedded data. The mail app still decides whether the button appears, what it does and whether displaying it sends the…
History
Flickr Kept Your Photo Address. Yahoo Took the Key to the Door.
In 2005, Flickr told its photographers they could keep their screen names and public photo addresses. The thing changing was the key: new users would sign in with a Yahoo ID, while old Flickr users could keep their email-and-password login for a while. By 2007 that exception was…
History
SmugMug Bought Flickr. Yahoo Still Held the Login.
The photographs kept their Flickr addresses when the service changed hands in 2018. Members still entered with Yahoo credentials. It took a separate login migration in 2019 to begin handing them a new key. Flickr's own notices show how a public archive, a corporate owner and the…
IETF
RADIUS Sent an Error. The Proxy Owns the Next Attempt.
A login request reaches a RADIUS proxy. The next hop returns an error. The proxy now has a decision to make: find another route or send a fresh error toward the access device. Passing the packet along unchanged would be cheaper, and wrong. A new IETF draft puts that small…
IETF
The Registry Gave the Transfer a URL. The Domain Had Not Moved.
A registrar asks to take over a domain and receives an HTTP `201 Created` response. What was created? Under a new IETF RPP draft, it can be the *transfer process*, not the completed change of sponsor. The process has its own URL, decisions and messages. A customer-facing…
History
Red Hat Bought Two Netscape Security Systems. One Opened First.
Red Hat announced a deal for Netscape's Directory Server and Certificate Management System in September 2004. The purchase closed in December. By June 2005, Directory Server code was open under the GPL and the supported product was offered through an annual subscription, with…
IETF
The Quantum Door Has a Classical Lock in Eight MLS Suites
An IETF draft offers eleven new cipher suites for secure group messaging. Eight use post-quantum key encapsulation but keep traditional signatures; three add ML-DSA signatures. The November revision now spells out what a forged classical signature could do to a later group epoch…
IETF
The File Was Encrypted. The Download Kept a Guest List.
In a cross-provider chat, an encrypted attachment travels separately from its message. Somebody must fetch it. A new MIMI draft offers three routes, and each gives a different operator a view of the request. The receiving provider can lose sight of the asset host under Oblivious…
IETF
The CNAME Moved. The Old Provider Still Had a Key.
A website owner changes its DNS alias to a new provider. New visitors follow the new route. A proposed HTTP/2 and HTTP/3 feature complicates the goodbye: the former provider can still offer that site's certificate on a connection opened for another site it serves. The server's…
History
Persona Left Sites the Email Address. Then Its Verifier Went Dark.
Mozilla Persona promised websites a login without collecting another password. It deliberately gave them the user's email address, a useful account key. When Mozilla retired its hosted service in 2016, that key remained on the website. The machinery that proved the visitor owned…
Global Cloud Services Trends
Twilio’s verification failed. The SMS meter kept counting.
A login flow can finish with no approved code and still leave a communications bill. Twilio charges its standard Verify platform fee when a code is successfully approved, while SMS attempts have their own meter. The distinction sits exactly where a product team usually calls the…
Europe and Middle East National Telecom Trends
Sweden Can Open the Evidence Inbox Before Anyone Takes the Shift.
Europe's evidence orders now have a digital route to Swedish service providers. PTS says a receiving point can start getting requests once its access administrator is registered, while that administrator still has to appoint the people who will work the queue. An eight-hour…
IETF
The EST Server Gets the Request. This Draft Denies It the Decision.
A new remote-attestation proposal lets an enrollment server move credential requests, evidence and sealed replies. The issuer or vault keeps the power to decide. That line matters most when a convenient middlebox starts to look like a trusted authority.
IETF
The Agent's Door Can Move Without the App Moving
An IETF proposal gives a small file at an application's origin the power to advertise which operations agents may perform. Its own security section names the uncomfortable consequence: whoever can replace that file can move the agent's door without shipping new application code.
IETF
The Suspended Agent Is in the Chain. The Gate Cannot Use It to Say No.
A new agent-evidence draft gives the receiving service a history of who handled a request. Its November revision draws a hard line: that history can expose a suspended upstream actor after the fact, but the gate checks the current actor when deciding whether to let the request…
History
The Server Set the Cookie. Then It Refused the Request Carrying It.
A website can fill a browser with small pieces of state and receive them back as one oversized request. HTTP acquired a name for the collision in 2012: 431 Request Header Fields Too Large. The code can identify the jam. It cannot decide which memory to throw away, and the machine…
IETF
The Log Can Be Honest. Its Owner Can Still Replace Your Verifier.
Key Transparency promises to catch a messaging service that shows different public keys to different users. A new IETF draft section puts the service's software update channel under the lamp: the operator often supplies both the log and the app meant to check it.
History
DoubleClick Put Your Refusal in a Cookie. Blocking Cookies Could Erase It.
DoubleClick offered an opt-out cookie to remember that a browser did not want its tracking. A browser setting meant to reject cookies could remove that very marker. In January 2001, the Federal Trade Commission made the company promise to explain the trap: if a user later…
IETF
The Agent Had a Mandate. Its Identity Expired at the Gate.
A cross-domain software agent can carry a valid delegation and still lose the right to act in the time between checking its papers and issuing an access token. A 1 November Internet-Draft revision puts the agent instance's own identity expiry on the final authorization clock.
IETF
A Trusted Root Does Not Give a Bad Certificate a Second Turn
A TLS draft now draws a line through its own recovery mechanism: a certificate rejected for expiry, revocation or the wrong name cannot borrow the reputation of its root to claim a retry with that same trust-anchor ID.