tarsnap-recrypt.1-man 2.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192
  1. .TH TARSNAP-RECRYPT 1 "@DATE@" ""
  2. .SH NAME
  3. .ad l
  4. \fB\%tarsnap-recrypt\fP
  5. \- re-encrypts data stored using
  6. \fBtarsnap\fP(1)
  7. .SH SYNOPSIS
  8. .ad l
  9. .br
  10. \fB\%tarsnap-recrypt\fP
  11. \fB\--oldkey\fP \fIold-key-file\fP
  12. \fB\--oldcachedir\fP \fIold-cache-dir\fP
  13. \fB\--newkey\fP \fInew-key-file\fP
  14. \fB\--newcachedir\fP \fInew-cache-dir\fP
  15. .br
  16. \fB\%tarsnap-recrypt\fP
  17. \fB\--version\fP
  18. .SH DESCRIPTION
  19. .ad l
  20. \fB\%tarsnap-recrypt\fP
  21. downloads and decrypts data using
  22. \fIold-key-file\fP
  23. and re-encrypts and uploads it using
  24. \fInew-key-file\fP.
  25. After all the data has been re-uploaded,
  26. \fB\%tarsnap-recrypt\fP
  27. deletes the data using
  28. \fIold-key-file\fP
  29. so that the only remaining copy of the data
  30. is encrypted using
  31. \fInew-key-file\fP.
  32. The key file
  33. \fInew-key-file\fP
  34. must have been generated by
  35. \fBtarsnap-keyregen\fP(1)
  36. with
  37. \fIold-key-file\fP.
  38. .PP
  39. \fB\%tarsnap-recrypt\fP
  40. checkpoints its progress after every 1-2 GB of data that it has
  41. copied; if it is interrupted it can be re-run and it will
  42. attempt to continue.
  43. .PP
  44. Note that after
  45. \fB\%tarsnap-recrypt\fP
  46. completes it will be possible to store more archives using the key
  47. \fIold-key-file\fP
  48. and the cache directory
  49. \fIold-cache-dir\fP
  50. so care should be taken to disable any automatic (e.g.,
  51. \fBcron\fP(8))
  52. archiving while
  53. \fB\%tarsnap-recrypt\fP
  54. is run.
  55. .PP
  56. The
  57. \fB\--version\fP
  58. option prints the version number of
  59. \fB\%tarsnap-recrypt\fP,
  60. then exits.
  61. .SH EXAMPLES
  62. .ad l
  63. The following sequence of commands will create new keys and re-encrypt
  64. data, assuming that the currently used keys are in
  65. \fI/root/tarsnap.key\fP
  66. and the current cache directory is
  67. \fI/usr/local/tarsnap-cache\fP:
  68. .PP
  69. .RS 4
  70. \fBtarsnap-keyregen\fP \fB\--keyfile\fP \fI/root/tarsnap.key.new\fP \fB\--oldkey\fP \fI/root/tarsnap.key\fP \fB\--user\fP \fIme@example.com\fP \fB\--machine\fP \fImyserver\fP
  71. .RE
  72. .PP
  73. .RS 4
  74. \fB\%tarsnap-recrypt\fP \fB\--oldkey\fP \fI/root/tarsnap.key\fP \fB\--oldcachedir\fP \fI/usr/local/tarsnap-cache\fP \fB\--newkey\fP \fI/root/tarsnap.key.new\fP \fB\--newcachedir\fP \fI/usr/local/tarsnap-cache.new\fP
  75. .RE
  76. .PP
  77. .RS 4
  78. \fBrm\fP \fB\-r\fP \fI/usr/local/tarsnap-cache\fP
  79. .RE
  80. .PP
  81. .RS 4
  82. \fBmv\fP \fI/usr/local/tarsnap-cache.new\fP \fI/usr/local/tarsnap-cache\fP
  83. .RE
  84. .PP
  85. .RS 4
  86. \fBrm\fP \fI/root/tarsnap.key\fP
  87. .RE
  88. .PP
  89. .RS 4
  90. \fBmv\fP \fI/root/tarsnap.key.new\fP \fI/root/tarsnap.key\fP
  91. .RE