Skip to content
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

Passwords with ; in it won't work with /secure #324

Closed
HptmHavoc opened this Issue Jan 29, 2015 · 5 comments

Comments

Projects
None yet
4 participants
@HptmHavoc
Copy link

HptmHavoc commented Jan 29, 2015

Passwords with ; in it wont work with /secure. If you want to paste your password you only get the part till ; . For Example if you make a password like 123;546 and you want to paste it, you only get 123. If you create an password with a generator with special chars it isn't impossible that it contain this char.

@stfnm

This comment has been minimized.

Copy link
Contributor

stfnm commented Jan 29, 2015

What do you mean by pasting?

/secure set test 123;456
/eval -n ${sec.data.test}

This example works just fine for me and displays the expected result:

>> ${sec.data.test}
== [123;456]
@HptmHavoc

This comment has been minimized.

Copy link
Author

HptmHavoc commented Jan 29, 2015

This works, correct, but if you want to show the password, only for example, to a chan or want it to sent it to someone or want to identify your nick this won't work. The char ; works as a seperator, you get 2 lines.
Try /eval /msg #channame ${sec.data.test}

@flashcode

This comment has been minimized.

Copy link
Member

flashcode commented Jan 29, 2015

The problem is not secured data, but /eval which automatically splits the commands on ";".
I'll remove that from /eval (and add another way to split commands, if needed, but not done by default).

@flashcode flashcode added the bug label Jan 29, 2015

@flashcode flashcode added this to the 1.2 milestone Jan 29, 2015

@flashcode flashcode self-assigned this Jan 29, 2015

@Shawn-Smith

This comment has been minimized.

Copy link
Contributor

Shawn-Smith commented Jan 29, 2015

Maybe just add a -nosplit option to eval instead of removing it all together?

@flashcode

This comment has been minimized.

Copy link
Member

flashcode commented Jan 30, 2015

I'll probably enable the split with a new option, but not do it by default (I think in most cases, you don't want to split the content after /eval).

@flashcode flashcode closed this in 5e2cd75 Jan 30, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.