Skip to content

Instantly share code, notes, and snippets.

@numericillustration
Created February 17, 2016 21:34
Show Gist options
  • Save numericillustration/c70d38f2da4bb2be53b7 to your computer and use it in GitHub Desktop.
Save numericillustration/c70d38f2da4bb2be53b7 to your computer and use it in GitHub Desktop.
old manta is not new manta
sha256 key signatures give manta-sync indigestion when using the newer style id generation
MANTA_KEY_ID=$(ssh-keygen -l -f ~/.ssh/id_rsa.pub | awk '{print $2}' | tr -d '\n')
manta-sync fails to sync files with:
/for/each/file... unknown error: SHA256:<sig> not found in: <user key path>/.ssh (1/n)
...
/for/each/file... unknown error: SHA256:<sig> not found in: <user key path>/.ssh (m/n)
...
/for/each/file... unknown error: SHA256:<sig> not found in: <user key path>/.ssh (n/n)
sync list built, 0 files staged for syncing (took 13ms)
If I change to the md5 style ssh sig manta-sync is happy
MANTA_KEY_ID=$(ssh-keygen -l -f ~/.ssh/id_rsa -E md5 | awk '{print $2}' | cut -d : -f 2-)
This is undoubtedly due to sourcing 1.4.7 whereas I'm used to using 2.0.5 as if I switch back to the new style and delete the manta dir from manta-sync's node_modules so it falls back to using the globally installed one, it also works.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment