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
Banned payment accounts #6137
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Hi a user has brought this up again. @alvasw please can you let me know if a solution is feasible |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi @jmacxx is this something you would be able to take on? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant. |
Description
I was using debugger and saw a lot of records in
filterManager.getFilter().getBannedPaymentAccounts()
. Most of them contains sensitive data like email, username, phone etc. I'm pretty sure I didn't set them manually, so probably they were propagated via P2P network. It seems to be a security issue.Version
1.8.6
Steps to reproduce
Not reproduceable via UI. Use debugger, stop somewhere where
filterManager
is available and checkfilterManager.getFilter().getBannedPaymentAccounts()
Expected behaviour
I'm not sure - propositions:
The text was updated successfully, but these errors were encountered: