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

CHANGING THE URL TO https://accounts-emea.f-secure.com DOES NOT WORK !! #2098

Closed
TESTER-sec opened this issue Jan 27, 2024 · 5 comments
Closed

Comments

@TESTER-sec
Copy link

The KeePassXC browser extension is not detecting the F-Secure account login page.

This is not a Microsoft Edge issue; it is a KeePassXC browser extension issue.

CHANGING THE URL TO https://accounts-emea.f-secure.com DOES NOT WORK !!

Expected Behavior
The KeePassXC browser extension should detect the F-Secure account login page so that the user can use KeePass to log into their F-Secure account. KeePassXC content script should show the KeePassXC element in both the username & password fields. The right-click --> Fill username & password should work. Also KeePassXC should detect the URL and a pop-up should appear so that the user can allow the field fill if they have not already permanently allowed it.

Current Behavior
Steps to Reproduce (for bugs)
Navigate to https://my.f-secure.com/login .
KeePassXC cannot detect a login, even though one exists in KeePassXC.
Debug info
KeePassXC - 2.7.6
KeePassXC-Browser - 1.8.11
Operating system: Windows 11 23H2
Browser: Microsoft Edge

@TESTER-sec
Copy link
Author

CHANGING THE URL TO https://accounts-emea.f-secure.com/ DOES NOT WORK !!

@TESTER-sec TESTER-sec changed the title KeePassXC Does Not Function Correctly on F-Secure Login Webpage CHANGING THE URL TO https://accounts-emea.f-secure.com DOES NOT WORK !! Jan 27, 2024
@varjolintu
Copy link
Member

Please. The issue is already fixed in #2079 and we are releasing a new version soon.

@varjolintu varjolintu closed this as not planned Won't fix, can't repro, duplicate, stale Jan 27, 2024
@TESTER-sec
Copy link
Author

Please. The issue is already fixed in #2079 and we are releasing a new version soon.

Just doing what @droidmonkey said to do. The only way to report that what he said to do does not work is to create another issue.

He told me to change the URL in KeePassXC and that would solve the problem - which is complete nonsense.

He doesn't provide very good support. Don't blame the user.

@varjolintu
Copy link
Member

Please. The issue is already fixed in #2079 and we are releasing a new version soon.

Just doing what @droidmonkey said to do. The only way to report that what he said to do does not work is to create another issue.

He told me to change the URL in KeePassXC and that would solve the problem - which is complete nonsense.

He doesn't provide very good support. Don't blame the user.

He also said this:
#2096 (comment)

You are just spamming the issue threads.

@TESTER-sec
Copy link
Author

You are just spamming the issue threads.

I have no idea what the connected issue is. I am not going to read it and even try to unravel it.

I am here for support. If you view that as "spamming the issue threads," well then that's on you. Not me.

@keepassxreboot keepassxreboot locked as too heated and limited conversation to collaborators Jan 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants