Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proper Crypto for remote connections #52

Closed
Nukesor opened this issue Dec 17, 2019 · 2 comments · Fixed by #154
Closed

Proper Crypto for remote connections #52

Nukesor opened this issue Dec 17, 2019 · 2 comments · Fixed by #154
Assignees

Comments

@Nukesor
Copy link
Owner

Nukesor commented Dec 17, 2019

For now, pueue only supports tcp connections via localhost.

async-tls looks quite promising.
However, we need a way to create new server and client certificates, if they're missing.
I'm still looking for a nice way to do this inside of pueue. I don't want to rely on external (system-specific) libraries and binaries.

@Nukesor Nukesor added this to the v1.0.0 milestone Jan 30, 2020
@Nukesor Nukesor added t: Feature A new feature that needs implementation and removed enhancement f: Help wanted labels Feb 2, 2020
@Nukesor Nukesor removed this from the v1.0.0 milestone May 11, 2020
@Nukesor Nukesor removed the t: Feature A new feature that needs implementation label May 11, 2020
@Nukesor Nukesor self-assigned this Nov 13, 2020
@quebin31
Copy link
Contributor

Remote connections shouldn't be handled with ssh pair keys?

@Nukesor
Copy link
Owner Author

Nukesor commented Nov 26, 2020

Well, one can use SSH tunnels/port-forwarding for now in combination with Pueue.
However, this is a little cumbersome. Integrating tools with the SSH protocol also tends to be quite annoying.

Simple TLS crypto with a proper Authentication via Client-Certificates seems like a good mix between security and convenience.

This was referenced Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants