delegatevoid Posted April 14, 2014 Report Share Posted April 14, 2014 According to the documentation:http://[address]:[port]/api?method=get_secrets[&secret=(secret)&type=encryption] When "type" is set to "encryption" the response should also contain the encryption keyThis worked with version 1.2.82 but as of version 1.2.91 it no longer returns the encryption key. Side note: The API docs need version markers and be more consistent. Quote Link to comment Share on other sites More sharing options...
scus Posted April 14, 2014 Report Share Posted April 14, 2014 The current version is 1.3.87!? And in this version the API returns an encryption secret. Quote Link to comment Share on other sites More sharing options...
delegatevoid Posted May 2, 2014 Author Report Share Posted May 2, 2014 Really? Damn'it the "update" feature of the client always says it's up to date...Will check for a manual update. Quote Link to comment Share on other sites More sharing options...
delegatevoid Posted May 2, 2014 Author Report Share Posted May 2, 2014 Ok, apparently they changed the parameter from "encryption" to "encrypted". And yet I'm not getting the encrypted key:http://localhost:8888/api?method=get_secrets&secret=AAAAAAAAAAAAAAAAAAAAAAAA&type=encryptedReturns:{ "read_only": "AAAAAAAAAAAAAAAAAA", "read_write": "BBBBBBBBBBBBBB" }Note that I did replace the actual key values before posting here. The API documentation specifies:http://[address]:[port]/api?method=get_secrets[&secret=(secret)&type=encryption]Yet the following line on the same page specifies: secret (required) - must specify folder secrettype (optional) - if type=encrypted, generate secret with support of encrypted peerPlease note the colour coded parameter and how two different versions are used: encrypted vs encryption Neither values return the encrypted key for me. (v1.3.94) Quote Link to comment Share on other sites More sharing options...
delegatevoid Posted June 5, 2014 Author Report Share Posted June 5, 2014 In version 1.3.105 this has finally been fixed!The correct type value is encryption, the API documentation is still outdated.However it only works if you don't specify any value for "secret".As soon as you do it doesn't work anymore. When is someone from the BTSync team going to deal with the API? Quote Link to comment Share on other sites More sharing options...
RomanZ Posted June 10, 2014 Report Share Posted June 10, 2014 @delegatevoid The correct value is encryption and it is the same in documentation. Please let me know if it is documented in a wrong way somewhere - we'll fix it. Also, the "type" parameter is taken only if you are generating a new secret. If you supply API some key - it will ignore the type and get it from the key you fed. If the key can encrypt-decrypt data - API automatically will give you Encryption key as well. Quote Link to comment Share on other sites More sharing options...
delegatevoid Posted June 10, 2014 Author Report Share Posted June 10, 2014 Please see the attached screenshot, one time it specifies encryption the other type encrypted As for getting the encrypted secret for an existing folder I will try that again. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted June 10, 2014 Report Share Posted June 10, 2014 Thanks for pinpointing it, we'll fix it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.