Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

ReBabel is inherently insecure, in multiple ways. one of which is the Absence of any encryption! #4

Open
KeyboardInterrupt opened this issue Dec 21, 2021 · 1 comment
Labels
ReBabel ReBabel Project related!

Comments

@KeyboardInterrupt
Copy link
Member


pushfoo:
The protocol doesn't matter as long as we pipe the netbabel connection through it
ssh came to mind because it's good enough for proxying connections to production servers, and i know there are python libs for working with it
in userspace with no admin rights, too iirc
on windows


Ideas:

  • plink (putty)
  • (py)stunnel
@KeyboardInterrupt KeyboardInterrupt added the ReBabel ReBabel Project related! label Dec 21, 2021
@ligfx
Copy link

ligfx commented Dec 21, 2021

One idea I had is it would be cool to support both NetBabel and NetBabel/TLS on the same port. That way the original clients could still connect, and any updated clients / shims / whatever could use encryption without having to change the configuration (or server names/ports returned from the server, in server message type 0x0a Login Response)

E.g. https://dgraph.io/blog/post/cmux/ explains how this can be done

@KeyboardInterrupt KeyboardInterrupt changed the title **ReBabel is inherently insecure, in multiple ways. one of which is the Absence of any encryption!** ReBabel is inherently insecure, in multiple ways. one of which is the Absence of any encryption! Dec 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ReBabel ReBabel Project related!
Projects
None yet
Development

No branches or pull requests

2 participants