A Passionate Techie

Generate keys with the command: ssh-keygen -t rsa Then add the public key to the authorized_keys with the command: cat .ssh/new_key.pub >> ~/.ssh/authorized_keys

You can do it without calling login shell: sudo DUMMY=dummy su <username> -c 'echo "$DUMMY"'

Look at the shell specified in /etc/passwd for the jenkins user. You can do so by running something like: grep jenkins /etc/passwd The output will look similar to this: jenking:1001:1001::/usr/local/jenkins:/bin/false The last field is the login shell of the user. Here you can see it is set to /bin/false which will immediately exit. The solution is to specify which shell to use as you described: su -s /bin/bash jenkins Or modify the login shell of the jenkins user with “usermod(8)” (executed as a root user) : usermod -s /bin/bash jenkins Then  grep jenkins /etc/passwd  should now output something like: jenkins:1001:1001::/usr/local/jenkins:/bin/bash After which.  su - jenkins  will work as you expect.

You can use  AllowUsers  /  AllowGroups  if you have only a few users/groups that are allowed to login via ssh or  DenyUsers  /  DenyGroups  if you have only a few users/groups that are  not  allowed to login. Note that this only restricts login via ssh, other ways of login (console, ftp, …) are still possible. You need to add these options to your  /etc/ssh/sshd_config  file for most ssh installations. If you have set the login shell to  /bin/false  you can use  su -s /bin/bash user  (replace  /bin/bash with the shell of your choice)

Git uses a username to associate commits with an identity. The Git username is not the same as your GitHub username. You can change the name that is associated with your Git commits using the  git config  command. The new name you set will be visible in any future commits you push to GitHub from the command line. If you’d like to keep your real name private, you can use any text as your Git username. Changing the name associated with your Git commits using  git config  will only affect future commits and will not change the name used for past commits. Setting your Git username for  every  repository on your computer Open  Git Bash . Set a Git username: $ git config --global user.name " Mona Lisa " Confirm that you have set the Git username correctly: $ git config --global user.name > Mona Lisa Setting your Git username for a single repository Open  Git Bash . Change the current working directory to the local repository whe...

Git uses a username to associate commits with an identity. The Git username is not the same as your GitHub username. You can change the name that is associated with your Git commits using the  git config  command. The new name you set will be visible in any future commits you push to GitHub from the command line. If you'd like to keep your real name private, you can use any text as your Git username. Changing the name associated with your Git commits using  git config  will only affect future commits and will not change the name used for past commits. Setting your Git username for  every  repository on your computer Open  Git Bash . Set a Git username: $ git config --global user.name " Mona Lisa " Confirm that you have set the Git username correctly: $ git config --global user.name > Mona Lisa Setting your Git username for a single repository Open  Git Bash . Change the current working directory to the local repository where you want to configure the name tha...

You can use  AllowUsers  /  AllowGroups  if you have only a few users/groups that are allowed to login via ssh or  DenyUsers  /  DenyGroups  if you have only a few users/groups that are  not  allowed to login. Note that this only restricts login via ssh, other ways of login (console, ftp, ...) are still possible. You need to add these options to your  /etc/ssh/sshd_config  file for most ssh installations. If you have set the login shell to  /bin/false  you can use  su -s /bin/bash user  (replace  /bin/bash with the shell of your choice)

Look at the shell specified in /etc/passwd for the jenkins user. You can do so by running something like: grep jenkins /etc/passwd The output will look similar to this: jenking:1001:1001::/usr/local/jenkins:/bin/false The last field is the login shell of the user. Here you can see it is set to /bin/false which will immediately exit. The solution is to specify which shell to use as you described: su -s /bin/bash jenkins Or modify the login shell of the jenkins user with "usermod(8)" (executed as a root user) : usermod -s /bin/bash jenkins Then  grep jenkins /etc/passwd  should now output something like: jenkins:1001:1001::/usr/local/jenkins:/bin/bash After which.  su - jenkins  will work as you expect.

You can do it without calling login shell: sudo DUMMY=dummy su <username> -c 'echo "$DUMMY"'  

Generate keys with the command: ssh-keygen -t rsa Then add the public key to the authorized_keys with the command: cat .ssh/new_key.pub >> ~/.ssh/authorized_keys

As interest and coverage continues to rise on the topic of Bitcoin and cryptocurrency, there is an increasing number of investors that are completely dubious to the “under-the-hood” mechanics of the technology. While a ‘complex’ understanding is typically left for the software-engineers and experts alike, a dumb-downed version can easily explain all the intricate complexities of Bitcoins; that is, without leaving much room for questions or concerns on the legitimacy of the rising cryptocurrency market. That is what this article will concentrate on. Explaining Bitcoin a bit further from the usual “ it’s a ledger… kept by everyone! ” notion. Quick recap on Bitcoin’s origin and its price history. Bitcoin was introduced back in 2007, when an individual or group of people by the pseudonym of Satoshi Nakamoto published a detailed white-paper, a proof-of-concept explanation, of a currency that had the potential to be both decentralized and self-governed. The paper is stil...

As interest and coverage continues to rise on the topic of Bitcoin and cryptocurrency, there is an increasing number of investors that are completely dubious to the “under-the-hood” mechanics of the technology. While a ‘complex’ understanding is typically left for the software-engineers and experts alike, a dumb-downed version can easily explain all the intricate complexities of Bitcoins; that is, without leaving much room for questions or concerns on the legitimacy of the rising cryptocurrency market. That is what this article will concentrate on. Explaining Bitcoin a bit further from the usual “ it’s a ledger… kept by everyone! ” notion. Quick recap on Bitcoin’s origin and its price history. Bitcoin was introduced back in 2007, when an individual or group of people by the pseudonym of Satoshi Nakamoto published a detailed white-paper, a proof-of-concept explanation, of a currency that had the potential to be both decentralized and self-governed. The paper is still officially hosted o...