shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

266
active users

#authenticator

1 post1 participant0 posts today
Replied in thread

@kuketzblog +9001%

Insbesondere da viele #Authenticator - #Apps entwender nur #SingleVendor & #SingleProvider - #Müll, #Bloatware, #Govware oder gänzlich unsicher sind.

  • Wir sind im Jahre 2024 und mit #TOTP, #HOTP & #PGP-verschlüsselten Nachrichten gibt's genug sichere & offene Standards für #2FA!

#AppZwang gehört verboten und ich hoffe @digitalcourage diesbezüglich mehr Druck macht, denn #Digitalzwang wird allzuoft als #Waffe gegen #Marginalisierte genutzt!

digitalcourage.de/digitalzwang

digitalcourage.deDigitalzwang | DigitalcourageDas gute digitale Leben setzt voraus, dass wir Digitalisierung nicht mit Überwachung gleichsetzen und immer auch Wahlfreiheit haben, analog zu bleiben.
Replied in thread

@GrapheneOS @thomas @wonka Also I think the issues usually outweigh the benefits - at least when we look at individuals & devices owned by consumers vs. corporate #ITsec where locking down devices is seen as desireable!

  • It should be the sole discretion of the devices' owners whether or not such a feature should be used or accessible and it shpuld be disallowed to coerce people into "consenting" under threat of denied access.

Because for every "#LegitimateInterest" (i.e. #2FA #Authenticator) I can find a dozen reasons this "functionaloty" should be discontinued and considered malware.

In *2019*, Alex Weinert of Microsoft wrote in techcommunity.microsoft.com/t5:

«
    MFA had failed.

    [...]
    All Authenticators Are Vulnerable
    [...]
»

Today, as echoed in bleepingcomputer.com/news/micr, Microsoft still insists that using weak MFA is a good idea.

In azure.microsoft.com/en-us/blog Microsoft writes (on August 15):

«
As recent research [1] by Microsoft shows that multifactor authentication (MFA) can block more than 99.2% of account compromise attacks, making it one of the most effective security measures available, today’s announcement brings us all one step closer toward a more secure future.
»

From that same article, "solutions" with (nearly as weak as SMS) "Microsoft Authenticator" is at the TOP of their list:

«
Organizations have multiple ways to enable their users to utilize MFA through Microsoft Entra:

• Microsoft Authenticator [...]
• FIDO2 security keys [...]
• Certificate-based authentication [...]
• Passkeys [...]
• Finally, and this is the least secure version of MFA, you can also use a SMS or voice approval [...]
»

From [1] (PDF) = query.prod.cms.rt.microsoft.co , no date of the "investigation period" to be seen *anywhere*, and one of the authors being Alex Weinert, more extreme percentages (approved by Microsoft's marketing dept):

«
Our findings reveal that MFA implementation offers outstanding protection, with over 99.99% of MFA-enabled accounts remaining secure during the investigation period. Moreover, MFA reduces the risk of compromise by 99.22% across the entire population and by 98.56% in cases of leaked credentials.
»

Dear reader: please stop buying Microsoft BS that completely ignores PhaaS.

To name a few examples:

🚨 "Experts agree [*] that setting up two-factor authentication (2FA) İs one of the most powerful ways to protect your account from getting hacked. However, hackers like COLDRIVER and COLDWASTREL may try to trick you into entering your second factor; we have seen attackers successfully compromise a victim who had enabled 2FA." - (PDF) accessnow.org/wp-content/uploa

[*] Not me. My tip is here: infosec.exchange/@ErikvanStrat

🚨 EvilGinx2: "Standalone man-in-the-middle attack framework used for phishing login credentials along with session cookies, allowing for the bypass of 2-factor authentication" - github.com/kgretzky/evilginx2 (there are more, like Modlishka, Muraena, CredSniper, EvilProxy (Phaas), NakedPages etc.)

🚨 Not even a fake website needed: bleepingcomputer.com/news/secu

🚨 From mrd0x.com/attacking-with-webvi:
«
Bypass 2FA
WebView2 also provides built-in functionality to extract cookies. This allows an attacker to extract cookies after the user authenticates into the legitimate website. This technique removes the need of having to spin up Evilginx2 or Modlishka but the obvious trade-off is that the user must execute the binary and authenticate.
»
In addition, from bleepingcomputer.com/news/secu:
«
"Yubikeys can't save you because you're authenticating to the REAL website not a phishing website."
mr.d0x
»
AND:
«
However, as mr.d0x admits and Microsoft pointed out in their response to our questions, this attack is a social engineering attack and requires a user to run a malicious executable.
»
Correct, but a local compromise does'nt protect you when you're using FIDO2 hardware keys or passkeys.

🚨 From 2022: microsoft.com/en-us/security/b:
«
A large-scale phishing campaign that used adversary-in-the-middle (AiTM) phishing sites stole passwords, hijacked a user’s sign-in session, and skipped the authentication process even if the user had enabled multifactor authentication (MFA).
»

🚨 "Phishing with Cloudflare Workers: Transparent Phishing and HTML Smuggling" - netskope.com/blog/phishing-wit

🚨 "New EvilProxy Phishing Service Allowing Cybercriminals to Bypass 2-Factor Security" - thehackernews.com/2022/09/new-

🚨 From europol.europa.eu/media-press/:
«
The investigation uncovered at least 40 000 phishing domains linked to LabHost, which had some 10 000 users worldwide.
[...]
LabRat was designed to capture two-factor authentication codes and credentials, allowing the criminals to bypass enhanced security measures.
»

🚨 "Security and Privacy Failures in Popular 2FA Apps" by Gilsenan et al. (USENIX 2023): usenix.org/conference/usenixse
The PDF can also be found here: github.com/blues-lab/totp-app- (Aegis was one of the least problematic apps, and don't use Authy).

This is what is wrong with weak MFA/2FA:

You
 o
/|\  [device + browser]
/ \ |
v
[login.microsoftonline-aitm.com]
|
v
[login.microsoftonline.com]

(no thanks to DV-certificates).

TECHCOMMUNITY.MICROSOFT.COMAll your creds are belong to us!Multi-factor Authentication (MFA) matters. 
#AitM#MitM#EvilProxy

My S-i-L fell for a #scam. Charges reversed, but her Apple ID was hacked in the process. I set up 2-step verification on all her accounts. I just learned that PayPal can ONLY be set up with an #Authenticator app now.
Apparently #PayPal won't let you use your phone number to verify anymore. AND they don't allow people to use printed backup codes!
My friends in info security get why PayPal did this, but trying to set up & walk her through the process took 5 hours over 3 days. UGH!

The whole idea of sending your OTP seeds to a “cloud” ⃰ backup facility really challenges the fundamental principle of OTP.

⃰: “Cloud” -- noun; tech jargon. Someone else's computers doing something for you that you need done but don't want to handle yourself, beyond your control or visibility.

Has anyone enumerated the situations that get you a Microsoft Number Matching MFA prompt that OBSCURES the number but does NOT offer the "I can't see the number" option in the MS Authenticator app?

I am "the guy" that always breaks this shit, but I cannot recreate one edge case reliably so we can document it in our "weird shit that one user will see when numbering matching becomes required" document.