How can user invoke superuser command? - qnx

I created a user group and a user, when i log onto it and type su on the terminal.
I get this error su error: Password and Shadow files on different devices
How do i fix this issue?

Related

Jenkins: The config profile (user_profile) could not be found Error: Cannot perform an interactive login from a non TTY device

I'm getting the error when executing the build with Jenkins:
The config profile (user_profile) could not be found
Error: Cannot perform an interactive login from a non TTY device
But from the command line it works, does anyone have any idea what it could be? Any credentials, access level or something like that?
configure aws profile in jenkins user and after that verify permission to /var/lib/jenkins/credentials file.
it should be accessible by jenkins user.
enter image description here

Influxdb 2: Cannot sign in

I've managed to install influxdb2 and login to the web ui at localhost:8086 with the default username/pass admin/admin. But when I try to login now with the same credentials i get an error saying "Could not sign in" as shown here: Running systemctl status influxdb gives me this output: This persists after reboots and reinstalls of influxdb. Is there some way to hard reset the password or to disable the authentification?
You can reset your InfluxDB 2 administrator password by recovering a admin token if you have access to the installation filesystem.
Find influxd.bolt on the host or in the container: /var/lib/influxdb2/influxd.bolt
Search this mixed text and binary json file for strings like your known username or token.
cat /var/lib/influxdb2/influxd.bolt | strings | grep "admin's Token"
{"id":"1234567898000000",
"token":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==",
"status":"active",
"description":"admin's Token",
With an admin-privileged token, you can update the password with the Influx Command Line Interface (CLI) command influx user password. For example:
$ docker exec -it 85e4df16a429 influx user password -n admin -t xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==
? Please type your new password *********************
? Please type your new password again *********************
Your password has been successfully updated.
$
It happened the same to me, I created a user and then I forgot the password.
For those who work in Windows, go to C:\Users\YourName and delete .influxdbv2.
I forgot i created a new user, organization and bucket when first running influxdb.
I've managed to solve it by purging all the influxdb files by running dpkg --purge influxdb2 and then reinstalling.

Secret username and password on Jenkins

I am having troubles to manage secret password on Jenkins. I want that the password is not showed on the log but i tried in two ways without success:
First attempt
I tried setting up with user and pwd with Global credentials (unrestricted) like this :
and i executed :
docker run -u root -v $(pwd)/:/usr/src/app deploy npm run application -- --params.login.user=$USER --params.login.password=$PWD
but i can see in the log that the user is wrote correctly but the pwd is being written like its path:
e2e#2.2.1 e2: `protractor dist/out-tsc/e2e/cucumberconfig.js "--params.login.user=user" "--**params.login.password=/var/lib/jenkins/workspace/application/app/e2e_test**"
And in my automatic test is also by entering the full path instead of the value of the variable.
Second attempt
I tried using a secret text like this:
docker run -u root -v $(pwd)/:/usr/src/app deploy npm run application -- --params.login.user=$USER --params.login.password=$PASS
But on the console log is being displayed the password as it is.
Someone can help me?
Thank you in advance.
But on the console log is being displayed the password as it is.
is it mean in clear text?
If so - use mask password plugin to solve the issue.
i used :
set +x
docker run -u root -v $(pwd)/:/usr/src/app deploy npm run application -- -params.login.user=$USER --params.login.password=$PWD
set -x
and that worked.

How to call "mysql" with STDIN redirection from inside Rails

I am trying to use redirection to load a SQL database schema using:
system("mysql -p -h db.server.local -u admin -D some_db < schema.sql")
I expect it to prompt for a password, and it works correctly when run from IRB. However, when run via Rails' runner it fails
as if I had hit the Enter key at the password prompt. In Rails console it looks like this:
pry(main)> system("mysql -p -h db.server.local -u admin -D some_db < schema.sql")
Enter password: ERROR 1045 (28000): Access denied for user 'admin'#'mylocalpc' (using password: NO)
It did not give me a chance to enter the password. When I removed the redirection (<), it correctly prompts for a password. So it appears that somehow, when run via Rails, the STDIN redirection is disrupting the password prompt. I tried with backticks and had the same issue.
I assume that the mysql executable must be using some magic so that the STDIN redirection does not disrupt the password prompt, but it appears to be broken when the executable is launched via Rails.
Is Rails overriding System() and if so, is there some way to call the real System()?
Does anyone have other ideas of how to work around this, or what could be happening here?
The mysql executable is skipping the request for a password because in order to except stdin for the password, the command needs to be executed with TTY enabled. Ruby system command and backticks do not execute the command using a TTY enabled interface to the underlying system. There are a couple gems that allow for TTY enabled execution on the command line, I would check out the tty-command gem if you’d like to force the command prompt to ask for the password.
Though for the ideal solution that I would suggest, since you’re executing the command from within Rails, you should have access to Rails.credentials. I would store the necessary credentials (username and password) for the database within the credentials store, and use this to populate the -u and -P flag values for the mysql command. This will avoid the need to prompt for the password entirely.

PSEXEC - Elevated Command prompt

Sorry if this has been asked a hundred times, I'm sure it might have been, but my searching skills don't seem to be finding the answer to my particular question today :(
I'm trying to execute a command on a server, from a domain user account, who has all the correct rights to perform the given action. I know this because if I login to the server under the admin account and then open the command prompt using 'Run as different User', specifying the login details of the domain user account, I can perform the relevant section of the below command successfully.
However, when I try running ("c:\NaviTest\psexec.exe" "\HOSTNAME" "c:\path to\server-command.exe" "arguments") from a command prompt on their host computer I get the 'Access Denied' message back.
If I launch the command prompt as administrator and change the syntax of the command as follows (where username is the logged in user and password is their password);
"c:\NaviTest\psexec.exe" -u username -p password "\\HOSTNAME" "c:\path to\server-command.exe" "arguments"
All works.
I know from this that its not running 'server-command.exe' the command that is causing the issue, its getting the connection to server using PSEXEC which seems to be failing unless the command prompt is being run in Elevated mode.
My question (as I haven't actually asked on yet!), is can PSEXEC work from the command prompt without having to be run administratively?
I'm trying to execute this as part of a much larger script, if I can't make it work without administrative privileges its not going to work.
Found the answer to this.......
https://serverfault.com/questions/280482/how-to-use-psexec-without-admin-privileges-on-target-machine
Basically, the user account executing the PSEXEC command needs local administrative rights on the destination host.
Adam
This might cause due to prevailing issue.
psexcec will start a service(windows) in end point .
check this
Run this as admin and will proceed without issues

Resources