-
Notifications
You must be signed in to change notification settings - Fork 290
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
Security concern #1341
Comments
Thank you: can you kindly send to [email protected] |
[email protected] is an open mailing list. So I think given the confidential thing of the information, a more private contact would be preferable. By the way, I have been chatting with @jb55 a bit in advance at [email protected]. @jb55 |
Email Will directly at the email you mentioned in that case |
Could you check the new SECURITY.md and contact @jb55 using his email address, if you have never contacted him yet? |
The upcoming nostrdb changes fixes all this because the ingress thread will handle verification on all events before insertion into the database, similar to how strfry does it. |
Does this mean with db update all incoming events are automagically validated? |
Thats the plan |
@jb55 is this resolved? |
On Mon, Sep 25, 2023 at 12:50:59PM -0700, alltheseas wrote:
@jb55 is this resolved?
it will be when we switch to nostrdb for our note cache (soon), but not yet.
|
Do you want to commit to this for the sprint first half of October? |
On Tue, Sep 26, 2023 at 06:35:34AM -0700, alltheseas wrote:
> On Mon, Sep 25, 2023 at 12:50:59PM -0700, alltheseas wrote: @jb55 is this resolved?
> it will be when we switch to nostrdb for our note cache (soon), but not yet.
Do you want to commit to this for the sprint first half of October?
It's a pretty crazy month for me (pacific, amsterdam, bali, tokyo), so probably not. Will be back at it after nostrasia.
|
Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@prprhyt) has found a potential issue, which I would be eager to share with you.
Could you add a
SECURITY.md
file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.Looking forward to hearing from you 👍
(cc @huntr-helper)
The text was updated successfully, but these errors were encountered: