NB-Public/security-hall-of-fame
11
0
Fork 0
Code Issues Pull requests 2 Projects Releases Wiki Activity

Fix minor issues

Browse source 
- Redo indentation
- Remove blanking
- Fix EOF whitespace
- Equalise trailing slashes on meta tags
- Fix typos
This commit is contained in:
Henrik HerHde Huettemann 2022-11-09 15:20:50 +01:00
parent 5ee619229e
commit cbdb83e6dd
Signed by: HueHe
GPG key ID: 9F7BD10E0A8A111E
3 changed files with 37 additions and 33 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
acknowledgements.html
View file

@ -3,28 +3,28 @@
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Vulnerability Report Acknowledgements</title>
<style>
h1, h2, h3 {
text-align: center;
}
h1, h2, h3 {
text-align: center;
}
</style>
</head>
<body style="background-color: #fff;">
<div style="max-width: 600px; margin-left: auto; margin-right: auto;">
<div style="max-width: 600px; margin-left: auto; margin-right: auto;">
<h1>Acknowledgements / Hall of Fame</h1>
<h1>Acknowledgements/Hall of Fame</h1>
<h3>verdigado eG and Netzbegr&uuml;nung eV recognize the following security researchers for their vulnerability reports.</h3>
<h3>verdigado eG and Netzbegr&uuml;nung eV recognize the following security researchers for their vulnerability reports.</h3>
<ul>
<li>2021-12-02: Mayank Mukhi &lt;mnkmukhi@gmail.com&gt;, Information Disclosure</li>
<li>2021-11-26: Madras, Information Disclosure (Wolke)</li>
<li>2020-12-04: Chabik Hatim &lt;chabikhatim@gmail.com&gt;, Cross Site Scripting (GCMS)</li>
</ul>
<ul>
<li>2021-12-02: Mayank Mukhi &lt;mnkmukhi@gmail.com&gt;, Information Disclosure</li>
<li>2021-11-26: Madras, Information Disclosure (Wolke)</li>
<li>2020-12-04: Chabik Hatim &lt;chabikhatim@gmail.com&gt;, Cross Site Scripting (GCMS)</li>
</ul>
</div>
</div>
</body>
</html>

34
index.html
View file

@ -3,24 +3,28 @@
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Security @ verdigado / Netzbegruenung</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Security @ verdigado/Netzbegruenung</title>
<style>
h1, h2, h3 {
text-align: center;
}
h1, h2, h3 {
text-align: center;
}
</style>
</head>
<body style="background-color: #fff;">
<div style="max-width: 600px; margin-left: auto; margin-right: auto;">
<h1>Resources</h1>
<ul>
<li>Contact: security@verdigado.com</li>
<li><a href="policy.txt">Security and Vulnerability Reporting Policy</a></li>
<li><a href="acknowledgements.html">Acknowledgements for reported vulnerabilities</a></li>
<li><a href="https://securitytxt.org">All our web services serve a security.txt file</a></li>
<li><a href="https://cert.netzbegruenung.de">Netzbegruenung CERT</a></li>
</div>
<body style="background-color: #fff;">
<div style="max-width: 600px; margin-left: auto; margin-right: auto;">
<h1>Resources</h1>
<ul>
<li>Contact: <a href="mailto:security@verdigado.com">security@verdigado.com</a></li>
<li><a href="policy.txt">Security and Vulnerability Reporting Policy</a></li>
<li><a href="acknowledgements.html">Acknowledgements for reported vulnerabilities</a></li>
<li><a href="https://securitytxt.org">All our web services serve a security.txt file</a></li>
<li><a href="https://cert.netzbegruenung.de">Netzbegruenung CERT</a></li>
</ul>
</div>
</body>
</html>

8
policy.txt
View file

@ -24,7 +24,7 @@ reports one of the following problems:
2. The vulnerability can be used to disrupt the orderly operation of a
service (Denial of Service).
3. The vulnerability can be used to manipulate data within the service.
4. XSS, CSRF, RCE, authentication/authorization bypass, SQL inections,
4. XSS, CSRF, RCE, authentication/authorization bypass, SQL injections,
etc are considered relevant.
B) We will consider a vulnerability report most likely as NOT relevant if
@ -33,7 +33,7 @@ it reports one of the following problems:
actually preventing a vulnerability.
2. Publicly accessible information such as version strings of used
software and previously publicly known information in general.
3. Security vulnerablities that can only be used within the scope of the
3. Security vulnerabilities that can only be used within the scope of the
used account.
4. Reporting Vulnerabilities
@ -52,7 +52,7 @@ For used open source software, we recommend to file bug reports and/or
pull requests against the upstream repositories. This includes hardening
instructions in the installation documentation.
5. Bug Bounties / Rewards
5. Bug Bounties/Rewards
The amount of reward payed depends on the severity of the found
vulnerability. We usually do not pay rewards if vulnerabilities can be
@ -62,7 +62,7 @@ Only responsible disclosures are eligible for rewards.
6. Acknowledgement
We list recognized reports of vulnerablities online if the reporting
We list recognized reports of vulnerabilities online if the reporting
security researcher agrees. The name, contact e-mail address, and type
of vulnerability can be included in the list. Our public
acknowledgements can be found at