seccure - tools for using algorithms based on elliptic curve cryptography (ECC)

Distribution: Ubuntu 16.04 LTS (Xenial Xerus)
Repository: Ubuntu Universe i386
Package name: seccure
Package version: 0.5
Package release: 1
Package architecture: i386
Package type: deb
Installed size: 524 B
Download size: 29.73 KB
Official Mirror:
The seccure toolset implements a selection of asymmetric algorithms based on elliptic curve cryptography (ECC). In particular, it offers public key encryption / decryption and signature generation / verification. ECC schemes offer a much better key size to security ratio than classical systems (RSA, DSA). Keys are short enough to make direct specification of keys on the command line possible (sometimes this is more convenient than the management of PGP-like key rings). seccure builds on this feature and therefore is the tool of choice whenever lightweight asymmetric cryptography -- independent of key servers, revocation certificates, the Web of Trust, or even configuration files -- is required. The toolkit implements Diffie-Hellman key exchange, allowing you to agree a key with another party over an insecure channel. The Diffie Helman protocol affords forward secrecy, and requires no previous contact with the other party. The seccure toolset allows you to select the curve that the operations are performed on, so that different cryptographic needs can be supported. This is currently the only ECC package in Debian GNU/Linux to offer a choice of curves and MAC lengths. It is currently missing some of the functionality of the sks-ecc package, including encrypting to multiple recipients at once, and creating different signature formats.



    Binary package: seccure_0.5-1_i386.deb
    Source package: seccure

    Install Howto

    1. Update the package index:
      # sudo apt-get update
    2. Install seccure deb package:
      # sudo apt-get install seccure


    • /usr/bin/seccure-decrypt
    • /usr/bin/seccure-dh
    • /usr/bin/seccure-encrypt
    • /usr/bin/seccure-key
    • /usr/bin/seccure-sign
    • /usr/bin/seccure-signcrypt
    • /usr/bin/seccure-veridec
    • /usr/bin/seccure-verify
    • /usr/share/doc/seccure/PATENTS
    • /usr/share/doc/seccure/README
    • /usr/share/doc/seccure/changelog.Debian.gz
    • /usr/share/doc/seccure/copyright
    • /usr/share/man/man1/seccure-decrypt.1.gz
    • /usr/share/man/man1/seccure-dh.1.gz
    • /usr/share/man/man1/seccure-encrypt.1.gz
    • /usr/share/man/man1/seccure-key.1.gz
    • /usr/share/man/man1/seccure-sign.1.gz
    • /usr/share/man/man1/seccure-signcrypt.1.gz
    • /usr/share/man/man1/seccure-veridec.1.gz
    • /usr/share/man/man1/seccure-verify.1.gz
    • /usr/share/man/man1/seccure.1.gz


    2015-09-03 - Tomasz Buchert <> seccure (0.5-1) unstable; urgency=medium * New maintainer. Thanks James! (Closes: #797688) * Imported Upstream version 0.5 * d/patches: refresh * d/copyright: update & switch GPL-2+ to LGPL-3+

    2014-02-05 - Daniel Kahn Gillmor <> seccure (0.4-0.1) unstable; urgency=low * Non-Maintainer Upload * New upstream version (Closes: #671667) - upstream secure memory overhaul, dropping now-unneeded memlock patch * refresh patches * convert packaging to dh 9 * convert to 3.0 (quilt) (Closes: #664390) * bump Standards-Version to 3.9.5 (no changes needed) * ensure use of LDFLAGS during compilation * added debian/watch * debian/copyright: convert to machine-readable format * run test suite

    2008-09-16 - James Westby <> seccure (0.3-3) unstable; urgency=low * Modify the patch added in the last upload to enable gcrypt's secure memory, as apparently not disabling it is different to enabling it. (Closes: #489835)

    2008-08-06 - James Westby <> seccure (0.3-2) unstable; urgency=low * Make failure to mlock all memory only a warning, and re-enable gcrypt's memory locking. Changes in pam since etch mean that the kernel's defaults for memory locking are now respected, and seccure tries to lock more memory than that, which means that the program can't be started. The patch is from the upstream author, who considers it a stop-gap, but doesn't anticipate having a proper fix before lenny. (Closes: #489835) * Don't ignore "$(MAKE) clean" errors. The normal reason for this is the use of autotools leading to the makefile not necessarily being present when the clean target is run, be this package doesn't use autotools, so that won't happen. * Add a description to debian/patches/10-man-hyphen.dpatch. * Update the standards version to 3.8.0 (no changes required). * Release team: this isn't the diff that I sent you, I apologise. My sponsor suggested that fixing these small things wouldn't be a problem.

    2006-09-07 - James Westby <> seccure (0.3-1) unstable; urgency=low * New upstream release.

    2006-07-25 - James Westby <> seccure (0.2-1) unstable; urgency=low * Initial release (Closes: #378987)