free
/
freedombone
Seguir 1
Destacar 0
Cuchillo 0
Código Incidencias 0 Peticiones pull 0 Lanzamientos 0 Wiki Activity
Explorar el Código

Instructions for configuring SIP apps

Bob Mottram hace 9 años
padre
616b874bb4
commit
32097104ea
Se han modificado 2 ficheros con 145 adiciones y 1 borrados
Unificar vista Mostrar estadísticas de diff
  1. 26
    0
      doc/EN/usage.org
  2. 119
    1
      website/EN/usage.html

+ 26
- 0
doc/EN/usage.org Ver fichero

311 
 /Note: if you don't know the default domain name and you did a full installation then it will be the same as the wiki domain name./
 311 
 /Note: if you don't know the default domain name and you did a full installation then it will be the same as the wiki domain name./
312 
 ** SIP phones
 312 
 ** SIP phones
313 
 Freedombone also supports SIP phones The username and domain is the same as for your email address, and the SIP password and extension number will appear within the README file in your home directory. Various SIP client options are available, such as CSipSimple on Android and Jitsi on desktop or laptop machines. Ideally use clients which support ZRTP, which will provide the best level of security.
 313 
 Freedombone also supports SIP phones The username and domain is the same as for your email address, and the SIP password and extension number will appear within the README file in your home directory. Various SIP client options are available, such as CSipSimple on Android and Jitsi on desktop or laptop machines. Ideally use clients which support ZRTP, which will provide the best level of security.
314 
+*** About ZRTP
315 
+[[https://jitsi.org/Documentation/ZrtpFAQ][ZRTP]] appears to be the current best standard to end-to-end encrypted voice calls, combining good security with simplicity of use. When the initial cryptographic negotiation between phones is done at the start of a call a short authentication string (SAS) is calculated and displayed at both ends. To check that there isn't anyone intercepting the call and acting as a /man in the middle/ - as [[https://en.wikipedia.org/wiki/Stingray_phone_tracker][stingray type devices]] try to do - the short authentication string can be read out and verbally confirmed between the callers. If it's the same then you can be pretty confident that the call is secure.
316 
+*** Using with CSIPSimple
317 
+Add an account. Under *General Wizards* choose *Expert* and enter the following details:
318 
+
319 
+| Account name     | Your username           |
320 
+| Account ID       | sip:username@yourdomain |
321 
+| Registration URI | sip:yourdefaultdomain   |
322 
+| Realm            | *                       |
323 
+| Username         | Your username           |
324 
+| Data (Password)  | Your SIP password       |
325 
+| ZRTP Mode        | Create ZRTP             |
326 
+
327 
+If everything is working the account should appear in green with a status of *Registered*.
328 
+*** Using with Ring
329 
+From the menu select *Manage accounts*.
330 
+
331 
+Add an account with the following details:
332 
+
333 
+| Alias    | Your full name or nickname |
334 
+| Protocol | SIP                        |
335 
+| Hostname | yourdefaultdomain          |
336 
+| Username | Your username              |
337 
+| Password | Your SIP password          |
338 
+
339 
+Select the *Security* tab. Under *SRTP Key Exchange* select *ZRTP*. Unde *SRTP Preferences* select *Not supported warning* and *Display SAS Once*.
314
340
315 
 * RSS Reader
 341 
 * RSS Reader
316 
 The way that RSS reading is set up on Freedombone gives you strong reading privacy. Not only is there onion routing between you and the server but also between the server and the source of the RSS feed. The only down side is that many RSS feeds are still http only, and so could be vulnerable to injection attacks, but it's expected that more of this will go to https in the foreseeable future due to a combination of growing recognition of security issues and systems like Let's Encrypt which make obtaining certificates much easier.
 342 
 The way that RSS reading is set up on Freedombone gives you strong reading privacy. Not only is there onion routing between you and the server but also between the server and the source of the RSS feed. The only down side is that many RSS feeds are still http only, and so could be vulnerable to injection attacks, but it's expected that more of this will go to https in the foreseeable future due to a combination of growing recognition of security issues and systems like Let's Encrypt which make obtaining certificates much easier.

+ 119
- 1
website/EN/usage.html Ver fichero

3 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 3 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
 4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 
 <head>
 5 
 <head>
6 
-<!-- 2016-03-20 Sun 15:23 -->
6 
+<!-- 2016-03-22 Tue 20:01 -->
7 
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
 7 
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 8 
 <meta name="viewport" content="width=device-width, initial-scale=1" />
9 
 <title></title>
 9 
 <title></title>
832 
 Freedombone also supports SIP phones The username and domain is the same as for your email address, and the SIP password and extension number will appear within the README file in your home directory. Various SIP client options are available, such as CSipSimple on Android and Jitsi on desktop or laptop machines. Ideally use clients which support ZRTP, which will provide the best level of security.
 832 
 Freedombone also supports SIP phones The username and domain is the same as for your email address, and the SIP password and extension number will appear within the README file in your home directory. Various SIP client options are available, such as CSipSimple on Android and Jitsi on desktop or laptop machines. Ideally use clients which support ZRTP, which will provide the best level of security.
833 
 </p>
 833 
 </p>
834 
 </div>
 834 
 </div>
835 
+<div id="outline-container-orgheadline34" class="outline-4">
836 
+<h4 id="orgheadline34">About ZRTP</h4>
837 
+<div class="outline-text-4" id="text-orgheadline34">
838 
+<p>
839 
+<a href="https://jitsi.org/Documentation/ZrtpFAQ">ZRTP</a> appears to be the current best standard to end-to-end encrypted voice calls, combining good security with simplicity of use. When the initial cryptographic negotiation between phones is done at the start of a call a short authentication string (SAS) is calculated and displayed at both ends. To check that there isn't anyone intercepting the call and acting as a <i>man in the middle</i> - as <a href="https://en.wikipedia.org/wiki/Stingray_phone_tracker">stingray type devices</a> try to do - the short authentication string can be read out and verbally confirmed between the callers. If it's the same then you can be pretty confident that the call is secure.
840 
+</p>
841 
+</div>
842 
+</div>
843 
+<div id="outline-container-orgheadline35" class="outline-4">
844 
+<h4 id="orgheadline35">Using with CSIPSimple</h4>
845 
+<div class="outline-text-4" id="text-orgheadline35">
846 
+<p>
847 
+Add an account. Under <b>General Wizards</b> choose <b>Expert</b> and enter the following details:
848 
+</p>
849 
+
850 
+<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
851 
+
852 
+
853 
+<colgroup>
854 
+<col  class="org-left" />
855 
+
856 
+<col  class="org-left" />
857 
+</colgroup>
858 
+<tbody>
859 
+<tr>
860 
+<td class="org-left">Account name</td>
861 
+<td class="org-left">Your username</td>
862 
+</tr>
863 
+
864 
+<tr>
865 
+<td class="org-left">Account ID</td>
866 
+<td class="org-left">sip:username@yourdomain</td>
867 
+</tr>
868 
+
869 
+<tr>
870 
+<td class="org-left">Registration URI</td>
871 
+<td class="org-left">sip:yourdefaultdomain</td>
872 
+</tr>
873 
+
874 
+<tr>
875 
+<td class="org-left">Realm</td>
876 
+<td class="org-left">*</td>
877 
+</tr>
878 
+
879 
+<tr>
880 
+<td class="org-left">Username</td>
881 
+<td class="org-left">Your username</td>
882 
+</tr>
883 
+
884 
+<tr>
885 
+<td class="org-left">Data (Password)</td>
886 
+<td class="org-left">Your SIP password</td>
887 
+</tr>
888 
+
889 
+<tr>
890 
+<td class="org-left">ZRTP Mode</td>
891 
+<td class="org-left">Create ZRTP</td>
892 
+</tr>
893 
+</tbody>
894 
+</table>
895 
+
896 
+<p>
897 
+If everything is working the account should appear in green with a status of <b>Registered</b>.
898 
+</p>
899 
+</div>
900 
+</div>
901 
+<div id="outline-container-orgheadline36" class="outline-4">
902 
+<h4 id="orgheadline36">Using with Ring</h4>
903 
+<div class="outline-text-4" id="text-orgheadline36">
904 
+<p>
905 
+From the menu select <b>Manage accounts</b>.
906 
+</p>
907 
+
908 
+<p>
909 
+Add an account with the following details:
910 
+</p>
911 
+
912 
+<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
913 
+
914 
+
915 
+<colgroup>
916 
+<col  class="org-left" />
917 
+
918 
+<col  class="org-left" />
919 
+</colgroup>
920 
+<tbody>
921 
+<tr>
922 
+<td class="org-left">Alias</td>
923 
+<td class="org-left">Your full name or nickname</td>
924 
+</tr>
925 
+
926 
+<tr>
927 
+<td class="org-left">Protocol</td>
928 
+<td class="org-left">SIP</td>
929 
+</tr>
930 
+
931 
+<tr>
932 
+<td class="org-left">Hostname</td>
933 
+<td class="org-left">yourdefaultdomain</td>
934 
+</tr>
935 
+
936 
+<tr>
937 
+<td class="org-left">Username</td>
938 
+<td class="org-left">Your username</td>
939 
+</tr>
940 
+
941 
+<tr>
942 
+<td class="org-left">Password</td>
943 
+<td class="org-left">Your SIP password</td>
944 
+</tr>
945 
+</tbody>
946 
+</table>
947 
+
948 
+<p>
949 
+Select the <b>Security</b> tab. Under <b>SRTP Key Exchange</b> select <b>ZRTP</b>. Unde <b>SRTP Preferences</b> select <b>Not supported warning</b> and <b>Display SAS Once</b>.
950 
+</p>
951 
+</div>
952 
+</div>
835 
 </div>
 953 
 </div>
836 
 </div>
 954 
 </div>
837
955