-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
dd664e6
commit afa1d5b
Showing
4 changed files
with
28,132 additions
and
11,945 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,40 +1,40 @@ | ||
=== security-txt === | ||
Plugin Name: Security-TXT | ||
Tags: security, infosec, netsec, security.txt, disclosure, bug bounty | ||
Requires at least: 5.0 | ||
Tested up to: 6.1.1 | ||
Stable tag: 6.1.1 | ||
Requires PHP: 7.0 | ||
License: GPLv3 or later | ||
License URI: https://github.com/tstokes8040/security-txt/blob/main/LICENSE.txt | ||
GitHub Plugin URI: https://github.com/tstokes8040/security-txt | ||
|
||
A plugin for serving 'security.txt' in WordPress 6.1.1+. | ||
|
||
== Description == | ||
|
||
This plugin creates a security.txt file in the WordPress installation root. | ||
|
||
You can edit/add to this file within the WordPress SecurityTXT settings page. | ||
|
||
The purpose of the security.txt file is to allow users to properly disclose security vulnerabilities or bugs to you. | ||
|
||
The [security.txt](https://securitytxt.org/) file is currently a draft "standard". This file is similar to the robots.txt file but for security. Large companies have already started to adopt this standard including Google, Facebook, GitHub, just to name a few. | ||
|
||
We welcome development to make this plugin even better! Create your [pull request](https://github.com/tstokes8040/security-txt) or [submit a bug here](https://github.com/tstokes8040/security-txt). | ||
|
||
== Installation == | ||
|
||
1. Upload `security-txt` to the `/wp-content/plugins/` directory. | ||
1. Activate the plugin through the 'Plugins' menu in WordPress. | ||
1. Configure the plugin using the 'Security TXT' link under 'Tools'. | ||
|
||
== Changelog == | ||
|
||
= 1.0.3 = | ||
* Initial release. | ||
|
||
== Upgrade Notice == | ||
|
||
= 1.0.3 = | ||
* Initial release. | ||
=== security-txt === | ||
Plugin Name: Security-TXT | ||
Tags: security, infosec, netsec, security.txt, disclosure, bug bounty | ||
Requires at least: 5.0 | ||
Tested up to: 6.2.2 | ||
Stable tag: 1.0.4 | ||
Requires PHP: 7.0 | ||
License: GPLv3 or later | ||
License URI: https://github.com/tstokes8040/security-txt/blob/main/LICENSE.txt | ||
GitHub Plugin URI: https://github.com/tstokes8040/security-txt | ||
A plugin for serving 'security.txt' in WordPress 6.1.1+. | ||
== Description == | ||
This plugin creates a security.txt file in the WordPress installation root. | ||
You can edit/add to this file within the WordPress SecurityTXT settings page. | ||
The purpose of the security.txt file is to allow users to properly disclose security vulnerabilities or bugs to you. | ||
The [security.txt](https://securitytxt.org/) file is currently a draft "standard". This file is similar to the robots.txt file but for security. Large companies have already started to adopt this standard including Google, Facebook, GitHub, just to name a few. | ||
We welcome development to make this plugin even better! Create your [pull request](https://github.com/tstokes8040/security-txt) or [submit a bug here](https://github.com/tstokes8040/security-txt). | ||
== Installation == | ||
1. Upload `security-txt` to the `/wp-content/plugins/` directory. | ||
1. Activate the plugin through the 'Plugins' menu in WordPress. | ||
1. Configure the plugin using the 'Security TXT' link under 'Tools'. | ||
== Changelog == | ||
= 1.0.4 = | ||
* Initial release. | ||
== Upgrade Notice == | ||
= 1.0.4 = | ||
* Initial release. |
Oops, something went wrong.