selfupdatectl

README

selfupdatectl: Manage deployment of self updating Fyne programs

selfupdatectl provide the ability to generate private and public key that can be used to sign and verify Fyne program to finally upload them to a S3 bucket.

To install selfupdatectl you should do:

go install github.com/fynelabs/selfupdate/cmd/selfupdatectl

selfupdatectl create-keys and selfupdatectl print-key

Calling selfupdatectl create-keys will result in the generation of a brand new private key ed25519.key and public key ed25519.pem. It is recommended to absolutely not store your private key (ed25519.key) in your git repository. If you are using a password manager, you should use it to store this private key. This keys are not password protected at the moment and you should be careful with them.

As you need to specify your public key to use selfupdate managed API, the easiest way is by using:

$ selfupdatectl print-key
publicKey := ed25519.PublicKey{178, 103, 83, 57, 61, 138, 18, 249, 244, 80, 163, 162, 24, 251, 190, 241, 11, 168, 179, 41, 245, 27, 166, 70, 220, 254, 118, 169, 101, 26, 199, 129}

And copy&paste the resulting line in your source code where you are instantiating selfupdate.Manage.

selfupdatectl sign myprogram ...

To sign an executable, you first need to create the private key necessary for that as described in the previous session. Once you do have the private key, you can do to sign your binary myprogram the following command: selfupdatectl sign myprogram.

This will generate a file named myprogram.ed25519 of size 64 bytes that contain the signature of your binary.

selfupdatectl check myprogram ...

To verify that your binary was properly signed, just call selfupdatectl check myprogram. It will error if there is a problem with your signature.

selfupdatectl s3upload myprogram targetS3Path

You can use selfupdatectl s3uploads myprogram-windows-amd64 targetS3PAth to automate signing your program and uploading to a target AWS S3 path. If no additional parameter are specified, it will try to read AWS information from configuration file and environment variable. Usually you would need to set $AWS_S3_REGION and $AWS_S3_BUCKET to match your need.