This is gonna catch some folks out 😅

[theorangetheme@en.osm.town]

@GossiTheDog This is a great reminder for me to finally write that TOTP manager for my Cardputer.

[alexhelvetica@toot.cat]

@GossiTheDog I used a rooted device, purely to copy my totp keys out of Microsoft Authenticator, because there's no native way of exporting them to migrate to a different platform.

I suggest everyone else does too. It's stored in an sqlite database as plain text, so it's trivial to extract them once you have access

[dascandy@infosec.exchange]

@GossiTheDog This is still just the authenticator TOTP protocol documented in an RFC?

[djgummikuh@mastodon.social]

@GossiTheDog this is completely idiotic. Let me guess, they also eventually will start ratting out Android devices which no longer receive security updates and wipe them as well? Fuck Microslop

[natkr@hachyderm.io]

@dascandy @GossiTheDog They have some custom push thingy too.

[gvs@rebelbase.site]

@GossiTheDog The irony. It means authenticator will not work on secure smartphones with @GrapheneOS even with the bootloader locked! But it will run fine on commercial phones that have countless holes and are broken into with cellebrite in a matter of hours (yes, when locked)

[schrotthaufen@mastodon.social]

@GossiTheDog This is going to do wonders for work/life balance

[khoos@infosec.exchange]

@GossiTheDog waiting for the first false positive...

[bernardsheppard@mastodon.au]

@DJGummikuh

I have worked for organisations that do just that - their mobile device management platform does a remote wipe of the work profile if you do not keep the system up to date: if you fall more than two versions behind you get a week to upgrade or no work email / teams / access for you.

Bliss.

@GossiTheDog

[djgummikuh@mastodon.social]

@BernardSheppard @GossiTheDog they can do whatever the fuck they want with devices that THEY issued. But they can go fuck themselves if they expect to gain access to my private device for shenanigans like that

[bernardsheppard@mastodon.au]

@DJGummikuh this was on byod devices - but, yeah, I hear you.

This was a major multi-national with, by and large, compliant staff.

You could either be given a shitty work supplied locked down device that was several generations out of date, and carry two phones (which personally shits me) or accept that, if you wanted to byod, which you could self-enrol, you had to keep it reasonably up to date.

As I was there for only a few months, and I didn't particularly want or need to have work email on my phone, I opted out.

@GossiTheDog

[cazzphoenix@social.vivaldi.net]

@GossiTheDog I've always felt weird about using my personal device for anything work related. Fortunately I was never forced to use it for email/teams. If this gets implemented, I hope people just start pushing for companies to provide them devices to use.

[jti42@infosec.exchange]

@BernardSheppard @DJGummikuh @GossiTheDog

Why would anyone byod or even mix private/business hardware, especially if there's MDM going on. I never got that.
Also, work hardware is going into poweroff after the agreed upon hours unless very special conditions and pricing apply.

On the other hand: Keeping the MDM'd business hardware up-to-date/updated or lock it otherwise sounds pretty sane.

[tock@corteximplant.com]

@GossiTheDog Compelling reason why my next job in tech under Microslop is paying for a workplace handheld 100% so my rooted phone can stay off of work.

[tock@corteximplant.com]

@KHoos @GossiTheDog Right? Or a regression where MS believes all is well when millions are affected.

[bernardsheppard@mastodon.au]

@jti42

When it was a small IT team, and the head of IT was a peer, and I could discuss, understand the stack, and trust him, a work profile was no big deal.

Otherwise, yeah, nah, you can supply me with a phone. Which I will still turn off.

@DJGummikuh @GossiTheDog

[bobo_pk@chaos.social]

@GossiTheDog FreeOTP+

Works fine for #Mircoslop and all other OTP tokens

[jackryder@infosec.exchange]

@GossiTheDog 🤯

Not quite unbelievable, but wow.

[fuzzyfuzzyfungus@cyberplace.social]

@dascandy @GossiTheDog It's several different things. Standardized TOTP is supported; two similar looking but distinct('microsoft authenticator(push notification)' and 'microsoft authenticator(phone sign-in)' proprietary things are supported and preferred in default AAD configs; and it's also the client for "Face Check"/"Verified ID" cases, if an org is paying up for that.

[fuzzyfuzzyfungus@cyberplace.social]

@DJGummikuh @GossiTheDog If 'play integrity' and similar are anything to go by; ancient and busted will be fine; so long as it's the ancient and busted that your OEM intended. The enemy, after all, is your filthy little hacker fingers; not an industry of pervasively abysmal code quality and more or less open contempt for confidentiality issues.