-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
Pass does not support EtM MACs #624
Comments
Add the following config to make passforios work temporarily on nixos
IMO, EtM is better than the original ones, so please support it. |
Yes, the Git provider did this for me, but ultimately they want to get rid of them sooner or later. So it would be nice if passforios could also move in that direction and try to support EtM macs. |
@mssun My repository provider removed the original ones again. So I can not sync my passwords again. Is it possible to think about supporting EtM MACs soon? |
I audited the ssh client used by passforios using sshaudit.com and got a score of F- with the following breakdown: Seems like the app needs some updates. I'll defer to others with more knowledge as to whether this level of security is a concern. EDIT: I discovered in my instance that I had previously "hardened" the sshd config to only include the strongest MACs, which excluded all of passforios's MACs. I fixed it by adding back a couple of the adequate/sufficient MACs in the config. Works fine now and I still get an A+ on ssh-audit.com. This is a fantastic app, so hopefully some tweaks/updating will be made in due course. Thank you to the maintainers!! |
I'm using passforios with a provider running a Gitea based on NixOS. Recently NixOS decided to kick out non-EtM MACs for security reasons.
Unfortunately passforios seem to not support EtM at the moment. So I can't sync my repository atm.
The server logs say this, when I try to sync:
Here is the change they made: NixOS/nixpkgs@537d611
And some reference why they did this:
I'm no Swift developer, but maybe it's easy to fix, by updating a library. If it comes from iOS of cause, then you can't do anything. In that case I will ask for a more compatible selection of MAC algorithms.
Thanks for your time.
The text was updated successfully, but these errors were encountered: