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

[BUG] Client Server Storage of Keys #142

Open
InitRoot opened this issue Feb 21, 2020 · 3 comments
Open

[BUG] Client Server Storage of Keys #142

InitRoot opened this issue Feb 21, 2020 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@InitRoot
Copy link

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.

@InitRoot InitRoot added the bug Something isn't working label Feb 21, 2020
@byt3bl33d3r
Copy link
Owner

@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

@InitRoot
Copy link
Author

InitRoot commented Mar 6, 2020

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.

@glides
Copy link
Contributor

glides commented Mar 6, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants