04-01-2019
Quote:
Originally Posted by
Shubham1182
Hello Team,
Please help me to solve my Problem,
By mistake, I give full permission to /(root) directory. by using the following command "chmod -R 777 /"
after this, the client asks for the password to login via ssh. Before that, I an able to Login without a password.
Please help me to retrieve changes.
Thank you.
You didn't just make your root directory readable, writeable, and searchable by everyone in the world; you made every file on your system readable, writeable, changeable, executable, delectable, and searchable by anyone who is able to access your system in any way shape or form.
I strongly suggest that you shut down the system as quickly as possible.
Then you can boot it up in single-user mode and try to restore your system to a stable point before you destroyed the system's self-protection capabilities by restoring everything from a recent backup dump. (You do perform regular backups, don't you?)
There is no "undo" command that can recover from you making every file on your system readable, writeable, executable, and searchable by everyone in the world!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
i am having following directory structure
Folder1
-> Folder2
-> Folder3
Folder4
Folder5
Now i am at top level and want to assign write permission to all the folder & files in it.
i am... (3 Replies)
Discussion started by: sarbjit
3 Replies
2. Shell Programming and Scripting
Hi all,
I need some help in my script...
I need to login into multiple servers from one Unix box and need to login as a superuser account and then I need to perform some actions on the server. For this, i'll use for loop to provide the server names to the script, but for every login as a... (8 Replies)
Discussion started by: raghu.iv85
8 Replies
3. Shell Programming and Scripting
Hi All,
Could any one please help me in performing the following?
We have the following folder:
/home/test/proj1
/home/test/proj2
/home/test/proj3
Users from different country places files in this folder using FTP (These users uses different flavors of FTP tools).
Our... (1 Reply)
Discussion started by: vfrg
1 Replies
4. Shell Programming and Scripting
In my script, I am creating a file ----> then writting one line (i.e. Timestamp) ----> then FTP'ing. The same script can be executed by many other users.
While other users executing this script, they couldn't Over write this one line (i.e. Timestamp)
My expectation
So I wanted to create a... (2 Replies)
Discussion started by: sbmk_design
2 Replies
5. Shell Programming and Scripting
How to execute a script with out giving x permission to the file? (7 Replies)
Discussion started by: praveen_b744
7 Replies
6. Shell Programming and Scripting
Hi Gurus,
I am new to scripting and needs your help in expect script used for telnet. I wrote a simple script as
#!/usr/bin/expect-5.43 -f
spawn telnet localhost 2233
expect "password:"
send "secret\r"
send "i data.cnbc.com\r"
send "exit\r"
expect eof
When I am trying to execute... (2 Replies)
Discussion started by: niks_yv
2 Replies
7. Shell Programming and Scripting
Hello Friends,
I know this issue has been raised many times and hence I tried every resolution provided in the forum before I posted this issue again.
My Password-less RSA authentication was working fine for quite some time. Whenever the remote server password used to change I used to re-do... (5 Replies)
Discussion started by: mehimadri
5 Replies
8. Solaris
hi guys..
how to give root permission for particular user
tel me step by step (2 Replies)
Discussion started by: coolboys
2 Replies
9. Solaris
Hi,
I have enabled the Apache webserver on my machime.
Apache root directory is /etc/apache2 and the user in which the web server is configured is webservd,I guess.
I have another user called perf.
Under perf user there is /export/home/perf/v9 directory.
I want to give the OS user of... (3 Replies)
Discussion started by: bikas89
3 Replies
10. Solaris
Hi,
Is there any chance that a file system that mounted on the server becomes read only when the space in that file system becomes full?
Regards,
Sreejith (9 Replies)
Discussion started by: Sreejith K
9 Replies
PASSWD(5) File Formats Manual PASSWD(5)
NAME
passwd - password files
DESCRIPTION
Passwd files are files consisting of newline separated records, one per user, containing ten colon (``:'') separated fields. These fields
are as follows:
name user's login name
password user's encrypted password
uid user's id
gid user's login group id
class user's general classification (unused)
change password change time
expire account expiration time
gecos general information about the user
home_dir user's home directory
shell user's login shell
The name field is the login used to access the computer account, and the uid field is the number associated with it. They should both be
unique across the system (and often across a group of systems) since they control file access.
While it is possible to have multiple entries with identical login names and/or identical user id's, it is usually a mistake to do so.
Routines that manipulate these files will often return only one of the multiple entries, and that one by random selection.
The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be
part of the name, as this tends to confuse mailers. No field may contain a colon (``:'') as this has been used historically to separate
the fields in the user database.
The password field is the encrypted form of the password. If the password field is empty, no password will be required to gain access to
the machine. This is almost invariably a mistake. Because these files contain the encrypted user passwords, they should not be readable
by anyone without appropriate privileges.
The group field is the group that the user will be placed in upon login. Since this system supports multiple groups (see groups(1)) this
field currently has little special meaning.
The class field is currently unused. In the near future it will be a key to a termcap(5) style database of user attributes.
The change field is the number in seconds, GMT, from the epoch, until the password for the account must be changed. This field may be left
empty to turn off the password aging feature.
The expire field is the number in seconds, GMT, from the epoch, until the account expires. This field may be left empty to turn off the
account aging feature.
The gecos field normally contains comma (``,'') separated subfields as follows:
name user's full name
office user's office number
wphone user's work phone number
hphone user's home phone number
This information is used by the finger(1) program.
The user's home directory is the full UNIX path name where the user will be placed on login.
The shell field is the command interpreter the user prefers. If the shell field is empty, the Bourne shell (/bin/sh) is assumed.
SEE ALSO
chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8), vipw(8) adduser(8)
BUGS
User information should (and eventually will) be stored elsewhere.
7th Edition May 8, 1989 PASSWD(5)