Web services will never store your plain text passwords. I would get nothing out of that and would compromise the security of every one of my users, not only on the Pulse service, but potentially their entire online presents for those that use the same password across services (which is probably plenty, unfortunately). What would I do with it if I could decrypt the billion records stored in Pulse, one-by-one? Nothing. This would be a massive security hole with literally no benefit to the owner of the service. If they did, they could obviously use that to log in to your Pulse account and any other service you use. You are "trusting" every single service that you sign up for to not store your password in plain text. Obviously I could encrypt it before sending it, but then that encrypted string would simply become your password. SSL protects and encrypts that password on its own. It is standard practice to send plain text passwords over SSL. I think I will also reply here about the "plain text" question, as well. No misleading/non-descriptive/clickbait titles, disinformation or illegal content.ĪmAs, Q&As, giveaways, and other community-facing content must be approved by moderators.Īnd as always, be nice and follow reddiquette. No self promotion, URL shorteners, referral/affiliate links/codes, or spam. No low effort submissions, memes, or NSFW content.
Posts must be related to the Google Pixel devices and the #madebygoogle lineup. (In the case of discrepancy, the rules linked above will take precendence.) Subscribe to this calendar to follow the biggest events coming to r/GooglePixel.įor more information on all of the devices in the Made By Google lineup, and other Google-related products, check out these subreddits:Ĭlick on each rule for its full description. DO NOT COMMENT unless you have evidence to share. Also, a reminder to users visiting links to the Issue Tracker: star the issue.
NOTE: You must be signed into your Google account to view bugs on the Google Issue Tracker.
0 kommentar(er)
