Earlier quoted context omitted.
Don't know why you're getting downvoted. I couldn't figure out how to get past it, but it looked like the article is in English.
Yes that was the bizarre part. I recognize it's a .de domain but the URL and content seemed to be in English. I didn't know how to get past the (what is presumably) cookie dialogue though, so I guess I'll never know.
Microsoft lays hands on login data: Beware of the new Outlook
91–100 of 119 posts
Re: Microsoft lays hands on login data: Beware of the new Outlook
#92Earlier quoted context omitted.
I wonder how long this will work? If I was Google, I'd think about banning IMAP logins from the Azure servers that are doing this syncing.
The already call IMAP an inscure, outdated service. So when you enable it, they will disable it for you after so many days whether you want them to or not.
Re: Microsoft lays hands on login data: Beware of the new Outlook
#93Only reason I could think of: some very specialized extensions that are only available for Outlook.
I'm really happy that Thunderbird recently got some updates, I think it's the only good free desktop mail client that is still around. Evolution looks really dated nowadays.
Personally I can recommend eM Client for Windows users as an Outlook replacement (and they have a macOS version too). It's commercial, but there is a free version for private use. It does CardDAV/CalDav quite well, and supports PGP/S/MIME.
Re: Microsoft lays hands on login data: Beware of the new Outlook
#94Oh wow, it posts your cleartext email credentials to an API endpoint called “/ows/beta/ShadowService/getShadowToken”. But it least it calls the password string a “Secret” in the JSON payload so you can REST assured knowing the Shadow Service agents will handle this data appropriately.
Re: Microsoft lays hands on login data: Beware of the new Outlook
#95https://mailbox.org/en/post/warning-new-outlook-sends-passwo...
> The German Federal Commissioner for Data Protection and Freedom of Information, Ulrich Kelber, is also alarmed: On the social media network Mastodon, he described the data collection as "alarming" and announced his intention to pursue the issue at European level through the data protection authorities as early as next Tuesday.
Re: Microsoft lays hands on login data: Beware of the new Outlook
#96Earlier quoted context omitted.
I wonder how long this will work? If I was Google, I'd think about banning IMAP logins from the Azure servers that are doing this syncing.
The already call IMAP an inscure, outdated service. So when you enable it, they will disable it for you after so many days whether you want them to or not.
For most services email is the master key to reset your password. By getting access to someone's email account a lot of other accounts can be breached easily. I try to disable password reset via email wherever possible. But most services don't provide this option.
I think it would be time for IMAP to get a standardized way to log in via OAuth2/OIDC. And maybe an update to the email standard to mark a recovery links or codes as secret, that require 2FA every time to read.
Especially dangerous are servers that still allow using IMAP without TLS, that's just asking for trouble.
Re: Microsoft lays hands on login data: Beware of the new Outlook
#97Re: Microsoft lays hands on login data: Beware of the new Outlook
#98The only way I can create a new email is: 1. Hit reply on an existing email and delete to; subject; and body; or 2. Go to contacts, select a person, and click email to, and then modify the "to" field to insert the correct address.
WTF?
Re: Microsoft lays hands on login data: Beware of the new Outlook
#99The free new Outlook replaces Mail in Windows, and later also the classic Outlook. It sends secret credentials to Microsoft servers.
I wonder how long this will work? If I was Google, I'd think about banning IMAP logins from the Azure servers that are doing this syncing.
Microsoft stores an OAuth2 access token for these accounts, which is still unnecessary compared to the locally synced version of Outlook we're all used to, but the user can revoke it through Google account settings at any time, just like any other OAuth2 access token.