[tickets] [opensaf:tickets] #2613 dtm: Protect against inter-cluster communication
- **Milestone**: 5.19.01 --> future --- ** [tickets:#2613] dtm: Protect against inter-cluster communication** **Status:** unassigned **Milestone:** future **Created:** Thu Oct 05, 2017 04:07 PM UTC by Anders Widell **Last Updated:** Wed Jan 09, 2019 09:23 PM UTC **Owner:** nobody With the unicast support, there is a possibility that nodes belonging to two separate clusters will connect with each other. We can add protection against this by including the DNS domain name in the node discovery message, and reply with a NACK to the sender if the domain names do not match. When the sender receives the NACK message, it will remove that IP address from its list of peers. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2613 dtm: Protect against inter-cluster communication
- **Milestone**: 5.18.09 --> 5.18.12 --- ** [tickets:#2613] dtm: Protect against inter-cluster communication** **Status:** unassigned **Milestone:** 5.18.12 **Created:** Thu Oct 05, 2017 04:07 PM UTC by Anders Widell **Last Updated:** Thu Aug 30, 2018 12:45 PM UTC **Owner:** nobody With the unicast support, there is a possibility that nodes belonging to two separate clusters will connect with each other. We can add protection against this by including the DNS domain name in the node discovery message, and reply with a NACK to the sender if the domain names do not match. When the sender receives the NACK message, it will remove that IP address from its list of peers. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2613 dtm: Protect against inter-cluster communication
--- ** [tickets:#2613] dtm: Protect against inter-cluster communication** **Status:** unassigned **Milestone:** 5.17.10 **Created:** Thu Oct 05, 2017 04:07 PM UTC by Anders Widell **Last Updated:** Thu Oct 05, 2017 04:07 PM UTC **Owner:** nobody With the unicast support, there is a possibility that nodes belonging to two separate clusters will connect with each other. We can add protection against this by including the DNS domain name in the node discovery message, and reply with a NACK to the sender if the domain names do not match. When the sender receives the NACK message, it will remove that IP address from its list of peers. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
