In all the following assignments, we assume that your public keys are obtainable via the email address use for handing in the assignment.
git
bitbucket.org
,
gitlab.com
, or
github.com
,
git push
your local repo to the above remote repo.
node
assignments the line
node_modules/
must
be in your .gitignore
file.
<nmla@iba.dk>
with:
submission <subjectname>
'
in the subject line
Download and install GnuPG from https://www.gnupg.org/download/, find the appropriate version in the section: GnuPG binary releases.
Generate a keypair for yourself, and export your
public key to an asc
,
ASCII Armored, file.
Use your regular email address when generating
your keypair.
Then publish your exported public key to either:
If you get a verification email, don't ignore it.
Create a text file, and encrypt it with your
own public key, use your email as
recipient
.
Give the encrypted file the name
SecE1.enc.txt
.
Then open the encrypted file
in your favorite editor. What happens?
Then decrypt the file into a file differently name than the original file. Verify that the content has become itself again.
Finally, encrypt the original file with
nmla@iba.dk
as the recipient.
You may get the public key from:
https://keyserver.pgp.com.
Name the output SecE1a.enc.txt
.
Both encrypted files go into the repo.
Take the text of this assignment, and put
it into a txt document. Then sign it with a
regular digital signature, name the output
SecE2.sign.txt
, and put it into
the repo.
Create a short document, and clearsign it into
SecE3.sig.txt
.
The document should give a possible use case for
clearsign.