Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #33056, comment 1


Ignore:
Timestamp:
07/21/2015 03:30:52 AM (9 years ago)
Author:
chriscct7
Comment:

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}.
     1In 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).
    22
    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.
     3This doesn't appear to be a valid security concern.
    44
    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).
     5Usernames are not considered sensitive information. WordPress core even uses them to generate author page urls.
     6
     7For 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).
    68
    79http://wptavern.com/why-showing-the-wordpress-username-is-not-a-security-risk