Slightly rephrase some of the text on the landing page
* 4096 bit keys are better * add port number to explanation * Firefox 26 isn't all that brand-new any more
This commit is contained in:
parent
4d2e85d1dd
commit
a069a171c2
1 changed files with 5 additions and 5 deletions
10
index.html
10
index.html
|
@ -127,14 +127,14 @@
|
||||||
<div id="collapseThree" class="panel-collapse collapse">
|
<div id="collapseThree" class="panel-collapse collapse">
|
||||||
<div class="panel-body">
|
<div class="panel-body">
|
||||||
If you check the encryption box, the communication between browser and WeeChat will be encrypted.<br>
|
If you check the encryption box, the communication between browser and WeeChat will be encrypted.<br>
|
||||||
<strong>Note</strong>: Due to a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=594502">bug</a> encryption will not work in Firefox. Unless you are using a certificate trusted by your browser, you must also first visit the URL https://weechathost:relayport/ to accept the certificate.</p>
|
<strong>Note</strong>: Due to a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=594502">bug</a> encryption will not work in Firefox. Unless you are using a certificate trusted by your browser, you must also first visit the URL https://weechathost:relayport/ to mark the certificate as trusted.</p>
|
||||||
If you want to use an encrypted session you first have to set up the relay using SSL. It is easiest to use a self-signed certificate, which you can create like this:
|
If you want to use an encrypted session you first have to set up the relay to use SSL. It is easiest to use a self-signed certificate, which you can create like this:
|
||||||
<pre>
|
<pre>
|
||||||
$ mkdir -p ~/.weechat/ssl
|
$ mkdir -p ~/.weechat/ssl
|
||||||
$ cd ~/.weechat/ssl
|
$ cd ~/.weechat/ssl
|
||||||
$ openssl req -nodes -newkey rsa:2048 -keyout relay.pem -x509 -days 365 -out relay.pem
|
$ openssl req -nodes -newkey rsa:4096 -keyout relay.pem -x509 -days 365 -out relay.pem
|
||||||
</pre>
|
</pre>
|
||||||
If WeeChat is already running, you can reload the certificate and private key with these commands:
|
If WeeChat is already running, you can reload the certificate and private key and set up an encrypted relay on port 8000 with these commands:
|
||||||
<pre>
|
<pre>
|
||||||
/relay sslcertkey
|
/relay sslcertkey
|
||||||
/relay add ssl.weechat 8000
|
/relay add ssl.weechat 8000
|
||||||
|
@ -152,7 +152,7 @@ $ openssl req -nodes -newkey rsa:2048 -keyout relay.pem -x509 -days 365 -out rel
|
||||||
</div>
|
</div>
|
||||||
<div id="collapseFour" class="panel-collapse collapse">
|
<div id="collapseFour" class="panel-collapse collapse">
|
||||||
<div class="panel-body">
|
<div class="panel-body">
|
||||||
<p>If you have a very recent version of Firefox you can install the frontend as an app. Click the button to install.</p>
|
<p>If you have a recent version of Firefox you can install glowing bear as an app. Click the button to install.</p>
|
||||||
<button class="btn btn-lg btn-primary" ng-click="install()">Install app <i class="glyphicon glyphicon-chevron-right"></i></button>
|
<button class="btn btn-lg btn-primary" ng-click="install()">Install app <i class="glyphicon glyphicon-chevron-right"></i></button>
|
||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
|
|
Loading…
Reference in a new issue