-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing Basic Auth from config file fails when password has a pound sign # in it. #194
Comments
ms-accounts-x-arvesta
changed the title
Parsing Basic Auth from config file fails when password hast a pound sign # in it.
Parsing Basic Auth from config file fails when password has a pound sign # in it.
Jun 25, 2021
This looks right: ***@***.***:password_with_#_in_it:realm 2 However,
I think you encountered a bug. It's treating the password like a comment.
I'll try to provide a fix soon.
…On Fri, Jun 25, 2021 at 4:07 PM ms-accounts-x-arvesta < ***@***.***> wrote:
I have something like this in my configuration file:
login = user:pass:realm
login = ***@***.***:password_with_#_in_it:realm 2
Siege -C output:
CURRENT SIEGE CONFIGURATION
Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/4.0.9
Edit the resource file to change the settings.
----------------------------------------------
version: 4.0.9
[removed for clarity]
www auth: credentials: user:pass:realm
credentials: ***@***.***:password_with_:any
Whatever I try (quoting the whole string, quoting only the password,
escaping, urlencoding, trying to put the pass in a var and using that as
suggested for the url file in this issue: #189
<#189>), I cannot make siege
understand that the line shouldn't be cut off after the pound sign. Is this
just a feature of the parser, or have I overlooked something?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#194>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJRHZUP5UY2FT3CUQLVMK3TUTOYRANCNFSM47KPVDVA>
.
--
Jeff Fulmer
1-717-799-8226
https://www.joedog.org/
He codes
|
Submitted under the wrong username, I was asked to delete/close this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have something like this in my configuration file:
Siege -C output:
Whatever I try (quoting the whole string, quoting only the password, escaping, urlencoding, trying to put the pass in a var and using that as suggested for the url file in this issue: #189), I cannot make siege understand that the line shouldn't be cut off after the pound sign. Is this just a feature of the parser, or have I overlooked something?
The text was updated successfully, but these errors were encountered: