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

Typing in text input field in Chrome sometimes triggers a password security alert #1265

Open
thisisnotnotnotmyrealname opened this issue Dec 14, 2024 · 3 comments

Comments

@thisisnotnotnotmyrealname

Describe the Issue
Sometimes when typing in the input field, Chrome will pop up its security nanny warning saying that I just entered my password on a deceptive site. I can only assume this is because Chrome thinks the input field is a password field for some reason.

Additional Information:
I am running KoboldCPP in Docker on Debian in a Proxmox virtual machine. I am accessing the site through my own domain using adguard local DNS and Caddy reverse proxy. The blacked out part in the screenshot is my domain that Chrome is warning me about.
image

@LostRuins
Copy link
Owner

I assume this happens because the page is served over http or is localhost? I haven't seen this warning before. Does it happen on all input fields or only specific ones ?

Lite does have api keys using a password input field that unmasks when selected.

@thisisnotnotnotmyrealname
Copy link
Author

It's being served over https thanks to my reverse proxy. The url is https://kob.mydomain.com

I have only seen it in the input_text field and only twice so far in thousands of words of text entry. Both times was when I was literally in the middle of typing a sentence.

I have seen this occasionally on other sites on my LAN hosted behind a reverse proxy but those times it was when I had actually entered a password in an actual password field.

@LostRuins
Copy link
Owner

LostRuins commented Dec 14, 2024

Then it's very strange. A regular input text field should not be treated as a password. Could it be due to some extension, or perhaps a browser bug.

If you figure it out let me know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants