[wp-meta] [Making WordPress.org] #8030: Introduce different SVN Application passwords for different/high security SVN instances (develop, meta, w.org deploy)

Making WordPress.org noreply at wordpress.org
Mon Jul 7 01:05:03 UTC 2025


#8030: Introduce different SVN Application passwords for different/high security
SVN instances (develop, meta, w.org deploy)
-----------------------------+---------------------
 Reporter:  peterwilsoncc    |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  low              |   Milestone:
Component:  Version Control  |  Resolution:
 Keywords:                   |
-----------------------------+---------------------
Changes (by dd32):

 * priority:  normal => low
 * type:  defect (bug) => feature request


Comment:

 > Would it be possible to either:

 Unfortunately at this point in time the implementation doesn't allow for
 this type of flexibility.

 The limitation primarily comes from the `mod_auth_mysql` code in use
 (Although we're using a customised version:
 https://code.trac.wordpress.org/browser/mod_auth_mysql) which only allows
 a singular user/pass combo to be used.

 When SVN Passwords were introduced, I investigated replacing it with
 something that allowed for this kind of fine-grained access, but that was
 rejected due to introducing a PHP requirement into the SVN authentication
 flow.

 > For developers using a GitHub action to deploy themes or plugins, this
 is great as it prevents users from recording their w.org credentials as
 secrets on the system.

 Potentially we should be looking at removing the need for recording
 credentials in such locations instead.


 ----

 I'm leaving this ticket open, rather than closing as a duplicate or
 wontfix, as it's something I personally would like to see.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8030#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list