-
Notifications
You must be signed in to change notification settings - Fork 92
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 contact #276
Comments
This project (hnhx/librex) is no longer being actively developed. Me and several other developers have started a fork from this codebase at Ahwxorg/LibreY. Please let us know about this issue because we might also be vulnerable and so we can make a fix available! You can contact the main developer through matrix or email, which is available on our security policy over on our repo. |
Rabenherz112
added a commit
to Rabenherz112/awesome-selfhosted-data
that referenced
this issue
Jun 24, 2024
- ref: awesome-selfhosted#1 - `ERROR:awesome_lint.py: LibreX: last updated -366 days, 1:30:55.443609 ago, older than 365 days` - In a security issue, a contributor mentioned that LibreX is not maintained anymore and they forked it (hnhx/librex#276) - [The Fork](https://github.com/Ahwxorg/LibreY) however does not have any releases and therfore doesn't meet our requirements
nodiscc
pushed a commit
to awesome-selfhosted/awesome-selfhosted-data
that referenced
this issue
Jun 24, 2024
- ref: #1 - `ERROR:awesome_lint.py: LibreX: last updated -366 days, 1:30:55.443609 ago, older than 365 days` - In a security issue, a contributor mentioned that LibreX is not maintained anymore and they forked it (hnhx/librex#276) - [The Fork](https://github.com/Ahwxorg/LibreY) however does not have any releases and therfore doesn't meet our requirements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello maintainer(s),
I am a security researcher from the Institute of Application Security at TU Braunschweig, Germany. We discovered a (potential) security vulnerability in your project.
We would like to report this vulnerability to you in a responsible and ethical manner.
Therefore, we do not want to disclose any details of the vulnerability publicly until you have had a chance to review and fix it.
Could you please let us know your prefered way of receiving security reports?
You can contact us at [email protected] or by replying to this issue.
Thank you for your attention and cooperation.
The text was updated successfully, but these errors were encountered: