# Pkg: private repository usage and keys

**URL:** https://discourse.julialang.org/t/pkg-private-repository-usage-and-keys/15575
**Category:** General Usage
**Tags:** pkg
**Created:** [September 27, 2018, 5:05pm UTC](https://discourse.julialang.org/t/pkg-private-repository-usage-and-keys/15575 "2018-09-27T17:05:36Z")
**Posts on this page:** 1
**Showing post:** 28

<div class="post-metadata">

### Author: ![OliverEvans96](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oliverevans96/32/4177_2.png) [@OliverEvans96](https://discourse.julialang.org/u/OliverEvans96)
#### Post date: [February 20, 2021, 3:28pm UTC](https://discourse.julialang.org/t/pkg-private-repository-usage-and-keys/15575/28 "2021-02-20T15:28:13Z")

</div>

Thanks for this @GunnarFarneback. As you point out, apparently using the PEM SSH key format works, but not the default OPENSSH format (which I was using) because (quoting you)

> `LibGit2` gets its ssh functionality from `libssh2` , which indeed is less capable of taking the `~/.ssh` configurations into account than the `ssh` command line interface used by the `git` command line interface.

But it seems like @StefanKarpinski is [working on improving this](https://discourse.julialang.org/t/pkg-fails-to-clone-with-ssh/39524/9).

Apparently the above solution involving `ssh-agent` somehow makes incompatible keys available to `libssh2` via an intermediary.

Just thought that summarizing the situation might be helpful for the next confused googler.

---

_[View the full topic](https://discourse.julialang.org/t/pkg-private-repository-usage-and-keys/15575)._