[BUG] Client Server Storage of Keys

Open InitRoot opened this issue 5 years ago • 3 comments

Issue Template

Context

I've moved from the default compiled ST packages to the source code. On my teamserver it runs without any issues, I deleted the previous .ST folder in home so that it overwrites the keys.

On my client I'm trying to connect, however, the teamserver is kicking me off and getting connection refused. I think it might be because of cached keys? Searched my home folder but couldn't find anything. Anything else I can try?

SILENTTRINITY Version: latest on source
OS running the Client: Arch Linux for client and Ubuntu for Teamserver
Python Version Running the Client: Python 3.8 on both

Expected Behavior

Was hoping for the connection to work.

Feb 21 '20 07:02 InitRoot

@InitRoot sounds like the client isn't registered anymore because you deleted the ~/.ST folder. Try using the register command from the sessions context menu and see if that works

Feb 21 '20 19:02 byt3bl33d3r

I completely redownloaded the client and server and tried to do a new setup. Still getting connection reset by peer. Can only think its something on my client (server completely recreated server), but no idea what else to delete.

Mar 06 '20 09:03 InitRoot

The session won’t get registered by redownloading. You’ll need to use the “register” command to register the session ID if you’re trying to use previously generated stagers.

Mar 06 '20 17:03 glides