forwagent | Experimental gpg agent forwarding for Windows
kandi X-RAY | forwagent Summary
kandi X-RAY | forwagent Summary
forwagent is a Python library. forwagent has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However forwagent build file is not available. You can download it from GitHub.
Forwagent allows forwarding gpg-agent sockets on Windows for use with GPG and SSH over TCP. For example, allow WSL or VMs to create signatures or SSH using keys stored on a YubiKey, without having access to the YubiKey itself. Tunneled connections use an encrypted transport, with mutual authentication of client and server. The server works on Windows, only. The client has only been tested on Ubuntu, but might work on other distros. NOTE: This project should be considered experimental, and is provided as-is. NOTE: This project was initially written in Go. The old code can be found in the git history.
Forwagent allows forwarding gpg-agent sockets on Windows for use with GPG and SSH over TCP. For example, allow WSL or VMs to create signatures or SSH using keys stored on a YubiKey, without having access to the YubiKey itself. Tunneled connections use an encrypted transport, with mutual authentication of client and server. The server works on Windows, only. The client has only been tested on Ubuntu, but might work on other distros. NOTE: This project should be considered experimental, and is provided as-is. NOTE: This project was initially written in Go. The old code can be found in the git history.
Support
Quality
Security
License
Reuse
Support
forwagent has a low active ecosystem.
It has 7 star(s) with 2 fork(s). There are 2 watchers for this library.
It had no major release in the last 6 months.
forwagent has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of forwagent is current.
Quality
forwagent has 0 bugs and 0 code smells.
Security
forwagent has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
forwagent code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
forwagent is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
forwagent releases are not available. You will need to build from source code and install.
forwagent has no build file. You will be need to create the build yourself to build the component from source.
Installation instructions, examples and code snippets are available.
It has 288 lines of code, 23 functions and 5 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi has reviewed forwagent and discovered the below as its top functions. This is intended to give you an instant insight into forwagent implemented functionality, and help decide if they suit your requirements.
- Execute the server
- Runs SSL
- Returns the argument parser
- Run the main loop
- Forward two sockets
- Get a gpg agent
- Get the SSH agent
- Returns a tuple of the names of all open sockets
- Get the directory for a GPG directory
- Ensure that gpg - agent is started
- Execute the command line interface
Get all kandi verified functions for this library.
forwagent Key Features
No Key Features are available at this moment for forwagent.
forwagent Examples and Code Snippets
No Code Snippets are available at this moment for forwagent.
Community Discussions
No Community Discussions are available at this moment for forwagent.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install forwagent
Both client and server need to have GnuPG installed, and their versions should be close to ensure compatbility of the gpg-agent protocol. You can use pip (or an alternative, like pipx) to install forwagent. The package defines two "extras" which are needed to run the server, and to initialize the configuration.
Initialize the configuration by running forwagent init. This will create a .forwagent/ directory in your users $HOME, and a self-signed certificate which will be used in the files key.pem and cert.pem. An empty trusted.pem file will be created for adding trusted client certificates. You will need to add client certificates to the trusted.pem file before the server will accept connections. If any of the files in .forwagent/ are changed, the server will need to be restarted for those changes to take effect. Run forwagent server to start the server. By default the server runs on 127.0.0.1:4711, but this can be set by providing the --interface and --port arguments when running. You'll most likely want to automate the startup of the server so that it runs each time the computer starts. See the files in doc/ for suggestions on how to do this.
The users private key should be usable from Windows.
The gpg-connect-agent.exe executable should be in the users PATH.
The gpg-agent.conf should have enable-putty-support.
Initialize the configuration by running forwagent init. This will create a .forwagent/ directory in your users $HOME, and a self-signed certificate which will be used in the files key.pem and cert.pem. An empty trusted.pem file will be created for adding the servers certificate. Run forwagent agent to start the client. By default the client will connect to a server running on 127.0.0.1:4711, but this can be set by providing the --interface and --port arguments when running.
Initialize the configuration by running forwagent init. This will create a .forwagent/ directory in your users $HOME, and a self-signed certificate which will be used in the files key.pem and cert.pem. An empty trusted.pem file will be created for adding trusted client certificates. You will need to add client certificates to the trusted.pem file before the server will accept connections. If any of the files in .forwagent/ are changed, the server will need to be restarted for those changes to take effect. Run forwagent server to start the server. By default the server runs on 127.0.0.1:4711, but this can be set by providing the --interface and --port arguments when running. You'll most likely want to automate the startup of the server so that it runs each time the computer starts. See the files in doc/ for suggestions on how to do this.
The users private key should be usable from Windows.
The gpg-connect-agent.exe executable should be in the users PATH.
The gpg-agent.conf should have enable-putty-support.
Initialize the configuration by running forwagent init. This will create a .forwagent/ directory in your users $HOME, and a self-signed certificate which will be used in the files key.pem and cert.pem. An empty trusted.pem file will be created for adding the servers certificate. Run forwagent agent to start the client. By default the client will connect to a server running on 127.0.0.1:4711, but this can be set by providing the --interface and --port arguments when running.
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:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page