We've had multiple reports of users who weren't able to run dangerzone on macOS due to errors in the .ssh/known_hosts file (in the tracker, #1420 and #1367, but we also got a few requests over email).
The error is the same everytime:
knownhosts: /Users//.ssh/known_hosts:45: illegal base64 data at input byte 140
An issue has been opened on the podman tracker about this in the past (by a separate user).
The solution is to go find the offending illegal input and remove it from the file, or directly remove the line. Removing the whole .ssh/known_hosts file would also work but has a broader impact.
I'm not sure what's causing this, but we've been having multiple occurrences of it. It might be interesting to
- try to understand the underlying cause for this ; and/or
- catch this specific class of error and have an appropriate error message for users, so they're able to fix things themselves.
We've had multiple reports of users who weren't able to run dangerzone on macOS due to errors in the
.ssh/known_hostsfile (in the tracker, #1420 and #1367, but we also got a few requests over email).The error is the same everytime:
An issue has been opened on the podman tracker about this in the past (by a separate user).
The solution is to go find the offending illegal input and remove it from the file, or directly remove the line. Removing the whole
.ssh/known_hostsfile would also work but has a broader impact.I'm not sure what's causing this, but we've been having multiple occurrences of it. It might be interesting to