mc_ssh
SSH client wrapper for SSH with access token
Installation
- Install mc_ssh from pypi:
pip install mc_ssh - Install mc_ssh from source:
- Install prerequisites:
pip install -r requirements.txt - Build package:
./setup.py sdist - Install package:
pip install dist/mc_ssh-$version.tar.gz
- Install prerequisites:
Usage
$ mccli --help
Usage: mccli [OPTIONS] COMMAND [ARGS]...
ssh client wrapper with OIDC-based authentication
Options:
--mc-endpoint URL motley_cue API endpoint, default URLs:
https://HOSTNAME, http://HOSTNAME:8080
--insecure ignore verifying the SSL certificate for
motley_cue endpoint, NOT RECOMMENDED
Access Token sources: [mutually_exclusive]
the sources for retrieving the access token,
odered by priority
--token TOKEN pass token directly, env variables are
checked in given order [env var:
ACCESS_TOKEN, OIDC, OS_ACCESS_TOKEN,
OIDC_ACCESS_TOKEN, WATTS_TOKEN,
WATTSON_TOKEN]
--oa-account SHORTNAME name of configured account in oidc-agent
[env var: OIDC_AGENT_ACCOUNT]
--iss, --issuer URL url of token issuer; configured account in
oidc-agent for this issuer will be used
[env var: OIDC_ISS, OIDC_ISSUER]
--log-level LEVEL Either CRITICAL, ERROR, WARNING, INFO or
DEBUG.
--version Show the version and exit.
--help Show this message and exit.
Commands:
info get info about service
scp secure file copy
sftp secure file transfer
ssh remote login client
You can also use the help option on each subcommand, eg:
mccli ssh --help
First, you'll need an OIDC Access Token to authenticate. You might want to check out the oidc-agent for that.
After you get the oidc-agent running, configure an account for your OP.
For example, if you generated an account named egi for the EGI AAI, you can set this in an environment variable:
export OIDC_AGENT_ACCOUNT=egi
Then, assuming that the ssh server has a motley_cue instance running on the same host at https://$SSH_SERVER or http://$SSH_SERVER:8080, you can connect to the ssh server simply by:
mccli ssh $SSH_SERVER
Or get the sshpass command that you can run instead:
mccli ssh $SSH_SERVER --dry-run
Metadata
Release files for mc-ssh 0.2.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mc_ssh-0.2.6.tar.gz | 19.5 kB | Without provenance | Details for mc_ssh-0.2.6.tar.gz |
Release files / mc_ssh-0.2.6.tar.gz
| Download URL | mc_ssh-0.2.6.tar.gz |
|---|---|
| Size | 19.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad60297e697b3d8984e4be2b356b9dc47f27ad22e297df7925ee0fdda3d93f85
|
|
BLAKE2b-256 checksum How to use checksums |
198d5c9c6653037508f9d9a8fd4bc9f760a0ee0e74ed69e8c6644befa912c1f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/57.1.0 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.9.5
|
Security for mc-ssh 0.2.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.