From c36b915435a5bba154c61dc71394c30e4529e920 Mon Sep 17 00:00:00 2001 From: Richard Hartmann Date: Mon, 15 Apr 2013 08:53:52 +0200 Subject: [PATCH] Typo --- doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn b/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn index 7a528573ba..01b8195b69 100644 --- a/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn +++ b/doc/design/assistant/blog/day_237__gnome-keyring_craziness.mdwn @@ -14,7 +14,7 @@ the source). If you use gnome-keyring and have set up a repository on a remote server with the assistant, I'd recommend moving the keys it set up and editing `~/.ssh/config` to point to their new location. -gnome-keyring is not the only peice of software that has a bad +gnome-keyring is not the only piece of software that has a bad interaction with git-annex. I've been working on a bug that makes git-annex fail to authenticate to ejabberd. ejabberd 2.1.10 got support for SCRAM-SHA-1, but its code violates the RFC, and chokes on an address