Add modules to repository

This commit is contained in:
Sebastian Kinne
2017-11-16 16:42:22 +11:00
commit d0aa1e38ef
707 changed files with 96750 additions and 0 deletions

36
Papers/includes/help/build.help Executable file
View File

@@ -0,0 +1,36 @@
<h4 style="color:red">WARNING!</h4>
<strong>Do not encrypt the private key in the set you will use for SSL on the Pineapple! If you do nginx will require a password upon boot which you will not have the chance to enter thus forcing you to factory reset your Pineapple!</strong>
<hr />
<strong>Key Type</strong><br />
Select the type of keys you want to build.
<br /><br />
<strong>Bit Size</strong><br />
This is the key length. The higher the value the harder it is to crack the key. Higher values will take longer to build and longer to check when used in applications. 2048 is the recommended value for web applications.
<br /><br />
<strong>Key Pair Name</strong><br />
This is the name of your keys when they are generated. Single word names are best.
<br /><br />
<strong>Days Valid</strong><br />
This value indicates how long the certificate will be valid. A default value of 365 days is set for convenience.
<br /></br >
<strong>Signature Algorithm</strong><br />
SHA-1 is considered to be too weak these days, or it will be soon enough, so SHA-256 is selected by default.
<br /><br />
<strong>Certificate Info (click to expand)</strong><br />
These fields are self explanatory and provide information that gets embedded in the public key. This can be left blank but if so the default settings will be used by OpenSSL.
<br /><br />
<strong>Encrypt Private Key</strong><br />
Check this box if you want to require a password to view the private key. You will have to select an algorithm (SHA-256 by default) and enter a password.
<br /><br />
<strong>Export keys to PKCS#12 container</strong><br />
Check this box if you want to export both the private and public keys into an encrypted container. This option will generate three files (.cer, .pem, .pfx).

View File

@@ -0,0 +1,10 @@
<strong>SSL Certificate and Private Key</strong><br />
Displays the keys currently being used by nginx on your Pineapple. These values are pulled directly from /etc/nginx/nginx.conf so they are always current.
<br /><br />
<strong>Dependencies</strong><br />
The only dependencies for Papers are zip and unzip which are downloaded via opkg. They are used to pack, and unpack, certificate archives for download/upload.
<br /><br />
<strong>Remove SSL</strong><br />
This reverts the Pineapple back to its original web configuration and removes all traces of SSL from the nginx config. This does not affect the certificate store or any configuration in the Papers module.

21
Papers/includes/help/store.help Executable file
View File

@@ -0,0 +1,21 @@
<strong>Encrypted</strong><br />
Displays if the private key (.pem) is encrypted. Does not include encryption on .pfx containers.
<br /><br />
<strong>PineSSL / PineSSH</strong><br />
For TLS/SSL keys this button configures SSL on the Pineapple or swaps the current SSL keys with those selected.
<br />
For SSH key pairs this button has two modes (the state does not change for TLS/SSL keys):
<br /><br />
<ul>
<li><img src="/modules/Papers/includes/icons/glyphicons-204-lock.png"/>&nbsp&nbsp;Add key to /root/.ssh/authorized_keys to allow connections to users who hold the private key.<br /><br />
<li><img src="/modules/Papers/includes/icons/glyphicons-205-unlock.png"/>&nbsp;&nbsp;Revoke key from /root/.ssh/authorized_keys to deny connections from those who use the private key.
</ul>
<br />
<strong>Download</strong><br />
Packages the keys in the selected row into a zip archive and downloads it.
<br /><br />
<strong>Delete</strong><br />
Removes the selected keys from the SSL store. This can't be undone.