pijul_org / pijul

#72 Push failure

Opened by lykahb, on May 5, 2017
lykahb commented on May 5, 2017

After setting up a project locally and on nest I ran into this error This can be caused by the ssh config, I've never been able to push to Nest. If this is the case, the error message could be improved.

helloworld$ pijul --version
pijul 0.5.5

helloworld$ pijul init

helloworld$ pijul add Cargo.toml src/*

helloworld$ pijul record -a -A "Boris Lykah" -m "Initial commit"
Recorded patch AeBhXoKF4A9xkKaSztEzGp-_4uI38C6mL_HTyH9XR3H0jTgWrJRE0w5YsMrd9WDiM71tccWrH8EYbcn6h_0Kf7M

helloworld$ RUST_BACKTRACE=1 pijul push lykahb@nest.pijul.com:helloworld
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: IO(Error { repr: Os { code: 2, message: "No such file or directory" } })', src/libcore/result.rs:859
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: tokio_core::reactor::Core::run
   1: pijul::commands::remote::Remote::session
   2: pijul::main
pmeunier commented on May 9, 2017

I would bet on a problem with your SSH keys. SSH keys are currently possibly the weakest point of Pijul.

What platform are you running? What type of key are you using?

lykahb commented on May 9, 2017

MacOS. I've created a key for nest following the nest instructions. It's a throwaway, so I'll publish both public and private keys.




ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIP+E+AiRLmPaoWqxU8nGiqdk0Rs5BEErYtFAO4JkY5JM borisl@Borisl-MBP-OT.local

pmeunier commented on May 19, 2017

Alright, I'm currently publishing a new version of Pijul (0.5.11) supporting custom paths for public keys. Pijul now supports both Ed25519 and RSA keys, both unencrypted (i.e. no password).

To configure it for a repository, edit the file named .pijul/meta.toml, at the root of your repository. Mine for Pijul looks like:

authors = [ "Pierre-√Čtienne Meunier <pe@pijul.org>" ]

address = "pijul_org@nest.pijul.com:pijul"
secret_key = "/home/pe/.ssh/id_rsa"
lthms commented on June 5, 2017

I believe it has been fixed.