Skip to content

Conversation

@rdebath
Copy link
Contributor

@rdebath rdebath commented Jun 23, 2016

The first is to simply make the socket readable only for the user (only of any note if you're putting them into /tmp)

The second is an option to suppress the ANSI terminal assumptions specifically:

  • Running tput init instead of printf("\033[?25h");
  • Don't clear the screen when attaching to an existing session.

rdebath added 2 commits June 21, 2017 07:20
Only running user can read (or write) data.
@crigler
Copy link
Owner

crigler commented Jun 18, 2025

The umask change did not seem to do anything until I moved the umask(omask) call after the call to bind.

@domo141
Copy link

domo141 commented Jun 18, 2025

looks understandable, since bind(2) creates that socket file to the system
(maybe some systems set the umask to the socket descriptor (not yet bound anywhere)
(i wonder why I got email about this commit :)

other thing, that system() looks somewhat "heavyweight" to me...

@crigler
Copy link
Owner

crigler commented Jun 18, 2025

Yeah, I agree and only cherry-picked the umask change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants