• As a publisher, if I set my WordPress.org password to say a 22-character random sequence of letters numbers and symbols, authentication fails when I update/commit my plugin.

    If I make the password shorter and only letters and numbers, say 8 characters, authentication works fine. How can I fix this?

    The only thing I can think of is the password being somehow truncated when it’s saved in WordPress.org profile options and sent to the SVN server.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    No, the passwords are not truncated. However, certain special characters, particularly non-ascii ones, can get encoded by your SVN client into something different before they’re sent. This results in a password mismatch.

    Length is not an issue, but the character set and code-page used is. Stick to plain ASCII.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Also, we don’t actually know your password here on WordPress.org. It’s not saved anywhere. All we save is the hash, same as WordPress itself does. The SVN authentication does a hashed value comparison against that value. It’s checking against the database in real-time, your password is not “sent to the SVN server” on our end in any way.

    Thread Starter wpspamhammer

    (@wpspamhammer)

    It is already all ASCII; if it’s not truncated something else is happening here. Try it for yourself 😮

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    Perhaps it just doesn’t like some of the symbols you’re using then. Percent signs might be a problem. Not sure, as it’s an SVN thing.

    Regardless, I know long passwords work fine. My own password is not a short one. 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘[WordPress.org] SVN Password Truncation’ is closed to new replies.