Skip to content

Latest commit

 

History

History
executable file
·
43 lines (30 loc) · 1.24 KB

SECURITY.md

File metadata and controls

executable file
·
43 lines (30 loc) · 1.24 KB

Reporting security issues

Please report security issues related to the reload4j project or log4j 1.x to the following email address:

support(at)qos.ch

Verifying contents

All reload4j project artifacts published on Maven central are signed. For each artifact, there is an associated signature file with the .asc suffix.

To verify the signature use this public key. Here is its fingerprint:

pub   2048R/A511E325 2012-04-26
Key fingerprint = 475F 3B8E 59E6 E63A A780  6748 2C7B 12F2 A511 E325
uid   Ceki Gulcu <[email protected]>
sub   2048R/7FBFA159 2012-04-26

A copy of this key is stored on the keys.openpgp.org keyserver. To add it to your public key ring use the following command:

> FINGER_PRINT=475F3B8E59E6E63AA78067482C7B12F2A511E325
> gpg  --keyserver hkps://keys.openpgp.org --recv-keys $FINGER_PRINT

Preventing commit history overwrite

In order to prevent loss of commit history, developers of the project are highly encouraged to deny branch deletions or history overwrites by invoking the following two commands on their local copy of the repository.

git config receive.denyDelete true
git config receive.denyNonFastForwards true