Set APC correctly for community updates, reject routes for non-APC comms
authorJennifer Richards <jennifer@painless-security.com>
Mon, 30 Apr 2018 17:07:46 +0000 (13:07 -0400)
committerJennifer Richards <jennifer@painless-security.com>
Mon, 30 Apr 2018 17:07:46 +0000 (13:07 -0400)
commit2efa039c6aaf0b5a82912a8ab1ff0403b0b0b907
tree78b0649861b69fe8ba515c01b73dc5c595c936e3
parent74efd266be8e0672050401a890716cc089a2d609
Set APC correctly for community updates, reject routes for non-APC comms

When an APC community update is received, the "apcs" list is empty. The
APC for any realms described by that update should be the APC community
itself.

Also, the trust router previously accepted any realm/community pairs for
routing. That should have been APC communities only.

Finally, this also prevents configuring multiple communities with the
same ID.
common/tr_comm.c
common/tr_config_comms.c
include/tr_comm.h
trp/trps.c