config_echomail_nodes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
config_echomail_nodes [2019/03/16 17:21] – page 2 updates avon | config_echomail_nodes [2019/03/16 17:41] – 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 | 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 " | ||
+ | |||
+ | 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 other echomail node must of course have the same key configured for your node in order to decrypt the netmail when it arrives. | ||
+ | |||
+ | When routing Netmail, Mystic will intelligently re-encrypt the message between routing points when possible. | ||
=== Security Level === | === Security Level === | ||
- | Placeholder text - this feature under development 1.12 A38 | + | You can set ACS rules for this EchoMail node. Refer to discussion info in the Echomail Node Security section below. |
=== Access Flags === | === Access Flags === | ||
- | Placeholder text - this feature under development 1.12 A38 | + | You can set access flags for this EchoMail Node. Refer to discussion info in the Echomail Node Security section below. |
+ | |||
+ | === Echomail Node Security ==== | ||
+ | |||
+ | The beginnings 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 | ||
+ | |||
+ | Different functions throughout the echomail system will eventually have "Echo ACS" strings which work just like the [[access_control|user ACS strings that we're familiar with]]. | ||
+ | |||
+ | 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 ==== | ==== Page 3 of 6 - Groups ==== | ||
Line 272: | Line 294: | ||
| | ||
- | Placeholder text - this feature under development 1.12 A38 | + | Define which EchoMail groups |
==== Page 4 of 6 - BinkP==== | ==== Page 4 of 6 - BinkP==== |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon