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
LEARN ABOUT DEBIAN
s3qllock
S3QLLOCK(1) S3QL S3QLLOCK(1)
NAME
s3qllock - Make trees on an S3QL file system immutable
SYNOPSIS
s3qllock [options] <directory>
DESCRIPTION
S3QL is a file system for online data storage. Before using S3QL, make sure to consult the full documentation (rather than just the man
pages which only briefly document the available userspace commands).
The s3qllock command makes a directory tree in an S3QL file system immutable. Immutable trees can no longer be changed in any way whatso-
ever. You can not add new files or directories and you can not change or delete existing files and directories. The only way to get rid of
an immutable tree is to use the s3qlrm command.
s3qllock can only be called by the user that mounted the file system and (if the file system was mounted with --allow-other or
--allow-root) the root user. This limitation might be removed in the future (see issue 155).
RATIONALE
Immutability is a feature designed for backups. Traditionally, backups have been made on external tape drives. Once a backup was made, the
tape drive was removed and locked somewhere in a shelf. This has the great advantage that the contents of the backup are now permanently
fixed. Nothing (short of physical destruction) can change or delete files in the backup.
In contrast, when backing up into an online storage system like S3QL, all backups are available every time the file system is mounted.
Nothing prevents a file in an old backup from being changed again later on. In the worst case, this may make your entire backup system
worthless. Imagine that your system gets infected by a nasty virus that simply deletes all files it can find -- if the virus is active
while the backup file system is mounted, the virus will destroy all your old backups as well!
Even if the possibility of a malicious virus or trojan horse is excluded, being able to change a backup after it has been made is generally
not a good idea. A common S3QL use case is to keep the file system mounted at all times and periodically create backups with rsync -a. This
allows every user to recover her files from a backup without having to call the system administrator. However, this also allows every user
to accidentally change or delete files in one of the old backups.
Making a backup immutable protects you against all these problems. Unless you happen to run into a virus that was specifically programmed
to attack S3QL file systems, backups can be neither deleted nor changed after they have been made immutable.
OPTIONS
The s3qllock command accepts the following options:
--debug
activate debugging output
--quiet
be really quiet
--version
just print program version and exit
EXIT STATUS
s3qllock returns exit code 0 if the operation succeeded and 1 if some error occurred.
SEE ALSO
The S3QL homepage is at http://code.google.com/p/s3ql/.
The full S3QL documentation should also be installed somewhere on your system, common locations are /usr/share/doc/s3ql or
/usr/local/doc/s3ql.
COPYRIGHT
2008-2011, Nikolaus Rath
1.11.1 August 27, 2014 S3QLLOCK(1)