# Does a security issue with the node cookies continue to exist nowadays?

**URL:** <https://erlangforums.com/t/does-a-security-issue-with-the-node-cookies-continue-to-exist-nowadays/4035>\
**Category:** Questions / Help\
**Tags:** security\
**Created:** [September 29, 2024, 12:53pm UTC](https://erlangforums.com/t/does-a-security-issue-with-the-node-cookies-continue-to-exist-nowadays/4035 "2024-09-29T12:53:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jhogberg](https://erlangforums.com/user_avatar/erlangforums.com/jhogberg/32/179_2.png) [@jhogberg](https://erlangforums.com/u/jhogberg)\
**Post date:** [September 30, 2024, 7:05am UTC](https://erlangforums.com/t/does-a-security-issue-with-the-node-cookies-continue-to-exist-nowadays/4035/3 "2024-09-30T07:05:06Z")

</div>

The cookie is not a security measure, it’s meant to prevent distinct clusters from crossing each other on a local and secure network. The documentation states that it’s there to prevent accidental misuse, not a deliberate attack.

We never considered this a security issue in and of itself because no one in their right mind would run the _unencrypted and unauthenticated_ Erlang distribution unsecured over the internet.

There is nothing to fix other than for people who do that, to stop doing that.

---

_[View the full topic](https://erlangforums.com/t/does-a-security-issue-with-the-node-cookies-continue-to-exist-nowadays/4035)._