Skip to content

Conversation

@maflcko
Copy link
Member

@maflcko maflcko commented Apr 30, 2022

This was added in commit 438ee59, but I couldn't determine if it was intentional.

One reason to accept foo:bar:baz over foo:bar$baz is that $ may be eaten by the shell. Though, I don't think many users pass rpcauth via the shell. Also it should be easy to avoid by passing '-rpcauth=foo:bar$baz' or "-rpcauth=foo:bar\$baz".

Can be tested with the added test.

@pk-b2
Copy link

pk-b2 commented May 1, 2022

ACK fa12706

Tested various patterns manually. Behaves now as expected with the patch.

@bitcoin bitcoin deleted a comment from Meru852 May 1, 2022
@fanquake fanquake merged commit e389c4d into bitcoin:master May 1, 2022
@maflcko maflcko deleted the 2204-rpcauth-invalid-format-🍰 branch May 2, 2022 12:45
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request May 2, 2022
fa12706 Reject invalid rpcauth formats (MacroFake)

Pull request description:

  This was added in commit 438ee59, but I couldn't determine if it was intentional.

  One reason to accept `foo:bar:baz` over `foo:bar$baz` is that `$` may be eaten by the shell. Though, I don't think many users pass `rpcauth` via the shell. Also it should be easy to avoid by passing `'-rpcauth=foo:bar$baz'` or `"-rpcauth=foo:bar\$baz"`.

  Can be tested with the added test.

ACKs for top commit:
  pk-b2:
    ACK fa12706

Tree-SHA512: 9998cbb295c79f7b0342bf86e1d3e5b5ab90851c627662ad6495b699a65a9035998173cf1debfd94325387faba184de683407b609fe86acdd8f6749157644441
@bitcoin bitcoin locked and limited conversation to collaborators May 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants