MadCap Software Forums

Hi,
I was trying to connect Flare 12 project with Git repo through SSH and I am stuck on the "Certificate Specification" dialog.
I added my keys (Public and private) and clicked OK. Nothing happened and this dialog is still here (no error or something). I know that my keys are OK, since I am using them outside the Flare.
Anybody experiencing same behaviour? Or some advice how to connect?
Thanks

Hi.

Did you ever figure this out or work around it?

Or are you still stuck, months later?

Still stuck. So I started using https instead of ssh. It is still problematic, but at least it's doing something.

Hi,

We are trying to migrate our Flare projects from Subversion to Git, and we are facing the same problem with the SSH public and private keys: Flare does not accept them even if they are correctly 'labelled'.

Should you have solved your problem since your last post, could you please let me know?
We cannot consider using HTTP for the time being.

On my side, I will let you know if we find a solution in the coming days.

Kind regards,
Anne Delbruyère

Nope. Still using HTTPS...

I have just fought this battle in Flare2017r3 and finally figured out how to do this by sheer trial & error.
As I have wasted a lot of time figuring this out, i'm hoping to save other people from having to do the same by posting this here.

The public key must have a specific format of "[type] [base64key]"
So you can edit the key exported from, for example PuttyGen, in notepad to convert it from: To this, on a single line: The private key must have the OpenSSH format, this can be done by importing the key in PuttyGen, and using the "Conversions" function to export it to an OpenSSH key format.

After these changes, the Git binding works beautifully via SSH!

I just wish that these key formats were documented better.

ThomasK wrote:I have just fought this battle in Flare2017r3 and finally figured out how to do this by sheer trial & error.
As I have wasted a lot of time figuring this out, i'm hoping to save other people from having to do the same by posting this here.

The public key must have a specific format of "[type] [base64key]"
So you can edit the key exported from, for example PuttyGen, in notepad to convert it from:

Code: Select all

---- BEGIN SSH2 PUBLIC KEY ----
Comment: "rsa-key-20170522"
LongMulti
LineBase64
StringHere==
---- END SSH2 PUBLIC KEY ----

To this, on a single line:

Code: Select all

ssh-rsa LongMultiLineBase64StringHere==

The private key must have the OpenSSH format, this can be done by importing the key in PuttyGen, and using the "Conversions" function to export it to an OpenSSH key format.

After these changes, the Git binding works beautifully via SSH!

I just wish that these key formats were documented better.

Now that you've cracked the magic code, please file a bug or enhancement for documentation update, and include the magic details in your request!