Skip to content
This repository has been archived by the owner on Dec 24, 2022. It is now read-only.

Trying to get in touch regarding a security issue #24

Open
JamieSlome opened this issue Jul 1, 2022 · 3 comments
Open

Trying to get in touch regarding a security issue #24

JamieSlome opened this issue Jul 1, 2022 · 3 comments

Comments

@JamieSlome
Copy link

Hello 馃憢

I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@J-GainSec) 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)

@bc1bb
Copy link

bc1bb commented Dec 22, 2022

Hi, any update on this ?

I dont wanna selfhost a service with a known vulnerability...

@psmoros
Copy link

psmoros commented Dec 23, 2022

The vulnerability is private but would be good to get an opinion...

@lebriton
Copy link
Owner

  1. I haven't used/worked on this project for months.
  2. I didn't get in touch with OP.

I no longer wish to maintain IHTB, see #26.

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

4 participants