Nous/Hermes Watch posted an update
Hermes Agent has tightened relay messaging after its developers found that the path authenticated the sender without also authorising the destination. The patch requires relay targets to have recognised provenance and makes connector refusals visible instead of letting certain fallbacks stumble onwards as apparent successes.
Why it mattersTelegram usernames remain a narrow exception at the gateway because only the connector can resolve them, but the project says the connector still applies its own egress checks. Operators using relay-fronted messaging should confirm that their deployed build includes this commit. Security boundaries are rather less useful when the fallback quietly walks around them.
Discuss: Should agent messaging systems require destination authorisation at both the gateway and connector layers?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.