@DustinB3403 said in The Fundamental Flaw in Not Listening to the Boss:

You're paid to do as they tell you, not to question them.

This statement was the one I disagreed with

@DustinB3403 said in The Fundamental Flaw in Not Listening to the Boss:

@Obsolesce said in The Fundamental Flaw in Not Listening to the Boss:

@scottalanmiller said in The Fundamental Flaw in Not Listening to the Boss:

At which point, when do we listen and when do we ignore?

You don't, but IMO you inform/educate them of your expert opinion, then after, you do as told.

Exactly, you can say "Boss, giving everyone access to the server is a bad idea. We can go about this other ways if you'd like that would result in what you likely need, can we meet and discuss?"

If they say, "no, do as I said." you've done your job to offer a reasonable solution, so do as they said and open up the server.

I think that would be interpreted as questioning of the reasoning behind the action. If I discuss it with them and they still decide it then yeah, I'm going to do it. I'm also going to document everything including e-mails etc to cover myself as I always do.

@DustinB3403 So you're boss says give access to our file server to all users. It has very sensitive data on it. You just do it?

@DustinB3403 said in The Fundamental Flaw in Not Listening to the Boss:

You're paid to do as they tell you, not to question them.

That depends on who your boss is. They are paying you for your expertise. Anyone can make a request. It's our job to interpret their needs and to do it in the best way possible. Sometimes there are considerations a non-technical user won't think about. That requires you to ask questions and help them understand how they can achieve what they actually want to do.

@scottalanmiller said in The Fundamental Flaw in Not Listening to the Boss:

One of the core problems with using the "end user technique" with a boss is that when it is an end user, they are powerless to do anything about it. Management dictated what happened to them, not IT.

When IT does this to their own boss, they are at fault, there is no management chain protection. If, in an odd case, this behaviour is demanded you are at an impasse - any action you take puts you at fault, there are conflicting requirements.

Yeah but there is a time where blindly following policy doesn't make sense either. can't ever account for everything you will encounter. It's a balance.

@scottalanmiller yeah I have to make sense of what someone else did. Won't be doing it in the future

Going through the process of learning bash scripting in general, but also specifically in regards to database manipulation. Any resources you guys have would be greatly appreciated

@stacksofplates Hey are you doing any database management with Ansible? exporting/importing tables, etc

Anyone know if there is a way to remove revision entries on bookstack exports? I don't want links inside of documentation I could give to the outside

@DustinB3403

@IRJ said in Locating a script that you don't know the name of in Linux:

This thread really got shit on .....

@IRJ At this point it's a miracle I'm not into scatplay

@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.

@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 f for future reference. You could then pipe that to grep for keywords.

Didn't know this. Thanks

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.

@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

@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

@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:

@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.

@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?

@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:

It could end in .py or any other extension.

Or very likely, no extension at all. Most of mine don't have one.

I create my own extensions for labeling purposes