Transition from --key to --keygen/--keyfile

Question

Transition from --key to --keygen/--keyfile

xxirs opened this issue 10 months ago · comments

Currently I have chisel setup and working well however I know --key is depreciated and will be removed in future versions. I would like to move over to using --keygen/--keyfile however I'm having trouble grasping what I need to do differently. I run chisel inside docker environments with one chisel server and two chisel clients .

Current Setup
Chisel Server

Chisel Clients

Actual keys and IPs removed from the screenshots above.

So really my only question is how do I transition away from using --key and being using --keygen/--keyfile using docker?

When I try to generate the keyfile with --keygen using docker and mounting a bind mount it still doesn't work

Deleted user · Answer 1 · Sat Oct 21 2023 21:45:34 GMT+0800 (China Standard Time)

Consider the issue closed, leaving this here in-case anyone else runs into my issue. You need to set a bind mount so --keygen has a place to store its generated key.

Above is how I fixed it for myself.

Accompanying docker run

Jaime Pillora · Answer 2 · Sun Oct 22 2023 04:13:49 GMT+0800 (China Standard Time)

-keyfile supports a “ck-…” string or a filepath string And it can be set with an env var too I think the socks example in the readme has it, but yea we need some more examples

…

On Sun, 22 Oct 2023 at 12:45 AM xxirs ***@***.***> wrote: Consider the issue closed, leaving this here in-case anyone else runs into my issue. You need to set a bind mount so --keygen has a place to store its generated key. [image: image] <https://user-images.githubusercontent.com/47906826/277111494-5a36242f-af80-44e3-a04c-1f46d0f15769.png> Above is how I fixed it for myself. — Reply to this email directly, view it on GitHub <#462 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE2X46B7XP2VYZT6IQKU7TYAPGYVAVCNFSM6AAAAAA6JRVAMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTG44TMMRWHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Deleted user · Answer 3 · Sun Oct 22 2023 06:57:25 GMT+0800 (China Standard Time)

-keyfile supports a “ck-…” string or a filepath string And it can be set with an env var too I think the socks example in the readme has it, but yea we need some more examples
…
On Sun, 22 Oct 2023 at 12:45 AM xxirs @.> wrote: Consider the issue closed, leaving this here in-case anyone else runs into my issue. You need to set a bind mount so --keygen has a place to store its generated key. [image: image] https://user-images.githubusercontent.com/47906826/277111494-5a36242f-af80-44e3-a04c-1f46d0f15769.png Above is how I fixed it for myself. — Reply to this email directly, view it on GitHub <#462 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2X46B7XP2VYZT6IQKU7TYAPGYVAVCNFSM6AAAAAA6JRVAMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTG44TMMRWHE . You are receiving this because you are subscribed to this thread.Message ID: @.>

I definitely think more docker examples would be useful. I kinda just dabbled around with what I knew about docker and it eventually worked. Another think that might help is updating the docker page with specific docker examples maybe? https://hub.docker.com/r/jpillora/chisel/