Sun Coast Amateur
Radio Club Society

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== About Encryption ======
After flashing the hAP, this message will appear only once:

<WRAP box center round 80%>
<html>
<center>
<b>
This node is not yet configured.<br>
Go to the setup page and set your node name and password.<br>
Click Save Changes, <u>even if you didn't make any changes</u>, then the node will reboot.
</b><br><br>
</center>

<div style="margin-top: 0px; margin-left: auto; margin-right:auto;
text-align: left; max-width: 600px;">
<p>This device can be configured to either permit or prohibit known encrypted traffic on its RF link. It is up to the user to decide which is appropriate based on how it will be used and the license under which it will be operated. These rules vary by country, frequency, and intended use. You are encouraged to read and understand these rules before going further.</p>
<p>This device is pre-configured with no restrictions as to the type of data being passed.</p>
<p>Follow these steps if you wish to prohibit known encrypted traffic on the RF link. These instructions will disappear, so copy them for your reference:</p>
<p>
<ol>
    <li>Setup your node name and password as instructed at the top of this page</li>
    <li>After you Save Changes allow your node to reboot</li>
    <li>Return to the Node Status page and navigate to Setup &gt Administration</li>
    <li>Obtain the blockknownencryption package from the AREDN&trade; website OR refresh the Package list (node must be connected to the internet)</li>
    <li>Install the blockknownencryption package by uploading it or choosing it from the package drop-down list</li>
    <li>Wait until the package installs and then reboot your node</li>
</ol></p>
</div>
</html>
</WRAP>

Section 47 (b) of the [[https://laws-lois.justice.gc.ca/eng/regulations/SOR-96-484/FullText.html |Radiocommunication Regulations]] stipulates that:
<QUOTE>
**47** A person who operates radio apparatus in the amateur radio service may only:

<wrap indent>**(b)** use a code or cipher that is not secret</wrap>
</QUOTE>

<WRAP important round center 80%>
  * Unencrypted data uses a code that is not secret so it's not a problem
  * but encrypted data uses ciphers that are secret, so it's not allowed.
</WRAP>

To ensure that no encrypted data is transmitted on the air, ensure that you do **not** allow other mesh nodes to your your WAN.

  * On the old UI, this setting is in the ''Advanced Configuration'':
{{  wansettings.png  }}

  * On the new UI:
    - Login.
    - Click in the ''NETWORK'' area on the left-hand side of the screen.
    - Expend the ''Advanced Options''
    - Make sure that ''Mesh to WAN'' is toggled off (red).
{{  wansettings_new.png  }}

For more information, see: https://docs.arednmesh.org/en/latest/arednGettingStarted/node_admin.html#mesh-to-wan
/*
To ensure that no encrypted data is transmitted on the air, install the ''blockknownencryption'' package from the ''Administration'' page:
{{  blockknownencryption.png  }}

This should pretty much block any ''https'' addresses but it could have [[https://www.arednmesh.org/content/block-known-encryption |some issues]].  And here's a more [[https://www.arednmesh.org/content/when-can-i-allow-others-use-my-wan |technical discussion]].

<WRAP center round info 80%>
Note that this might block ''ssh'' over RF but not over LAN.  However, Telnet can be used over RF as it is not encrypted.
</WRAP>
*/