Differences

This shows you the differences between two versions of the page.

--- config_echomail_nodes [2019/03/16 17:21] – page 2 updates avon
+++ config_echomail_nodes [2019/03/16 17:39] – echomail secuity avon
@@ Line 244: / Line 244: @@
 Without this password set your Mystic BBS will ignore the files it receives and/or move them in to the BAD directory defined in the [FileToss] stanza of your MUTIL .ini file
+=== Encryption Key ===
+Echomail nodes now have an "Encryption Key" option.  When this option is set to a non-blank value, Mystic will encrypt all of the contents of Netmail messages to this node with an AES-256 encryption.  This completes a fully encrypted echomail solution as both transport and private messages are secured.
+This is done in a way that is completely transparent to unsupporting systems, meaning that you can still route netmail through systems and they will not harm the encrypted netmails!  The encryption also hides the message subject, so when combined with Area/Filefix passwords will no longer be readable. You must have Cryptlib installed for this to work.
+The other echomail node must of course have the same key configured for your node in order to decrypt the netmail when it arrives.  This works the same way as any other password setting in echomail nodes.
+When routing Netmail, Mystic will intelligently re-encrypt the message between routing points when possible.  In other words if you have a point system who sends from 555:1/2.1 to 555:1/1 but is routed through 555:1/2,   Mystic at 555:1/2 will know that it has an encryption agreement between both 555:1/2.1 and 555:1/1 so it will decrypt the message from 555:1/2.1 and then re-encrypt it for 555:1/1 before routing it.
 === Security Level ===
-Placeholder text - this feature under development 1.12 A38
+You can set ACS rules for this EchoMail node.
 === Access Flags ===
-Placeholder text - this feature under development 1.12 A38
+You can set access flags for this EchoMail Node.
+=== Echomail Node Security ====
+The beginning of Echomail node security is here!  The easiest way to think about how this system works is to relate an Echomail node to the way security works for a user in your BBS.  Each node will have a security   level, access flags, and can be a member of many Echomail groups (up to 65000 echomail groups can be defined).
+Different functions throughout the echomail system will eventually have "Echo ACS" strings which work just like the user ACS strings that we're familiar with.  For example, you might have "Hatch File EACS" in a file base where you could say that you wanted only echomail nodes within a particular group to be able to hatch files, or a particular security level or access flag(s), or even by static echomail node ID.  For example:
+     Hatch File EACS: g2|s255|fH|u10
+The above would say that any echomail node that is a member of Echomail group 2, OR any node that has a security level of 255 OR any Echomail node that has flag H can hatch files to that file base.  The Echomail node with the ID of #10 can also hatch.
+This is a very powerful system for managing an Echomail network, and EACS strings will be added to various functions in the future as seen fit.
 ==== Page 3 of 6 - Groups ====
@@ Line 272: / Line 294: @@
-Placeholder text - this feature under development 1.12 A38
+Define which EchoMail groups this EchoMail node is a member of.
 ==== Page 4 of 6 - BinkP====