onetime 1.122-1 source package in Ubuntu


onetime (1.122-1) unstable; urgency=low

  * New upstream release.
    - improved --intro documentation

onetime (1.111-1) unstable; urgency=low

  * New upstream release.
    - uses 'hashlib' module instead of 'sha1' to avoid deprecation warning
    - various Makefile improvements that don't really affect users
    - remove bashism in, as per Debian NMU change
 -- Ubuntu Archive Auto-Sync <email address hidden>   Mon,  17 Oct 2011 13:43:11 +0000

Upload details

Uploaded by:
Ubuntu Archive Auto-Sync on 2011-10-17
Uploaded to:
Original maintainer:
Karl Fogel
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Bionic release on 2017-10-24 universe misc
Artful release on 2017-04-20 universe misc
Zesty release on 2016-10-18 universe misc
Yakkety release on 2016-04-22 universe misc
Xenial release on 2015-10-22 universe misc
Wily release on 2015-05-04 universe misc
Vivid release on 2014-10-23 universe misc
Trusty release on 2013-10-18 universe misc
Precise release on 2011-10-17 universe misc


File Size SHA-256 Checksum
onetime_1.122.orig.tar.gz 1.7 MiB 44dff1dcbd83b08d743c22692a36bf95686a54a57f731b22124d0bd84e2828bf
onetime_1.122-1.diff.gz 3.1 KiB a3d0c50faae3b876a3675691b8a7292e7ccf595a8300c05b32d86e60cb83a93d
onetime_1.122-1.dsc 1.7 KiB 45d92c61d40146d1d2c84f3598fb00930224bb2709ce0652326fa6a4897c45f3

Available diffs

View changes file

Binary packages built by this source

onetime: command-line encryption using the "one-time pad" method

 OneTime is an encoder/decoder that uses the one-time pad algorithm.
 OneTime is a simple one-time pad encryption program that takes care
 of some of the pad-management bureaucracy for you. It avoids
 re-using pad data (except when decrypting the same encrypted message
 twice, of course) by maintaining records of pad usage.
 If you keep your ~/.onetime configuration area under version control
 with Subversion or CVS, OneTime will automatically update it to get
 the latest pad usage records before using a pad, and will commit new
 records after using a pad. Thus, by sharing a single configuration
 area via version control, you and your interlocutors can more easily
 avoid the sin of pad range reuse.
 See for more information about OneTime,
 or run 'onetime --help' for detailed usage. For more information about
 one-time pads in general, see