Despite some early back-and-forth with the author in the comments, I'm pretty sure he meant chmod, not chown. He writes, "... is now completely public", which would only happen with chmod, not wtih chown.

Source Link

edit approved Jun 13, 2024 at 5:59

Jonathan Gilbert

103
4

I have created a really really short life temporary directory that I wanted to share between some users for a few hours : /some/path/tmp

Unfortunately I have launched sudo chownchmod 777 -R /tmp instead of sudo chownchmod 777 -R tmp, so my /tmp file is now completely public.

Is it a security concern now that it is completely set to public? Should I change it back to more secure settings? What are the correct permissions for /tmp?

I have created a really really short life temporary directory that I wanted to share between some users for a few hours : /some/path/tmp

Unfortunately I have launched sudo chown 777 -R /tmp instead of sudo chown 777 -R tmp, so my /tmp file is now completely public.

Is it a security concern now that it is completely set to public? Should I change it back to more secure settings? What are the correct permissions for /tmp?

I have created a really really short life temporary directory that I wanted to share between some users for a few hours : /some/path/tmp

Unfortunately I have launched sudo chmod 777 -R /tmp instead of sudo chmod 777 -R tmp, so my /tmp file is now completely public.

Is it a security concern now that it is completely set to public? Should I change it back to more secure settings? What are the correct permissions for /tmp?

removed blah blah

Source Link

edited Mar 9, 2020 at 9:41

Stephane Rolland

4.4k
7
41
50

I have abused sudo.

I have created a really really short life temporary directory that I wanted to share between some users for a few hours... and I named this directory : /some/path/tmp

Unfortunately I have launched sudo chown 777 -R /tmp instead of sudo chown 777 -R tmp, so my /tmp file is now completely public.

I use the common /tmp pretty often (every day, almost every hour) personally for short life files, scripts, lots of scripts.

Is it a security concern now that it is completely set to public? Should I change it back to more secure settings, or like common default settings for a Debian or Ubuntu distro - (I don't know which they were)? What are the correct permissions for /tmp?

I have abused sudo.

I have created a really really short life temporary directory that I wanted to share between some users for a few hours... and I named this directory /some/path/tmp

Unfortunately I have launched sudo chown 777 -R /tmp instead of sudo chown 777 -R tmp, so my /tmp file is now completely public.

I use the common /tmp pretty often (every day, almost every hour) personally for short life files, scripts, lots of scripts.

Is it a security concern now that it is completely set to public? Should I change it back to more secure settings, or like common default settings for a Debian or Ubuntu distro - (I don't know which they were)? What are the correct permissions for /tmp?

I have created a really really short life temporary directory that I wanted to share between some users for a few hours : /some/path/tmp

Unfortunately I have launched sudo chown 777 -R /tmp instead of sudo chown 777 -R tmp, so my /tmp file is now completely public.

Is it a security concern now that it is completely set to public? Should I change it back to more secure settings? What are the correct permissions for /tmp?

"common rights" --> "correct permissions", "breach" --> "concern" minor other modifications and formatting.

Source Link

edited Apr 21, 2018 at 9:33

Kusalananda ♦

355.8k
42
735
1.1k

What are common rightscorrect permissions for /tmp ? I unintentionally set it all public recursively

I have abused sudo.

I have created a really really short life temporary directory that I wanted to share between some users for a few hours... and I named this directory /some/path/tmp

Unfortunately I have launched sudo chown 777 -R /tmp instead of sudo chown 777 -R tmp

, so my /tmp file is now completely public.

I use the common /tmp pretty often (every day, almost every hour) personally for short life files, scripts, lots of scripts.

Is it a security breachconcern now that it is completely set to public? Should I change it back to more secure settings, or like common default settings for a Debian /or Ubuntu distro - (I don't know which they were)? What are the common right settingscorrect permissions for /tmp?

What are common rights for /tmp ? I unintentionally set it all public recursively

I have abused sudo.

I have created a really really short life temporary directory that I wanted to share between some users for a few hours... and I named this directory /some/path/tmp

Unfortunately I have launched sudo chown 777 -R /tmp instead of sudo chown 777 -R tmp

so my /tmp file is now completely public.

I use the common /tmp pretty often (every day, almost every hour) personally for short life files, scripts, lots of scripts.

Is it a security breach now that it is completely set to public? Should I change it back to more secure settings, or like common default settings for a Debian / Ubuntu distro - (I don't know which they were)? What are the common right settings for /tmp?

What are correct permissions for /tmp ? I unintentionally set it all public recursively

I have abused sudo.

I have created a really really short life temporary directory that I wanted to share between some users for a few hours... and I named this directory /some/path/tmp

Unfortunately I have launched sudo chown 777 -R /tmp instead of sudo chown 777 -R tmp, so my /tmp file is now completely public.

I use the common /tmp pretty often (every day, almost every hour) personally for short life files, scripts, lots of scripts.

Is it a security concern now that it is completely set to public? Should I change it back to more secure settings, or like common default settings for a Debian or Ubuntu distro - (I don't know which they were)? What are the correct permissions for /tmp?