• 0 Posts
  • 24 Comments
Joined 5 years ago
cake
Cake day: June 28th, 2020

help-circle

  • It’s nice that this exists, but even for this I’d prefer to use an open source tool.

    And it of course helps with migration only if the old HS is still online…

    I think most practically this migration function would be built inside some Matrix client (one that would support more than one server to start with), but I suppose a standalone tool would be a decent solution as well.


  • Wish the homeserver portability would be worked on more. The ability to change homeserver would really allow people to more easily move on from matrix.org.

    Myself included ;).

    Optimally it would even allow the switch “after the fact”, so after your original homeserver is down, assuming your client has a local copy of the server-side secret storage. It would need to be based on some cryptographic identity then, I suppose.



  • I’m also in a one-party consent country, and I’ve found it sometimes useful to get back to some calls just to find out some details, such as agreed date/time or some detail of a discussion I had with my mother. I would enjoy an automatic text translation to be stored alongside them.

    I miss the feature now that I have Pixel 8.

    I used syncthing to sync them to PC. Size-wise I have so few phone calls (work meetings excluded, which they are as they are over Slack/Teams) that all of them will fit most any modern phone easily.













  • At the end of the log you find:

    822413 connect(4, {sa_family=AF_UNIX, sun_path="/run/user/1000/gcr/ssh"}, 110) = 0
    ...
    822413 read(4, 
    

    meaning it’s trying to interact with the ssh-agent, but it (finally) doesn’t give a response.

    Use the lsof command to figure out which program is providing the agent service and try to resolve issue that way. If it’s not the OpenSSH ssh-agent, then maybe you can disable its ssh-agent functionality and use real ssh-agent in its place…

    My wild guess is that the program might be trying to interactively verify the use of the key from you, but it is not succeeding in doing that for some reason.


  • As mentioned, -v (or -vv) helps to analyze the situation.

    My theory is that you already have something providing ssh agent service, but that process is somehow stuck, and when ssh tries to connect it, it doesn’t respond to the connect, or it accepts the connection but doesn’t actually interact with ssh. Quite possibly ssh doesn’t have a timeout for interacting with ssh-agent.

    Using eval $(ssh-agent -s) starts a new ssh agent and replaces the environment variables in question with the new ones, therefore avoiding the use of the stuck process.

    If this is the actual problem here, then before running the eval, echo $SSH_AUTH_SOCK would show the path of the existing ssh agent socket. If this is the case, then you can use lsof $SSH_AUTH_SOCK to see what that process is. Quite possibly it’s provided by gnome-keyring-daemon if you’re running Gnome. As to why that process would not be working I don’t have ideas.

    Another way to analyze the problem is strace -o logfile -f ssh .. and then check out what is at the end of the logfile. If the theory applies, then it would likely be a connect call for the ssh-agent.