config_echomail_nodes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
config_echomail_nodes [2019/03/16 17:39] – echomail secuity avon | config_echomail_nodes [2019/03/16 17:41] – echomail secuity avon | ||
---|---|---|---|
Line 257: | Line 257: | ||
=== Security Level === | === Security Level === | ||
- | You can set ACS rules for this EchoMail node. | + | You can set ACS rules for this EchoMail node. Refer to discussion info in the Echomail Node Security section below. |
=== Access Flags === | === Access Flags === | ||
- | You can set access flags for this EchoMail Node. | + | You can set access flags for this EchoMail Node. Refer to discussion info in the Echomail Node Security section below. |
=== Echomail Node Security ==== | === Echomail Node Security ==== | ||
- | The beginning | + | The beginnings |
- | 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: | + | 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]]. 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 | Hatch File EACS: g2|s255|fH|u10 |
config_echomail_nodes.txt · Last modified: 2023/01/03 01:49 by avon