777 means that anyone can write to the socket, potentially from anywhere, and execute the contents. Don't let that "file" be executable; 666 would work better.
For access control, I would never rely on flat-file permissions. If authentication is needed [Mir team?], it would be better to use a client or mutual authentication handshake mechanism such as employing PKI and certificates signed by a CA. After authentication completes, data encryption would not be required.
777 means that anyone can write to the socket, potentially from anywhere, and execute the contents. Don't let that "file" be executable; 666 would work better.
For access control, I would never rely on flat-file permissions. If authentication is needed [Mir team?], it would be better to use a client or mutual authentication handshake mechanism such as employing PKI and certificates signed by a CA. After authentication completes, data encryption would not be required.