-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Bug With Passwords Including Ampersands? #12362
Comments
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
Hey, found a fix for this, going to see about submitting a pull request. |
That'd be awesome, thank you! |
Created a pull request at #12363 let me know if I need to add anything. Nothing major so idk if you need me to do all of the stuff but if it must be done I'd be glad to :D @uberbrady |
Fixed #12362: Bug With Passwords Including Ampersands?
Merged, ty! |
Debug mode
Describe the bug
Hello, loving Snipe thus far, however. I believe I may have accidentally found a bug involving passwords with ampersands and the auto generated email sent to users with credentials. I sent a user this automated email and the part of the password with the & also had amp; appended after the & (So, for example, instead of the password being "d57J08]& 'amp;' Sajb9VI" it was "d57J08]&Sajb9VI"). I'm assuming this may be an issue with the HTML used in email? Or would it be something on my end?
Reproduction steps
Expected behavior
Expected Password without the "amp;" as removing that portion of text fixes the issue.
Screenshots
Snipe-IT Version
v6.0.14 build 9038
Operating System
Turnkey Linux
Web Server
Apache 2.4.38
PHP Version
8.1.11
Operating System
Windows
Browser
Google Chrome
Version
109.0.5414.74 (64 bit)
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: