Locating a script that you don't know the name of in Linux
-
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@coliver No unfortunately.
Are there additional users on this system? If so you might need to login as them and check the history for each of them.
The problem is that I can't. They are local accounts and there was no transfer of information. No one knows the passwords. Can't reach out to these people as they left on bad terms apparently.
Very inconvenient
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
How do you do into Windows as another user without their password? or resetting their password to something you know?
net user name password
Doesn't that just offer you the ability to change the password?
No that changes the password. But you'd only ever do this if you HAD to login as SAID user. Otherwise you login as the admin and just grant yourself permissions to the user profile and files.
In this case to access the history you'd need to correct
-
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@coliver No unfortunately.
Are there additional users on this system? If so you might need to login as them and check the history for each of them.
The problem is that I can't. They are local accounts and there was no transfer of information. No one knows the passwords. Can't reach out to these people as they left on bad terms apparently.
Very inconvenient
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
I just don't know how this was setup or what it is doing. If I change the pw there is no chance that I could break something due to it being used like a service account for scripts?
Even if it was a service, it would run with the new password just as well. If it's setup to use the user password in some config, you should be able to see that pretty easily.
Yeah that should be the case. Just kind of afraid because I know nothing about the host.
So take a backup before you touch things.
Yeah I am
-
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
What goes for Windows too?
that you can
a) log in as a user without knowing the password
b) rest the user's password?obviously we know that we as admins can do 'b'... but I read Scott's comment to say he's talking about 'a'
-
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
What goes for Windows too?
that you can
a) log in as a user without knowing the password
b) rest the user's password?obviously we know that we as admins can do 'b'... but I read Scott's comment to say he's talking about 'a'
He's not
-
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
What goes for Windows too?
that you can
a) log in as a user without knowing the password
b) rest the user's password?obviously we know that we as admins can do 'b'... but I read Scott's comment to say he's talking about 'a'
Yes, you can change a user password on Windows for local user accounts from the control panel or
net userand then login as them. If you had AD you would change it there and then login as said user with the password you created. -
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@coliver No unfortunately.
Are there additional users on this system? If so you might need to login as them and check the history for each of them.
The problem is that I can't. They are local accounts and there was no transfer of information. No one knows the passwords. Can't reach out to these people as they left on bad terms apparently.
Very inconvenient
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
How do you do into Windows as another user without their password? or resetting their password to something you know?
net user name password
Doesn't that just offer you the ability to change the password?
Yes, in Windows you reset. In Linux you have multi-user from the command line.
-
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@coliver No unfortunately.
Are there additional users on this system? If so you might need to login as them and check the history for each of them.
The problem is that I can't. They are local accounts and there was no transfer of information. No one knows the passwords. Can't reach out to these people as they left on bad terms apparently.
Very inconvenient
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
How do you do into Windows as another user without their password? or resetting their password to something you know?
net user name password
Doesn't that just offer you the ability to change the password?
No that changes the password. But you'd only ever do this if you HAD to login as SAID user. Otherwise you login as the admin and just grant yourself permissions to the user profile and files.
In this case to access the history you'd need to correct
You can access the history without logging in as the user. Root can access the text files that hold the history.
-
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
What goes for Windows too?
that you can
a) log in as a user without knowing the password
b) rest the user's password?obviously we know that we as admins can do 'b'... but I read Scott's comment to say he's talking about 'a'
He's not
Yeah, OK I see that now - he's simply saying - there's never a need to know a user's password.
of course reason is - because you can reset it.
But as mentioned by @wirestyle22 - doing that can break things.. like on Windows, if the user is using Bitlocker to encrypt things.. the key will be lost.
-
@Dashrender said in Locating a script that you don't know the name of in Linux:
But as mentioned by @wirestyle22 - doing that can break things.. like on Windows, if the user is using Bitlocker to encrypt things.. the key will be lost.
If a user doesn't exist, and is needed, it's already broken and they need to find out.
-
I found them randomly. Now I have to figure out how to update them once I figure out what needs to be taking place. Not strong with scripting but that will need to change.
-
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
I found them randomly. Now I have to figure out how to update them once I figure out what needs to be taking place. Not strong with scripting but that will need to change.
Then post the script, no shame in asking for help.
-
You can always do a
find /home -executable -type ffor future reference. You could then pipe that to grep for keywords. -
@stacksofplates said in Locating a script that you don't know the name of in Linux:
You can always do a
find /home -executable -type ffor future reference. You could then pipe that to grep for keywords.Didn't know this. Thanks
-
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
I found them randomly. Now I have to figure out how to update them once I figure out what needs to be taking place. Not strong with scripting but that will need to change.
Then post the script, no shame in asking for help.
I will when I'm ready to in a new thread. I have some other stuff to take care of now as well.
-
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@coliver No unfortunately.
Are there additional users on this system? If so you might need to login as them and check the history for each of them.
The problem is that I can't. They are local accounts and there was no transfer of information. No one knows the passwords. Can't reach out to these people as they left on bad terms apparently.
Very inconvenient
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
How do you do into Windows as another user without their password? or resetting their password to something you know?
net user name password
Doesn't that just offer you the ability to change the password?
No that changes the password. But you'd only ever do this if you HAD to login as SAID user. Otherwise you login as the admin and just grant yourself permissions to the user profile and files.
In this case to access the history you'd need to correct
No you do not need the user password ever.
Stop listening to @DustinB3403 as he is just spewing randomly.
@scottalanmiller already told you what to do.
-
@JaredBusch said in Locating a script that you don't know the name of in Linux:
Stop listening to @DustinB3403 as he is just spewing randomly.
I never said he needed the user password, I said he could change the user password if he wanted to login as that user and didn't know what it was.
-
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@DustinB3403 said in Locating a script that you don't know the name of in Linux:
@wirestyle22 said in Locating a script that you don't know the name of in Linux:
@coliver No unfortunately.
Are there additional users on this system? If so you might need to login as them and check the history for each of them.
The problem is that I can't. They are local accounts and there was no transfer of information. No one knows the passwords. Can't reach out to these people as they left on bad terms apparently.
Very inconvenient
So someone left / was termed?
su root
sudo passwd [login] [new pass]Even easier...
sudo -i su username
Right there. There was no reason to do shit randomly.
-
@Dashrender said in Locating a script that you don't know the name of in Linux:
@scottalanmiller said in Locating a script that you don't know the name of in Linux:
The admin can just reset passwords or log in as people. There is never a need to know the local user account passwords (and that goes for Windows, too.)
What goes for Windows too?
that you can
a) log in as a user without knowing the password
b) rest the user's password?obviously we know that we as admins can do 'b'... but I read Scott's comment to say he's talking about 'a'
Oh FFS, stop cluttering up threads randomly. The fucking platform has a reply as topic button. Use it.
You little side rant about windows was nothing but confusing in a thread about fucking Linux.
-
This thread really got shit on .....
The proper thing to do is to use your privilege account to search for the file. You must know some keywords or something associated with this file.
As you are not familar with bash, let me clarify what @stacksofplates said.
Run this to search for "app-agent".
find /home -executable -type f | grep app-agent -
@IRJ At this point it's a miracle I'm not into scatplay
