#61332 closed enhancement (fixed)
Post via email - Password field default value trips Google Chrome warning
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 6.7 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Administration | Keywords: | has-patch has-unit-tests |
Focuses: | Cc: |
Description
TLDR: The default "Post via email" password is simply "password", which can trigger a scary-looking popup in Google Chrome.
To reproduce the issue:
- In Chrome, go to "chrome://settings/security".
- Toggle on the "Warn you if a password was compromised in a data breach" setting.
- Spin up a WordPress test site.
- In wp-admin, go to Settings > Writing.
- Click "Save Changes". No need to change any actual settings.
- Observe the attached popup from Chrome.
I believe Chrome thinks I have actually chosen the password "password" and warning me about it, which makes sense. The problem is that this triggers even when I've simply left the "Post via email" settings on their defaults, and only changed the default post category or whatever.
I'm not sure if WP core can do anything about this, but it seemed worth mentioning.
Attachments (1)
Change History (7)
This ticket was mentioned in PR #6687 on WordPress/wordpress-develop by @sabernhardt.
10 months ago
#1
- Keywords has-patch has-unit-tests added
#2
follow-up:
↓ 3
@
10 months ago
- Version 6.5.3 deleted
#22942 might deprecate the feature at some point, but I wonder about just leaving the password empty in schema.php
. The value needs to be replaced for proper use anyway.
#3
in reply to:
↑ 2
@
10 months ago
Replying to sabernhardt:
#22942 might deprecate the feature at some point, but I wonder about just leaving the password empty in
schema.php
. The value needs to be replaced for proper use anyway.
I just tested with an empty password, and it doesn't trigger the Chrome warning. I can't think of any reasons why this wouldn't be ok, as you point out, you have to specify actual mail server details for it to work.
#5
@
7 months ago
- Owner set to SergeyBiryukov
- Resolution set to fixed
- Status changed from new to closed
In 58928:
@SergeyBiryukov commented on PR #6687:
7 months ago
#6
Thanks for the PR! Merged in r58928.
Updates
schema.php
and unit testsTrac 61332