sshrc | Bring your .bashrc, .vimrc, etc. with you when you ssh | SSH library

by cdown Shell Version: 0.6.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | sshrc Summary

sshrc is a Shell library typically used in Networking, SSH, Spring, Docker applications. sshrc has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

sshrc works just like ssh, but it also sources the ~/.sshrc on your local computer after logging in remotely. You can use this to set environment variables, define functions, and run post-login commands. It's that simple, and it won't impact other users on the server - even if they use sshrc too. This makes sshrc very useful if you share a server with multiple users and can't edit the server's ~/.bashrc without affecting them, or if you have several servers that you don't want to configure independently.

Support

Quality

Security

License

Reuse

Support

sshrc has a low active ecosystem.

It has 137 star(s) with 21 fork(s). There are 5 watchers for this library.

It had no major release in the last 6 months.

There are 3 open issues and 3 have been closed. On average issues are closed in 0 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of sshrc is 0.6.2

Quality

sshrc has no bugs reported.

Security

sshrc has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

sshrc is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sshrc releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sshrc

Get all kandi verified functions for this library.

sshrc Key Features

No Key Features are available at this moment for sshrc.

sshrc Examples and Code Snippets

No Code Snippets are available at this moment for sshrc.

Community Discussions

Trending Discussions on sshrc

How to use STDOUT inside /etc/ssh/sshrc without breaking SCP

Why is $PATH set in sshrc not used?

QUESTION

How to use STDOUT inside /etc/ssh/sshrc without breaking SCP

Asked 2021-Jan-05 at 15:51

I want to call a program when any SSH user logs in that prints a welcome message. I did this by editing the /etc/ssh/sshrc file:

...

ANSWER

Answered 2021-Jan-05 at 15:51

Use test to check $SSH_TTY (final solution in this link):

Source https://stackoverflow.com/questions/65582166

QUESTION

Why is $PATH set in sshrc not used?

Asked 2017-Mar-11 at 17:31

I am trying to setup svn over ssh on an OS X server. In order to do so, I read that I need a wrapper to set umask and - in my case - to set the repository root. A quick and dirty way to do that is to rename /usr/bin/svnserve and place a wrapper script at that location. However SIP protects that location from any changes, and I would prefer a cleaner solution anyway.

So I created a wrapper script at /usr/local/bin/svnserve and created /etc/ssh/sshrc with

...

ANSWER

Answered 2017-Mar-11 at 17:31

/etc/sshrc does not run in the same shell instance with the remotely-issued command, so the PATH update does not persist through.

Some of the available options:

You can set AcceptEnv PATH on the server to configure it to accept a PATH sent by the remote system, and SendEnv PATH on the client (in ~/.ssh/config, or as an argument to ssh passed with -o, or in /etc/ssh/ssh_config).
In /etc/ssh/sshd_config on the server, you can set the option PermitUserEnvironment to yes; with that done, the variable and value can be added to ~/.ssh/environment in the individual user's account on the server.
You can use ForceCommand to override the remotely requested command, either with something like /usr/bin/env PATH=/usr/local/bin:/usr/bin:/bin svnserve or simply /usr/local/bin/svnserve

Source https://stackoverflow.com/questions/42725326

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sshrc

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: