Running `link` with garble multiple times for windows fails

[chikamobina]

Running `link` with garble multiple times for windows fails

[chikamobina]

Yes, this happens after 2-4 weeks of server operation. Resolved by clearing the cache or restarting docker

[NHAS]

Thanks for this I'll see if I can replicate. Just working on re-adding the VPN (udp,tcp,icmp tunneling) back to rssh at user request :)

[NHAS]

Hmm I cant replicate this on either windows or linux with thew following flow:

catcher$ ls
No RSSH clients connected
catcher$ link --garble --name a
http://192.168.122.1:443/a
catcher$ link --garble --name b
http://192.168.122.1:443/b
catcher$ link --garble --name c
this link name is already in use
catcher$ link --garble --name d
this link name is already in use
catcher$ link --garble --name e
http://192.168.122.1:443/e
catcher$ link -r *
Removed 783fb1c2e38c4534af9ffdafd622e184
Removed c
Removed d
Removed a
Removed b
Removed e
catcher$ link --name a --garble
http://192.168.122.1:443/a
catcher$ link --name a --garble
this link name is already in use
catcher$ link --name b --garble
http://192.168.122.1:443/b
catcher$ link --name c --garble
http://192.168.122.1:443/c
catcher$ link --name d --garble
http://192.168.122.1:443/d
catcher$ link -r *
Removed a
Removed b
Removed c
Removed d
catcher$ link --name a --garble
http://192.168.122.1:443/a
catcher$ link --garble --name windows --goos windows
http://192.168.122.1:443/windows
catcher$ link --garble --name windows --goos windowslink -r *
Removed windows
Removed a
catcher$ link --garble --name windows --goos windows
http://192.168.122.1:443/windows
catcher$ link --garble --name windows --goos windows
this link name is already in use
catcher$ link -r *
Removed windows
catcher$ link --garble --name windows --goos windows
http://192.168.122.1:443/windows

[NHAS]

So may need more details around reproducing it

[chikamobina]

Then I don't know how this problem happens, but I've had it 7-8 times in all the time I've been using it. I have clean different ubuntu servers and I run rssh through docker.

[NHAS]

I take it this is very long running servers, I only let mine run for an hour or so after deleting a link and rebuilding using the same name.

Super frustrating issue to have

[chikamobina]

Hi, version 2.2.3

catcher$ link -C test --goarch amd64 --garble --shared-object --goos windows
Error: exit status 1

github.com/NHAS/reverse_ssh/cmd/client

/root/.cache/garble/tool/link: running x86_64-w64-mingw32-gcc failed: exit status 1
/usr/bin/x86_64-w64-mingw32-ld: /tmp/go-link-1426867729/go.o:(.text+0x27d7b2): undefined reference to `cwZ7KfYHOpmc.rlKNVGjp'
collect2: error: ld returned 1 exit status

exit status 2
exit status 1

[NHAS]

Right, thats super fucking annoying. Im going to do a work around that detects this issue and deletes /root/.cache

[NHAS]

Please give this a try on unstable and once you've confirmed it at least doesnt break I'll do a release

[chikamobina]

Ok

[chikamobina]

How can I install a non-stable version via Docker?

[NHAS]

docker exec -it /bin/bash <server container id>

Then do git pull, git checkout unstable, and then make

You'll need to restart the container to use the new server binary