StellarGuard

StellarGuard On feature 2: it’s probably better to do the 24 word phrase considering most people with hardware wallets have gotten used to that

That would be awesome to have a two-factor authentication similar to what we have on exchanges (code-only). Maybe you could serve some kind of HTML form that we would embed into a secure iframe? It would have to check that the iframe is indeed sandboxed, and would have to display let's say an user choosen quote or sentence to prove it's from you. Not sure if it's actually possible. I think it would make the user experience awesome! Anyway keep up the good work, StellarGuard is great ?

MisterTicot Would you mind clarifying what you mean by that? Do you mean the option of having StellarGuard integration/approval embedded directly into the wallet/tool you're using instead of having to go to the StellarGuard website?

StellarGuard Yes exactly, and having the option to use only the Google authenticator on top of that. (No mail)

I am going to be focusing heavily on 3rd party integration in the coming months, and something like this is on the top of the list. I want to explore whitelabel solutions around the same time. However, I want to take the time to do it right (developer API keys, oauth, etc...), so probably won't have something ready in the near future. But it's coming soonish (TM).

We would like to build in Native support into our wallet and the dotnet sdk for StellarGuard.

elucidsoft Great! Let me know how I can help. I've done C# in a previous life so I could probably help with the implementation as well. Send an email to developers@stellarguard.me if you want to get in touch outside of here.

I've added rudimentary transaction callback support today -- where when submitting a transaction you can specify an optional callback url that is POST'd to on successful transaction authorization and submission. POST /api/transactions { xdr: "<transaction-xdr>" callback: "https://webhook.site/7753d513-fc9b-488e-b762-c4596b79a3e7' } And also published version 1.4.1 of the StellarGuard JS SDK with support for it. const callback = 'https://webhook.site/7753d513-fc9b-488e-b762-c4596b79a3e7'; StellarGuardSdk.submitTransaction(transaction, callback); You can see the data that gets sent to the callback here: https://webhook.site/#/cc677ade-969d-411e-9b9c-93745f69d37b/407fad2d-a4b3-44e3-a235-d9a32f20c783/0

I've completed and pushed all 3 of the mentioned features (Onboarding, Transaction Security Level, Recovery Phrase) to https://test.stellarguard.me and will push it to production after a bit more testing. Feel free to get a preview if you have a test account (or sign up for one to try it) and if you do, please let me know what you think. I'm also very happy to announce that StellarGuard has 3 more fully supported wallets/tools! Stellar Authenticator MyStellar.Tools Nucleo.fi I'll be adding them to the supported wallets page shortly as well as writing up tutorials for each one. Thank you so much for supporting StellarGuard. Screenshots of the onboarding flow:

StellarGuard Just to complete your message StellarGuard is also supported by cosmic-lib, so when cosmicLink.send() and 2FA is enabled the transaction is automatically send to Stellar Guard.

StellarGuard - Add enhanced security to any Stellar account

tim That’s all there is to it! There is also a JS SDK I have published if you happen to be doing it client-side or via NodeJS (https://github.com/stellarguard/stellarguard-js-sdk).

You are free to use any StellarGuard logos, marks, code, or whatever you would like.

Let me know if you have any more questions or need help integrating.

tim

StellarGuard I made a testrun and it works as described. As I have timed transactions I have the additional requirement that the transaction can't be submited right away. Could we have a chat about that? My contact is contact(at)smartstellarDOTorg.

StellarGuard

In case anyone else wants this functionality -- in response to the inquiry tim, I'll be adding a "do not submit to Stellar" flag along with the transaction, which will default to false (or a submit to Stellar flag, which defaults to true, have not decided yet). Depending on the value, it will sign and return the XDR to the user without submitting it. Combined with the callback url, this should allow services to manage how they want to handle the XDR, and also enable better interop with other multisig coordinators (sign the transaction and, pass it back to another coordinator).

This is looking more and more like SEP-0007 protocol as I progress -- so I may end up changing it to support that spec as well (even though I wouldn't register a handler for it).

StellarGuard

Note: I changed the semantics of the "callback" parameter to match what SEP-0007 does, and send back the signed XDR instead of submitting it to Stellar directly. This will make things more flexible in the future as well.

sbsends

Hey @StellarGuard, would you mind explaining how you are using KMS to encrypt the keys? I would like to do the same thing.

Congrats!!

Sam

StellarGuard

sbsends Sure thing. Here's the googleKms code I use for it: https://github.com/stellarguard/stellarguard/blob/master/src/server/lib/utils/googleKms.js

There are other clients besides NodeJS, too.

It's essentially just a REST API that you call from within your app - but you need to convert to base64 when storing and from base64 when retrieving.

You need to configure your keyrings on the Google Cloud Console: https://console.cloud.google.com/security/kms

One thing that bit me when I first set it up: make sure your app's service account is added in the Permissions section to the "Cloud KMS CryptoKey Encrypter/Decrypter" membership.

sbsends

Check my understanding:

Saving key
1) generate keypair on server running the code
2) convert to base64
3) send data to KMS
4) receive encrypted data and store in database

Loading key
1) pull from database
2) send encrypted data to KMS for decryption
3) covert back from base64
4) use key
5) purge from memory

Thank you! I will give it a try.

« Previous Page