veyepar: securely backing up gpg private keys.. to the cloud‽

Author(s):	Joey Hess
Location	Plenary Hall
Date	jan Mon 16	Days Raw Files
Start	17:40	First Raw Start	17:17
Duration	0:30:0	Offset	0:22:47
End	18:10	Last Raw End	18:17
Chapters	00:00 0:03:41
Total cuts_time	30 min.

http://linux.conf.au/schedule/presentation/152/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf securely_backing_up_gpg_private_keys_to_the_cloud.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Imagine a world in which gpg was not hard to use, and was used widely. Users exchange encrypted email, gpg sign comments on websites, make encrypted backups, and so on. What happens, in that world, when a user's gpg private key gets deleted? The only backup is encrypted with the lost private key. Catch 22. We're not in that world, and so we don't often worry about this problem. Unless we've lost gpg key ourselves. But solving the gpg key backup problem seems a necessary step in the path toward that world. Most ways to back up gpg private keys require physical security, like a safe to keep the key in, and often cumbersome backup and restore procedures. Keysafe makes backup and restore easy, by backing the private key up to the cloud. It necessarily trades off some security to do so, but manages to make it very expensive to compromise its backups. I'll explain how Argon2, Shamir Secret Sharing, relatively weak passwords, and AES decryption puzzles are combined in keysafe to accomplish this. markdown
Comment:	First ver had the mini conf opening included at the start. removed, encoding.... production notes

2017-01-17/10_17_13.ts Apply: 17:24:49 - 17:36:12 ( 00:11:23 ) S: 17:17:13 - E: 17:47:12 D: 00:29:59 (Start: 456.0) (End: 1139.0) show more...

vlc ~/Videos/veyepar/lca/lca2017/dv/plenary/2017-01-17/10_17_13.ts :start-time=0456.0 --audio-desync=0

	Raw File	Cut List
	17:17:13		seconds: 456.0 Wall: 17:24:49
Duration	00:29:59
	17:47:12		seconds: 1139.0 Wall: 17:36:12
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

2017-01-17/10_17_13.ts Apply: 17:36:12 - 17:41:16 ( 00:05:04 ) S: 17:17:13 - E: 17:47:12 D: 00:29:59 (Start: 1139.0) (End: 1443.0) show more...

vlc ~/Videos/veyepar/lca/lca2017/dv/plenary/2017-01-17/10_17_13.ts :start-time=01139.0 --audio-desync=0

	Raw File	Cut List
	17:17:13		seconds: 1139.0 Wall: 17:36:12
Duration	00:29:59
	17:47:12		seconds: 1443.0 Wall: 17:41:16
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

2017-01-17/10_17_13.ts Apply: 17:43:30 - 17:47:12 ( 00:03:41 ) S: 17:17:13 - E: 17:47:12 D: 00:29:59 (Start: 1577.640571) show more...

vlc ~/Videos/veyepar/lca/lca2017/dv/plenary/2017-01-17/10_17_13.ts :start-time=01577.640571 --audio-desync=0

	Raw File	Cut List
	17:17:13		seconds: 1577.640571 Wall: 17:43:30
Duration	00:29:59
	17:47:12		seconds: 0.0 Wall: 17:17:13
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this