Social 📸 Photography

Alvin Ashcraft 🐿️MCP Gets OAuth: Understanding the New Authorization Specification | MCP Dev Days.<a href="https://www.youtube.com/watch?v=EXxIeOfJsqA" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=EXxIeOfJsqA</a> <a href="https://hachyderm.io/tags/mcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#mcp</a> <a href="https://hachyderm.io/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://hachyderm.io/tags/oauth" class="mention hashtag" rel="nofollow noopener" target="_blank">#oauth</a> <a href="https://hachyderm.io/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://hachyderm.io/tags/modelcontextprotocol" class="mention hashtag" rel="nofollow noopener" target="_blank">#modelcontextprotocol</a> <a href="https://hachyderm.io/tags/aiagents" class="mention hashtag" rel="nofollow noopener" target="_blank">#aiagents</a>

Alvin Ashcraft 🐿️OAuth 2.0 Access Tokens and the Principle of Least Privilege | by Andrea Chiarelli.<a href="https://auth0.com/blog/oauth2-access-tokens-and-principle-of-least-privilege/" rel="nofollow noopener" translate="no" target="_blank">https://auth0.com/blog/oauth2-access-tokens-and-principle-of-least-privilege/</a> <a href="https://hachyderm.io/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://hachyderm.io/tags/oauth" class="mention hashtag" rel="nofollow noopener" target="_blank">#oauth</a> <a href="https://hachyderm.io/tags/auth0" class="mention hashtag" rel="nofollow noopener" target="_blank">#auth0</a>

Serge from BabkaAnother approach would be if Alice could generate multiple Passkeys and hand them out to individuals she trusts, and then retaining the ability to revoke them. Sadly many sites don't yet support Passkeys, and this model still lets someone like Mal revoke Alice's access, so that's not great.Bitwarden has a feature whereby Alice can share a password with Eve but not let her see it or export it. This could work pretty well, except that if the site requires 2FA from a SMS text message (vs TOTP or a token) or if Eve has the knowhow to intercept the password.I still think that what we ultimately want is attenuated scopes because then we can track all actions by the delegated party.I do wonder if this need is niche or if the current solution of "good faith password sharing" works well enough often enough that it's not risen to the level of concern for developers.2/2<a href="https://babka.social/tags/Authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authentication</a> <a href="https://babka.social/tags/Authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authorization</a> <a href="https://babka.social/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://babka.social/tags/Passwords" class="mention hashtag" rel="nofollow noopener" target="_blank">#Passwords</a> <a href="https://babka.social/tags/Passwordless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Passwordless</a> <a href="https://babka.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a>

Serge from BabkaI've been thinking about delegated authority on websites lately.It would be convenient if I could delegate certain functions to people, for example allowing someone like my accountant to have access to some of my financial records.Some organizations make this easy, allowing me to have multiple accounts.Other services don't offer this, nor do they offer any kind of OAuth type of delegated authorization or capabilities model.I've been thinking about ways around this.One very wacky way would be if Alice could have a a "special browser" that would tie into some service she runs. Bob would log in with his credentials and then behind the scenes the application logs in as Alice.This would be very complicated to implement though.1/<a href="https://babka.social/tags/Authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authentication</a> <a href="https://babka.social/tags/Authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authorization</a> <a href="https://babka.social/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://babka.social/tags/Passwords" class="mention hashtag" rel="nofollow noopener" target="_blank">#Passwords</a> <a href="https://babka.social/tags/Passwordless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Passwordless</a> <a href="https://babka.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a>

Alvin Ashcraft 🐿️Please Don't Write Your Own MCP Authorization Code | by Den Delimarsky.<a href="https://den.dev/blog/mcp-prm-auth/" rel="nofollow noopener" translate="no" target="_blank">https://den.dev/blog/mcp-prm-auth/</a> <a href="https://hachyderm.io/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://hachyderm.io/tags/mcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#mcp</a> <a href="https://hachyderm.io/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://hachyderm.io/tags/modelcontextprotocol" class="mention hashtag" rel="nofollow noopener" target="_blank">#modelcontextprotocol</a> <a href="https://hachyderm.io/tags/aiagents" class="mention hashtag" rel="nofollow noopener" target="_blank">#aiagents</a>

Alvin Ashcraft 🐿️An Introduction to MCP and Authorization | Auth0.<a href="https://auth0.com/blog/an-introduction-to-mcp-and-authorization/" rel="nofollow noopener" translate="no" target="_blank">https://auth0.com/blog/an-introduction-to-mcp-and-authorization/</a> <a href="https://hachyderm.io/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://hachyderm.io/tags/mcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#mcp</a> <a href="https://hachyderm.io/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://hachyderm.io/tags/aimodels" class="mention hashtag" rel="nofollow noopener" target="_blank">#aimodels</a>

Kevin Karhan :verified:<a href="https://cyberplace.social/@GossiTheDog" class="u-url mention" rel="nofollow noopener" target="_blank">@GossiTheDog</a> the sheer fact that <a href="https://infosec.space/tags/MSPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSPs</a> & <a href="https://infosec.space/tags/CSPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSPs</a> can access clients' setups without proper <a href="https://infosec.space/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> [including <a href="https://infosec.space/tags/KYC" class="mention hashtag" rel="nofollow noopener" target="_blank">#KYC</a> / <a href="https://infosec.space/tags/KYB" class="mention hashtag" rel="nofollow noopener" target="_blank">#KYB</a>, <a href="https://infosec.space/tags/AuthCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#AuthCode</a>|s and proper authorization via contract] is already sickening.<ul><li><a href="https://cyberplace.social/@GossiTheDog/114104955818018205" rel="nofollow noopener" target="_blank">This</a> literally begs to be abused via <a href="https://infosec.space/tags/SocialEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#SocialEngineering</a> / <a href="https://infosec.space/tags/SocialHacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#SocialHacking</a> of <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> personnel or just blatant "<a href="https://infosec.space/tags/PrivilegueEscalation" class="mention hashtag" rel="nofollow noopener" target="_blank">#PrivilegueEscalation</a>" through falsefully claiming to be a <a href="https://infosec.space/tags/MSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSP</a> / <a href="https://infosec.space/tags/CSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSP</a> contracted by the targeted company.</li></ul>Such fundamental <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#ITsec</a> fuckups are reasons alone not to use <a href="https://infosec.space/tags/Azure" class="mention hashtag" rel="nofollow noopener" target="_blank">#Azure</a> or any <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> products & services at all...<ul><li>I mean, it doesn't require <a href="https://infosec.space/tags/Mitnick" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mitnick</a>-level skills to pull this off, since it doesn't necessitate <a href="https://infosec.space/tags/Lapsus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lapsus</a>-Style <a href="https://infosec.space/tags/SIMswap" class="mention hashtag" rel="nofollow noopener" target="_blank">#SIMswap</a> or other means to gain access...</li></ul>

C.<a href="https://fosstodon.org/@kentoseth" class="u-url mention" rel="nofollow noopener" target="_blank">@kentoseth</a> I think the main reason that API frameworks commonly don't have built-in authentication and authorization controls is that there are too many different ways to do that, for many different use cases, each with their own benefits and drawbacks.A highly-opinionated framework could include support for one type and declare it to be The Supported Auth Method. If none do that, perhaps there's a reason... but of course, you could always create such an opinionated package, if you thought it important enough.There are almost always add-on packages available for a given framework implementing different approaches to this, giving you almost-zero-code integration with the auth type of your choice. Have you looked around for these sorts of add-on solutions?<a href="https://mindly.social/tags/FastAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FastAPI</a> <a href="https://mindly.social/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a> <a href="https://mindly.social/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mindly.social/tags/opinionated" class="mention hashtag" rel="nofollow noopener" target="_blank">#opinionated</a> <a href="https://mindly.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a> <a href="https://mindly.social/tags/framework" class="mention hashtag" rel="nofollow noopener" target="_blank">#framework</a>

Alvin Ashcraft 🐿️RAG and Access Control: Where Do You Start?<a href="https://auth0.com/blog/rag-and-access-control-where-do-you-start/" rel="nofollow noopener" translate="no" target="_blank">https://auth0.com/blog/rag-and-access-control-where-do-you-start/</a> <a href="https://hachyderm.io/tags/auth0" class="mention hashtag" rel="nofollow noopener" target="_blank">#auth0</a> <a href="https://hachyderm.io/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://hachyderm.io/tags/rag" class="mention hashtag" rel="nofollow noopener" target="_blank">#rag</a> <a href="https://hachyderm.io/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://hachyderm.io/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a>

Erik van Straten🌘DV-CERT MIS-ISSUANCES & OCSP ENDING🌒 🧵#1/3On Jul 23, 2024, Josh Aas of Let's Encrypt wrote, while his nose was growing rapidly:<<< Intent to End OCSP Service [...] We plan to end support for OCSP primarily because it represents a considerable risk to privacy on the Internet. [...] CRLs do not have this issue. >>> <a href="https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html" rel="nofollow noopener" translate="no" target="_blank">https://letsencrypt.org/2024/07/23/replacing-ocsp-with-crls.html</a>🚨 On THAT SAME DAY, Jul 23, 2024, LE (Let's Encrypt) issued at least 34 certs (certificates) for [*.]dydx.exchange to cybercriminals, of which LE revoked 27 mis-issued certs approximately 6.5 hours later.Note that falsified DNS records may instruct DNS caching servers to retain entries for a long time; therefore speedy revocation helps reducing the number of victims.Apart from this mis-issuance *blunder*, CRL's have HUGE issues that Josh does not mention: they are SSSLLLOOOWWW and files are potentially huge - while OCSP is instantaneous and uses little bandwith.🌘NO OCSP INCREASES INTERNET RISKS🌒 If LE quits OCSP support, the average risk of using the internet will *increase*.🌘LIES🌒 Furthermore, the privacy argument is mostly moot, as nearly every website makes people's browsers connect to domains owned by Google (and even let's those browsers execute Javascript from third party servers, allowing nearly unlimited espionage). In addition, IP-addresses are sent in the plain anyway (📎).(📎 When using a VPN, source and destination IP-addresses *within the tunnel* are not visible for anyone with access to the *outside* of the tunnel - but they are sent in the plain between the end of the tunnel and the actual server.)Worse, the remote endpoint of your E2EE https connection increasingly often is *not* the actual server (that website was moved to sombody else's server in the cloud anyway), but a CDN proxy server which has the ability to monitor everything you do (unencrypting your data: three letter agencies love it, FISA section 702 grants them unlimmited access - without anyone informing you).🤷 LE may try to blame others for their mis-issuance blunder, but *THEY* chose to use old, notoriously untrustworthy, internet protocols (BGP and DNS, including database records - that DNSSEC will never protect) as the basis for authentication. By making that choice, LE and other DV cert suppliers were simply ASKING for trouble.🔓 In fact, the promise that Let's Encrypt would make the internet safer was misleading from the start: domain names are mostly meaningless to users, 100% fault intolerant, unpredictable and easily forgotten. If your browser is communicating with a malicious server, encryption is pointless.Josh, stop lying to us; your motives are purely economical.🌘CORRUPT: BIG TECH FACILITATES CRIME🌒 DV-certs were heavily promoted by Google (not for phun but for profit) after their researchers "proved" that it was possible to show misleasing identification information in the browser's address bar after certificate mis-issuance (the "Stripe, Inc" incident, <a href="https://arstechnica.com/information-technology/2017/12/nope-this-isnt-the-https-validated-stripe-website-you-think-it-is/" rel="nofollow noopener" translate="no" target="_blank">https://arstechnica.com/information-technology/2017/12/nope-this-isnt-the-https-validated-stripe-website-you-think-it-is/</a>).This message was repeated by many specialists (e.g. <a href="https://www.troyhunt.com/paypals-beautiful-demonstration-of-extended-validation-fud/" rel="nofollow noopener" translate="no" target="_blank">https://www.troyhunt.com/paypals-beautiful-demonstration-of-extended-validation-fud/</a>) with stupid arguments: certificates do NOT directly warrant reliable websites.OV and EV certificates, and QWAC's, more or less reliably, warrant *WHO OWNS* a domain name. That means that users know *who* they're doing business with, can depend on their reputation and can sue them if they violate laws."Of course" Google recently lost trust in Entrust for mis-issuing certificates (<a href="https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html" rel="nofollow noopener" translate="no" target="_blank">https://security.googleblog.com/2024/06/sustaining-digital-certificate-security.html</a>).Meanwhile the internet has become a corrupt and criminal mess; its users get to see misleading identification info in their browser's address bar WAY MORE OFTEN, e.g. https:⁄⁄us–usps–ny.com (for loads of examples see <a href="https://www.virustotal.com/gui/ip-address/188.114.96.0/relations" rel="nofollow noopener" translate="no" target="_blank">https://www.virustotal.com/gui/ip-address/188.114.96.0/relations</a>; tap ••• a couple of times).Supporting DN's like "ing–movil.com" and "m–santander.de" *is* facilitating cybercrime, by repeatedly mis-issuing certs for them (see <a href="https://crt.sh/?q=ing-movil.com" rel="nofollow noopener" translate="no" target="_blank">https://crt.sh/?q=ing-movil.com</a> and <a href="https://crt.sh/?q=m-santander.de" rel="nofollow noopener" translate="no" target="_blank">https://crt.sh/?q=m-santander.de</a>) and by letting them hide behind a CDN (see <a href="https://www.virustotal.com/gui/domain/ing-movil.com/details" rel="nofollow noopener" translate="no" target="_blank">https://www.virustotal.com/gui/domain/ing-movil.com/details</a> and <a href="https://www.virustotal.com/gui/domain/m-santander.de/details" rel="nofollow noopener" translate="no" target="_blank">https://www.virustotal.com/gui/domain/m-santander.de/details</a>).In addition, *thousands* of DV-certs have been mis-issued - without *their* issuers getting distrusted by Google, Microsoft, Apple and Mozilla.People have their bank accounts drained and companies get slammed with ransomware because of this.But no Big Tech company (including the likes of Cloudflare) takes ANY responsibility; they make Big Money by facilitating cybercrime. Not by issuing "free" DV-certs, but by selling domain names, server space and CDN functionality, and by letting browsers no longer distinguish between useful and useless certs. They've deliberately made the internet insecure *FOR PROFIT*.🌘CERT MIS-ISSUANCE ROOT CAUSE🌒 The mis-issuance of LE certs was caused by the unauthorized modification of customer DNS records managed by SquareSpace; this incident was further described in <a href="https://www.bleepingcomputer.com/news/security/defi-exchange-dydx-v3-website-hacked-in-dns-hijack-attack/" rel="nofollow noopener" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/defi-exchange-dydx-v3-website-hacked-in-dns-hijack-attack/</a>.Note that a similar attack, also affecting SquareSpace customers, occurred on July 11, 2024 (see <a href="https://www.bleepingcomputer.com/news/security/dns-hijacks-target-crypto-platforms-registered-with-squarespace/" rel="nofollow noopener" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/dns-hijacks-target-crypto-platforms-registered-with-squarespace/</a>). Even if it *looks like* that no certs were mis-issued during the July 11 incident, because (AFAIK) none of them have been revoked, this does not warrant that none of them were mis-issued; such certs can still be abused by attackers, albeit on a smaller scale.🌘MORE INFO🌒 Please find additional information in two followups of this toot:🧵#2/3 Extensive details regarding Mis-issued dydx.exchange certs on 2024-07-23;🧵#3/3 Links to descriptions of multiple other DV-cert mis-issuance issues.🌘DISCLAIMER🌒 I am not (and have never been) associated with any certificate supplier. My goal is to obtain a safer internet, in particular for users who are not forensic experts. It is *way* too hard for ordinary internet users to destinguish between 'fake' and 'authentic' on the internet. Something that, IMO, can an must significantly improve ASAP.Edited 08:16 UTC to add people: <a href="https://infosec.exchange/@troyhunt" class="u-url mention" rel="nofollow noopener" target="_blank">@troyhunt</a> <a href="https://infosec.exchange/@dangoodin" class="u-url mention" rel="nofollow noopener" target="_blank">@dangoodin</a> <a href="https://infosec.exchange/@BleepingComputer" class="u-url mention" rel="nofollow noopener" target="_blank">@BleepingComputer</a> <a href="https://infosec.exchange/@agl" class="u-url mention" rel="nofollow noopener" target="_blank">@agl</a> <a href="https://infosec.exchange/tags/DV" class="mention hashtag" rel="nofollow noopener" target="_blank">#DV</a> <a href="https://infosec.exchange/tags/LE" class="mention hashtag" rel="nofollow noopener" target="_blank">#LE</a> <a href="https://infosec.exchange/tags/LetsEncrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#LetsEncrypt</a> <a href="https://infosec.exchange/tags/Certificates" class="mention hashtag" rel="nofollow noopener" target="_blank">#Certificates</a> <a href="https://infosec.exchange/tags/Certs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Certs</a> <a href="https://infosec.exchange/tags/Misissuance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Misissuance</a> <a href="https://infosec.exchange/tags/Mis_issuance" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mis_issuance</a> <a href="https://infosec.exchange/tags/Revocation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Revocation</a> <a href="https://infosec.exchange/tags/Revoked" class="mention hashtag" rel="nofollow noopener" target="_blank">#Revoked</a> <a href="https://infosec.exchange/tags/Weaknessess" class="mention hashtag" rel="nofollow noopener" target="_blank">#Weaknessess</a> <a href="https://infosec.exchange/tags/WeakCertificates" class="mention hashtag" rel="nofollow noopener" target="_blank">#WeakCertificates</a> <a href="https://infosec.exchange/tags/WeakAuthentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#WeakAuthentication</a> <a href="https://infosec.exchange/tags/Authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authentication</a> <a href="https://infosec.exchange/tags/Impersonation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Impersonation</a> <a href="https://infosec.exchange/tags/Identification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Identification</a> <a href="https://infosec.exchange/tags/Infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#Infosec</a> <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> <a href="https://infosec.exchange/tags/DNSHijacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNSHijacks</a> <a href="https://infosec.exchange/tags/SquareSpace" class="mention hashtag" rel="nofollow noopener" target="_blank">#SquareSpace</a> <a href="https://infosec.exchange/tags/Authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#Authorization</a> <a href="https://infosec.exchange/tags/UnauthorizedChanges" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnauthorizedChanges</a> <a href="https://infosec.exchange/tags/UnauthorizedModifications" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnauthorizedModifications</a> <a href="https://infosec.exchange/tags/DeFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeFi</a> <a href="https://infosec.exchange/tags/dydx_exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#dydx_exchange</a> <a href="https://infosec.exchange/tags/CryptoCoins" class="mention hashtag" rel="nofollow noopener" target="_blank">#CryptoCoins</a>

Anders EknertThis was a nice surprise! Me and <a href="https://hachyderm.io/@parcifal" class="u-url mention" rel="nofollow noopener" target="_blank">@parcifal</a> will be talking <a href="https://hachyderm.io/tags/OPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#OPA</a> for <a href="https://hachyderm.io/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> in <a href="https://hachyderm.io/tags/Backstage" class="mention hashtag" rel="nofollow noopener" target="_blank">#Backstage</a> at <a href="https://hachyderm.io/tags/KubeCon" class="mention hashtag" rel="nofollow noopener" target="_blank">#KubeCon</a> 🇫🇷 Well, the co-located backstage event anyway, but who’s counting. <a href="https://colocatedeventseu2024.sched.com/event/1YFhV/can-it-be-done-building-fine-grained-access-control-for-backstage-with-opa-peter-macdonald-vodafoneziggo-anders-eknert-styra" rel="nofollow noopener" translate="no" target="_blank">https://colocatedeventseu2024.sched.com/event/1YFhV/can-it-be-done-building-fine-grained-access-control-for-backstage-with-opa-peter-macdonald-vodafoneziggo-anders-eknert-styra</a><a href="https://hachyderm.io/tags/CloudNative" class="mention hashtag" rel="nofollow noopener" target="_blank">#CloudNative</a> <a href="https://hachyderm.io/tags/CNCF" class="mention hashtag" rel="nofollow noopener" target="_blank">#CNCF</a> <a href="https://hachyderm.io/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a>

Art SmartRemember when <a href="https://mas.to/tags/RonaldReagan" class="mention hashtag" rel="nofollow noopener" target="_blank">#RonaldReagan</a> famously stood up to the <a href="https://mas.to/tags/SovietUnion" class="mention hashtag" rel="nofollow noopener" target="_blank">#SovietUnion</a>? "Mr. Gorbachev, tear down this <a href="https://mas.to/tags/wall" class="mention hashtag" rel="nofollow noopener" target="_blank">#wall</a>."It's amazing how far the <a href="https://mas.to/tags/GOP" class="mention hashtag" rel="nofollow noopener" target="_blank">#GOP</a> has devolved since then. Instead of tearing down walls, it demands they be built. Instead of admonishing <a href="https://mas.to/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mas.to/tags/dictators" class="mention hashtag" rel="nofollow noopener" target="_blank">#dictators</a>, it admires them. <a href="https://mas.to/tags/Trump" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trump</a> repeatedly promises to be one himself (but just for one day, as only the most gullible could ever foolishly believe).That's not an earthquake. It's <a href="https://mas.to/tags/Reagan" class="mention hashtag" rel="nofollow noopener" target="_blank">#Reagan</a> spinning in his grave.<a href="https://www.newyorker.com/news/letter-from-bidens-washington/a-congressional-christmas-gift-to-putin" rel="nofollow noopener" translate="no" target="_blank">https://www.newyorker.com/news/letter-from-bidens-washington/a-congressional-christmas-gift-to-putin</a>

Joey de Villa 🪗This week, I’ll be in San Francisco’s Moscone West, helping run the Developer Hub booth at Okta’s annual conference, Oktane, where I’ll show how you can secure your websites and applications with Auth0 by Okta...and playing some accordion too!<a href="https://mastodon.cloud/tags/Okta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Okta</a> <a href="https://mastodon.cloud/tags/Oktane" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oktane</a> <a href="https://mastodon.cloud/tags/Auth0" class="mention hashtag" rel="nofollow noopener" target="_blank">#Auth0</a> <a href="https://mastodon.cloud/tags/conference" class="mention hashtag" rel="nofollow noopener" target="_blank">#conference</a> <a href="https://mastodon.cloud/tags/conferences" class="mention hashtag" rel="nofollow noopener" target="_blank">#conferences</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a> <a href="https://mastodon.cloud/tags/identity" class="mention hashtag" rel="nofollow noopener" target="_blank">#identity</a> <a href="https://mastodon.cloud/tags/passkeys" class="mention hashtag" rel="nofollow noopener" target="_blank">#passkeys</a> <a href="https://mastodon.cloud/tags/passwordless" class="mention hashtag" rel="nofollow noopener" target="_blank">#passwordless</a> <a href="https://mastodon.cloud/tags/OAuth" class="mention hashtag" rel="nofollow noopener" target="_blank">#OAuth</a> <a href="https://mastodon.cloud/tags/OAuth2" class="mention hashtag" rel="nofollow noopener" target="_blank">#OAuth2</a> <a href="https://mastodon.cloud/tags/OIDC" class="mention hashtag" rel="nofollow noopener" target="_blank">#OIDC</a> <a href="https://mastodon.cloud/tags/OpenID" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenID</a> <a href="https://mastodon.cloud/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a> <a href="https://mastodon.cloud/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mastodon.cloud/tags/SanFrancisco" class="mention hashtag" rel="nofollow noopener" target="_blank">#SanFrancisco</a> <a href="https://mastodon.cloud/tags/SFO" class="mention hashtag" rel="nofollow noopener" target="_blank">#SFO</a><a href="https://www.globalnerdy.com/2023/09/14/ill-be-at-the-oktane-conference-in-san-francisco-oct-3-5/" rel="nofollow noopener" target="_blank">https://www.globalnerdy.com/2023/09/14/ill-be-at-the-oktane-conference-in-san-francisco-oct-3-5/</a>

Susan Larson ♀️🏳️‍🌈🏳️‍⚧️🌈‘What We Do in the <a href="https://mastodon.online/tags/Shadows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Shadows</a>’ <a href="https://mastodon.online/tags/Stars" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stars</a> Take Us <a href="https://mastodon.online/tags/Behindthescenes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Behindthescenes</a> in <a href="https://mastodon.online/tags/Season5" class="mention hashtag" rel="nofollow noopener" target="_blank">#Season5</a>’s <a href="https://mastodon.online/tags/Pride" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pride</a> <a href="https://mastodon.online/tags/episode" class="mention hashtag" rel="nofollow noopener" target="_blank">#episode</a> This <a href="https://mastodon.online/tags/interview" class="mention hashtag" rel="nofollow noopener" target="_blank">#interview</a> was conducted <a href="https://mastodon.online/tags/prior" class="mention hashtag" rel="nofollow noopener" target="_blank">#prior</a> to the <a href="https://mastodon.online/tags/SAG" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAG</a>-<a href="https://mastodon.online/tags/AFTRA" class="mention hashtag" rel="nofollow noopener" target="_blank">#AFTRA</a> <a href="https://mastodon.online/tags/strike" class="mention hashtag" rel="nofollow noopener" target="_blank">#strike</a> <a href="https://mastodon.online/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mastodon.online/tags/Women" class="mention hashtag" rel="nofollow noopener" target="_blank">#Women</a> <a href="https://mastodon.online/tags/Transgender" class="mention hashtag" rel="nofollow noopener" target="_blank">#Transgender</a> <a href="https://mastodon.online/tags/LGBTQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#LGBTQ</a> <a href="https://mastodon.online/tags/LGBTQIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#LGBTQIA</a> <a href="https://mastodon.online/tags/Entertainment" class="mention hashtag" rel="nofollow noopener" target="_blank">#Entertainment</a> <a href="https://mastodon.online/tags/TV" class="mention hashtag" rel="nofollow noopener" target="_blank">#TV</a> <a href="https://mastodon.online/tags/Representation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Representation</a> <a href="https://mastodon.online/tags/Culture" class="mention hashtag" rel="nofollow noopener" target="_blank">#Culture</a> <a href="https://www.tvinsider.com/1100096/what-we-do-in-the-shadows-season-5-pride-parade-nadja-colin-body-swap-nandor-space/" rel="nofollow noopener" translate="no" target="_blank">https://www.tvinsider.com/1100096/what-we-do-in-the-shadows-season-5-pride-parade-nadja-colin-body-swap-nandor-space/</a>

Al Jazeera (unofficial)A man detained in North Korea after crossing the military demarcation line separating the two Koreas is a United States soldier who entered the country “will... <a href="https://www.youtube.com/watch?v=I2hyodR4Zms" rel="nofollow noopener" target="_blank">US national likely held by North Korea after crossing border: UN</a>

Fahim FarookFor work, I'm working on a custom macOS installer at the moment … "Why an installer when installing a macOS app is as simple as dragging and dropping into a folder”, you ask? Well, because this is for a macOS login/authorization plugin … At this point, most people will probably go “Huh?” and I don’t blame you, because this is a dark corner of macOS coding that most probably don’t venture into 😛 A macOS login plugin allows you to customise the macOS login flow so that you can add your own layer of authorization/security or carry out some specific tasks that need to happen during the login process. Unofrtunately, none of that is very well documented. In fact, I spent months scouring the Internet and going through documentation to get our implementation of a macOS login plugin working correctly. In fact, somebody at work said that I was one of possibly 10 people in the world who understood this stuff. Honestly, I don’t believe that since I think that if I could figure it out, anybody else could too since the information is all out there 🙂 Whatever the case, our login plugin requires particular authorization rules to be set and what most people seem to do is to use a shell script to do this since that’s fairly widely documented. But in our case, while that’s the option we are using now, I want to actually do this via code because it simplifies a few logistical issues. So here I am, exploring the macOS documentation again to see how you can do what I want to do in Swift and finding that this is not very well documented at all 😛 I do wish that the Apple documentation was excellent throughout instead of being very informative for the areas that everybody is interested in and then getting rather opaque, terse, or downright non-existent for the areas that people don’t venture into often. But I guess that’s how it works out — afterall, why bother spending the time on documenting something that not many people will use? <a class="hashtag" href="https://a.farook.org/tag/coding" rel="nofollow noopener" target="_blank">#Coding</a> <a class="hashtag" href="https://a.farook.org/tag/apple" rel="nofollow noopener" target="_blank">#Apple</a> <a class="hashtag" href="https://a.farook.org/tag/macos" rel="nofollow noopener" target="_blank">#macOS</a> <a class="hashtag" href="https://a.farook.org/tag/authorization" rel="nofollow noopener" target="_blank">#Authorization</a> <a class="hashtag" href="https://a.farook.org/tag/documentation" rel="nofollow noopener" target="_blank">#Documentation</a> <a class="hashtag" href="https://a.farook.org/tag/security" rel="nofollow noopener" target="_blank">#Security</a> <a class="hashtag" href="https://a.farook.org/tag/login" rel="nofollow noopener" target="_blank">#Login</a> <a class="hashtag" href="https://a.farook.org/tag/swift" rel="nofollow noopener" target="_blank">#Swift</a>

Joey de Villa 🪗Follow the JWT (JSON Web Token) Rabbit, collect all 13 pieces, and share your badge! It’s all part of Okta’s Developer Days, taking place today and tomorrow.<a href="https://mastodon.cloud/tags/Auth0" class="mention hashtag" rel="nofollow noopener" target="_blank">#Auth0</a> <a href="https://mastodon.cloud/tags/Okta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Okta</a> <a href="https://mastodon.cloud/tags/Identity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Identity</a> <a href="https://mastodon.cloud/tags/DigitalIdentity" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitalIdentity</a> <a href="https://mastodon.cloud/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mastodon.cloud/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a> <a href="https://mastodon.cloud/tags/online" class="mention hashtag" rel="nofollow noopener" target="_blank">#online</a> <a href="https://mastodon.cloud/tags/conference" class="mention hashtag" rel="nofollow noopener" target="_blank">#conference</a> <a href="https://mastodon.cloud/tags/DevDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevDay</a> <a href="https://mastodon.cloud/tags/DeveloperDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeveloperDay</a> <a href="https://mastodon.cloud/tags/JWT" class="mention hashtag" rel="nofollow noopener" target="_blank">#JWT</a> <a href="https://mastodon.cloud/tags/JSONWebToken" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSONWebToken</a> <a href="https://mastodon.cloud/tags/ScavengerHunt" class="mention hashtag" rel="nofollow noopener" target="_blank">#ScavengerHunt</a> <a href="https://developer.auth0.com/resources/challenges" rel="nofollow noopener" target="_blank">https://developer.auth0.com/resources/challenges</a>

Joey de Villa 🪗It’s not too late to join Okta’s/Auth0 by Okta’s Developer Day, a FREE ONLINE conference taking place today and tomorrow. Today’s about customer identity — that is, login, logout, and permissions. Join us! <a href="https://mastodon.cloud/tags/Auth0" class="mention hashtag" rel="nofollow noopener" target="_blank">#Auth0</a> <a href="https://mastodon.cloud/tags/Okta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Okta</a> <a href="https://mastodon.cloud/tags/Identity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Identity</a> <a href="https://mastodon.cloud/tags/DigitalIdentity" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitalIdentity</a> <a href="https://mastodon.cloud/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mastodon.cloud/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a> <a href="https://mastodon.cloud/tags/online" class="mention hashtag" rel="nofollow noopener" target="_blank">#online</a> <a href="https://mastodon.cloud/tags/conference" class="mention hashtag" rel="nofollow noopener" target="_blank">#conference</a> <a href="https://mastodon.cloud/tags/DevDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevDay</a> <a href="https://mastodon.cloud/tags/DeveloperDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeveloperDay</a><a href="https://developerday.com/" rel="nofollow noopener" target="_blank">https://developerday.com/</a>

Joey de Villa 🪗TOMORROW and WEDNESDAY! A free online conference on digital identity — a.k.a. login, logout, and who’s allowed to do what in your applications — courtesy of Okta and Auth0 by Okta. Register, and I’ll see you there!<a href="https://mastodon.cloud/tags/Auth0" class="mention hashtag" rel="nofollow noopener" target="_blank">#Auth0</a> <a href="https://mastodon.cloud/tags/Okta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Okta</a> <a href="https://mastodon.cloud/tags/Identity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Identity</a> <a href="https://mastodon.cloud/tags/DigitalIdentity" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitalIdentity</a> <a href="https://mastodon.cloud/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mastodon.cloud/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a> <a href="https://mastodon.cloud/tags/online" class="mention hashtag" rel="nofollow noopener" target="_blank">#online</a> <a href="https://mastodon.cloud/tags/conference" class="mention hashtag" rel="nofollow noopener" target="_blank">#conference</a> <a href="https://mastodon.cloud/tags/DevDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevDay</a> <a href="https://mastodon.cloud/tags/DeveloperDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeveloperDay</a><a href="https://developerday.com/" rel="nofollow noopener" target="_blank">https://developerday.com/</a>

Joey de Villa 🪗Okta’s Developer Day is about identity: namely, logging users in and knowing what they’re allowed (and not allowed) to do once logged in. Sign up for this free online conference that happens next week!<a href="https://mastodon.cloud/tags/Auth0" class="mention hashtag" rel="nofollow noopener" target="_blank">#Auth0</a> <a href="https://mastodon.cloud/tags/Okta" class="mention hashtag" rel="nofollow noopener" target="_blank">#Okta</a> <a href="https://mastodon.cloud/tags/identity" class="mention hashtag" rel="nofollow noopener" target="_blank">#identity</a> <a href="https://mastodon.cloud/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a> <a href="https://mastodon.cloud/tags/authorization" class="mention hashtag" rel="nofollow noopener" target="_blank">#authorization</a> <a href="https://mastodon.cloud/tags/login" class="mention hashtag" rel="nofollow noopener" target="_blank">#login</a> <a href="https://mastodon.cloud/tags/online" class="mention hashtag" rel="nofollow noopener" target="_blank">#online</a> <a href="https://mastodon.cloud/tags/conference" class="mention hashtag" rel="nofollow noopener" target="_blank">#conference</a><a href="https://developerday.com/" rel="nofollow noopener" target="_blank">https://developerday.com/</a>

Recent searches

Search options

Administered by:

Server stats:

#authorization