updatenotification module cause excessive spam in pm2 error logs

Platform: RPi3
Node Version: 9.8.0
MagicMirror Version: 2.2.2

Description:
updatenotification module is throwing a bunch of SSH related spam into the pm2 error logs.

ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I would guess this happens when a modules has a .git file, but is not connected to an accessible repo.

[E3V3A]

That is not entirely correct. I’m also using SSH all the time as well, and can do any non-pushing operation without needing credentials. MM should not need any credentials to check for updates. Anything else is a security weakness…even if it doesn’t matter that much for us. At the end of the day, I guess one step less for users to have to deal with is better for everyone. (And correct ./.ssh/config is not that easy for beginners.

Regardless of what ideology we use, for authentication, the notification module spams the log with useless and cryptic info that nobody can resolve without reading this issue thread.

[MichMich]

When you use SSH access, MM does not need any credentials. Git does this for you, using your SSH key.

I agree that the error message is somewhat cryptic, but that’s something to solved in the simple-git nom module. Not in MagicMirror.

The issue is caused by a Raspberry configuration, not by a bug in MagicMirror², therefor I’m closing this issue for now.