Skip to content
Snippets Groups Projects
Select Git revision
  • aebe0b735e6339a2f86cd8897dda4458b8ed8139
  • main default protected
  • 0.3.0.0
  • 0.2.1.0
  • 0.2.0.0
5 results

tahoe-ssk

  • Clone with SSH
  • Clone with HTTPS
    • Jean-Paul Calderone's avatar
    Successfully round-trip one real Tahoe-LAFS SDMF share
    Jean-Paul Calderone authored 
    Read Tahoe-LAFS-generated bytes, decode into a Share, re-encoded to the same
bytes.
    aebe0b73
    History
    Jean-Paul Calderone's avatar aebe0b73
    History
    Name Last commit Last update
    make-keypairs
    src/Tahoe
    test
    .envrc
    .gitlab-ci.yml
    CHANGELOG.md
    LICENSE
    README.md
    cabal.project
    flake.lock
    flake.nix
    tahoe-ssk.cabal
    README.md

    tahoe-ssk

    What is it?

    Tahoe-SSK is a Haskell implementation of the Tahoe-LAFS SSK crytographic protocols. This includes (S)mall (D)istributed (M)utable (F)iles (SDMF) and (M)edium (D)istributed (M)utable (F)iles (MDMF). It aims for bit-for-bit compatibility with the original Python implementation.

    It will not include an implementation of any network protocol for transferring SSK shares. However, its APIs are intended to be easy to integrate with such an implementation.

    What is the current state?

    • All implementation tasks are pending.

    Why does it exist?

    A Haskell implementation can be used in places the original Python implementation cannot be (for example, runtime environments where it is difficult to have a Python interpreter). Additionally, with the benefit of the experience gained from creating and maintaining the Python implementation, a number of implementation decisions can be made differently to produce a more efficient, more flexible, simpler implementation and API. Also, the Python implementation claims no public library API for users outside of the Tahoe-LAFS project itself.