Package Details: kr 2.4.14-1

Git Clone URL: (read-only, click to copy)
Package Base: kr
Description: SSH using a key stored in Krypton
Upstream URL:
Licenses: custom
Conflicts: kr
Provides: kr
Submitter: kryptco
Maintainer: kryptco
Last Packager: kryptco
Votes: 7
Popularity: 0.000002
First Submitted: 2017-08-13 18:56
Last Updated: 2018-12-17 18:48

Latest Comments

1 2 3 Next › Last »

brandonrandle commented on 2019-08-12 20:31

@kryptco Is this still being maintained? I noticed that it's been flagged as out-of-date, and I'm curious as to whether future updates are planned. Thanks!

mercxry commented on 2019-04-08 12:47

@L3vi47h4N Seems like there is a temporary workaround for that,

kryptco commented on 2018-12-17 18:50

Version 2.4.14 now uses the latest version of cargo-web which should fix the openssl-related build issues. Thanks everyone for reporting!

mprom commented on 2018-11-05 08:47

Hey kryptco, I think you should add running kr uninstall to the package uninstall hook, as right now uninstalling the package as one normally uninstalls packages from the AUR (like yay -R kr) leaves SSH unusable

Pyrepenol commented on 2018-10-21 02:57

got cargo-web to install with this

env OPENSSL_INCLUDE_DIR=/usr/include/openssl-1.0 OPENSSL_LIB_DIR=/usr/lib/openssl-1.0 cargo install -f --version 0.6.10 cargo-web

unomar commented on 2018-10-17 15:14

Yeah, when I run makepkg that way I get:

error: could not find native static libraryssl, perhaps an -L flag is missing?

kryptco commented on 2018-10-16 20:08

Have you tried running makepkg with the same env command prepended as in the GitHub issue?

unomar commented on 2018-10-16 20:03

@kryptco Thanks for the link. I managed to get cargo-web 0.6.10 installed, but that only got me a little further. Running makepkg I get this error: error: failed to run custom build command for `openssl-sys v0.9.23 (<>)

It seems to be ignoring or missing the OPENSSL envvars and finding OpenSSL 1.1.1 as this error follows below: This crate is only compatible with OpenSSL 1.0.1, 1.0.2, and 1.1.0, or LibreSSL 2.5 and 2.6.0, but a different version of OpenSSL was found. The build is now aborting due to this version mismatch.

kryptco commented on 2018-10-13 19:20

@unomar thank you for reporting this. We are awaiting an upstream openssl depdendency update, but in the meantime you can workaround this issue following the instructions here:

unomar commented on 2018-10-09 18:40

I'm getting issues while attempting to build cargo-web. It appears to be related to rust-openssl & openssl 1.1.1 refereced here:

error: failed to run custom build command for `openssl v0.9.24` process didn't exit successfully: `/tmp/cargo-installq4ar12/debug/build/openssl-959868a99e49436a/build-script-build` (exit code: 101) --- stderr thread 'main' panicked at 'Unable to detect OpenSSL version', /home/<user>/.cargo/registry/src/ note: Run with `RUST_BACKTRACE=1` for a backtrace.