| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| config:sbbsecho.ini [2019/10/05 14:01] – Add some missing keys and default values digital man | config:sbbsecho.ini [2019/12/11 13:40] – [Node Sections] document the BinkpTLS option digital man |
|---|
| | ''BinkpAllowPlainText'' | ''true'' | Allow plain-text (unencrypted) communication with this linked node | | | ''BinkpAllowPlainText'' | ''true'' | Allow plain-text (unencrypted) communication with this linked node | |
| | ''BinkpSourceAddress'' | | Use an alternative FTN address as the source address when communicating with this node via BinkP | | | ''BinkpSourceAddress'' | | Use an alternative FTN address as the source address when communicating with this node via BinkP | |
| | | ''BinkpTLS'' | ''false''| Use implicit TLS for outbound encrypted connections with this linked node | |
| |
| **NOTE:** | **NOTE:** |
| |
| Also note: authentication is performed by the //answering// BinkP node (server/service), so while one security level may work okay for outgoing connections to a linked-node, its possible that there could be problems (incompatibilities) with incoming connections from that same linked-node. It's a good idea to test both incoming and outgoing connections with a linked-node before increasing the BinkP session security level. | Also note: authentication is performed by the //answering// BinkP node (server/service), so while one security level may work okay for outgoing connections to a linked-node, its possible that there could be problems (incompatibilities) with incoming connections from that same linked-node. It's a good idea to test both incoming and outgoing connections with a linked-node before increasing the BinkP session security level. |
| | |
| |
| ==== Domain Sections ==== | ==== Domain Sections ==== |
