Erlang: binary_to_atom filling up atom table space security issue
问题 I heard that an atom table can fill up in Erlang, leaving the system open for DDoS unless you increase the number of atoms that can be created. It looks like binary_to_existing_atom/2 is the solution to this. Can anyone explain exactly how binary_to_atom/2 is a security implication and how binary_to_existing_atom/2 solves this problem? 回答1: When an atom is first used it is given an internal number and put in an array in the VM. This array is allocated statically and can fill up if enough