Changes between Version 1 and Version 2 of Ticket #33056, comment 1
- Timestamp:
- 07/21/2015 03:30:52 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #33056, comment 1
v1 v2 1 In order to post this ticket, you first had to check a box saying you weren't reporting a security vulnerability. You then had to re-affirm this before you were able to submit this form. Next time, please follow the instructions to email potential security issues to security@{the WordPress url} .1 In order to post this ticket, you first had to check a box saying you weren't reporting a security vulnerability. You then had to re-affirm this before you were able to submit this form. Next time, please follow the instructions to email potential security issues to security@{the WordPress url} instead of posting here (this ensures security issues don't become public before we can fix them). 2 2 3 This doesn't appear to be a valid security concern. Usernames are not considered sensitive information. WordPress core even uses them to generate author page urls.3 This doesn't appear to be a valid security concern. 4 4 5 For more information see the following Tavern article or one of the dozens of related Trac tickets on this subject (a sample of which is below). 5 Usernames are not considered sensitive information. WordPress core even uses them to generate author page urls. 6 7 For more information see the following Tavern article or one of the dozens of related Trac tickets on this subject (I've included a couple below; you'll find many more by searching Trac). 6 8 7 9 http://wptavern.com/why-showing-the-wordpress-username-is-not-a-security-risk