![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.kde.social/pictrs/image/19e6d51f-5131-409e-8990-827d3d29e4d3.png)
Maybe scrcpy is the tool for you then.
Maybe scrcpy is the tool for you then.
There is scrcpy for that and you can launch arbitrary commands from KDE Connect too.
You need a phone, tablet, or other device that’s been rooted.
😦
A bit of both. The Allies started denazification. Then the western allies and Germans who got into power (including Nazis) became less and less strict as they realized they needed some of them to build up structures of society, especially with the cold war beginning. And of course Nazis protecting Nazis.
The allies even gave some groups of Nazis weapons to prepare for a guerilla war in case Stalin invaded West Germany (see Gladio and other stay behind groups).
Not punishing Nazis for their crimes was so common that there is a word created for this specific meaning: A Nazi or collaborator basically getting pardoned or even getting the authorities formally void their offenses/atrocities: Persilschein. The word refers to a popular brand of laundry detergent, similar to the phrase"whitewashing".
Also protects you from Poseidon’s Kiss as far as I have experienced.
Is he selling vegetables? /s
The guy on the left looks like a famous non-US politician.
I’m impressed 🙂
Why is this cursed? Wouldn’t anybody prefer horny AI hallucinations over rogue killer robots? 😉
Yeah, that’s a very useful exception.
Operator overloading is adding complexity, making code subtly harder to read. The most important lesson for code is: It should primarily be written to be easy to read by humans because if code is not trash, it will be read way more often than written.
If it is just the location, then it could be spoofed.
If it is something that requires physical presence, then you need both devices to communicate with each other. If it is not done via QR code (like some online banking do), then both devices need to be connected, e.g. via WiFi or Bluetooth. In this case, if an attacker controls one of the devices (that’s the class of attacks 2FA should prevent you from), the attacker probably controls both devices. So what’s the point then?
I guess if there is WiFi, he won’t even need a mobile data plan, so he could safe lots of money.
How would MS Authenticator make it any better than TOTP?
To break TOTP, the attacker would need to:
a) be able to observe the initial exchange of the TOTP secrets. To do that, the attacker needs access to the victim’s computer (on user level) at that specific time they set up TOTP. TOTP is a TOFU concept and thus not designed to protect against that. However, if the attacker controls the victim’s computer at that time, the victim is screwed anyways even before setting up 2FA.
b) have access to the TOTP app’s secret storage and to the victim’s login credentials (e.g. by phishing). If the attacker can gain that level of access, they would also have access to the Microsoft Authenticator’s secret storage, so there is no benefit of the Microsoft app.
On the other hand, Microsoft Authenticator is a very huge app (>100MB is huge for an authenticator app, Aegis is just 6MB, FreeOTP+ 11MB), i.e. it brings a large attack surface, especially by connecting to the internet.
I don’t think Microsoft Authenticator brings security benefits over a clean and simple TOTP implementation.
If it is just TOTP, you can use any other TOTP app, such as Aegis or FreeOTP+.
And no, Microsoft cannot be trusted on not doing anything bad. The app is full of trackers and has an excessive list of permissions it “requires”.
For comparison, Aegis and FreeOTP+ work without trackers and way less permissions.
Microsoft has a long track record of leaks. Just naming the 2 most prominent:
Are you forced to use their app or are they just very insistently trying to trick you into using it? I.e., have you tried with Bitwarden or any other TOTP capable app?
It might depend on configuration. In the only case of Microsoft enforced 2FA I know of, it is just TOTP. Microsoft’s web interface nudges (tries to trick) you into using the MS Authenticator app, but that app is not needed. You can use any TOTP capable 2FA app, e.g. Aegis or FreeOTP+, both of which are also available through F-Droid and don’t require internet connection.
“Diplomjodler” sounds German so probably different laws apply…
With Gtk, I have seen some issues with rarely used parts of the API, but that should not be relevant to your rather simple use case.
But it avoids buerocratic hassle