https://github.com/crodriguezvega/go-knapsackcrypto

Knapsack crypto systems in Go
https://github.com/crodriguezvega/go-knapsackcrypto

crypto cryptography cryptography-library go golang knapsack-crypto knapsack-encryption merkle-hellman merkle-hellman-knapsack public-key-cryptography

Last synced: 12 days ago
JSON representation

Knapsack crypto systems in Go

• Host: GitHub
• URL: https://github.com/crodriguezvega/go-knapsackcrypto
• Owner: crodriguezvega
• License: mit
• Created: 2021-02-03T21:39:53.000Z (almost 4 years ago)
• Default Branch: master
• Last Pushed: 2023-08-19T20:38:14.000Z (about 1 year ago)
• Last Synced: 2024-06-21T20:07:26.292Z (5 months ago)
• Topics: crypto, cryptography, cryptography-library, go, golang, knapsack-crypto, knapsack-encryption, merkle-hellman, merkle-hellman-knapsack, public-key-cryptography
• Language: Go
• Homepage:
• Size: 1.11 MB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# go-knapsackcrypto

[![Build Status](https://travis-ci.org/crodriguezvega/go-knapsackcrypto.svg?branch=master)](https://travis-ci.org/github/crodriguezvega/go-knapsackcrypto)

Implementation of knapsack crypto systems in Go.

Run the tests: `go test -v ./...`

## Schemes

### Basic & Multiple-iterated Merkle-Hellman knapsack public-key encryption

Basic is single-iterated, so `iterations` is `1`. For multiple-iterated, choose `iterations` greater than `1`.

References:

- Chapter 6 of "An Introduction to Mathematical Cryptography" by Jeffrey Hoffstein, Jill Pipher and J.H Silverman.

- [Chapter 8](http://cacr.uwaterloo.ca/hac/about/chap8.pdf) of "Handbook of Applied Cryptography" by Alfred J. Menezes et al.

Remarks:

- Decryption will produce a bit slice of the same length as the super increasing sequence of the private key. But the actual bit length of the encrypted plaintext message could be smaller. Therefore to correctly extract the plaintext message I make use of the fact that I know the byte length of the original message. I guess in real-life situations you would encrypt together with the plaintext message some code that allows the decrypting party to know how long the message actually is.

- The number of bits of the public key is 2 times the length of the super increasing sequence to the power of 2, then the bit size of the public key grows exponentially with the length of the super increasing sequence. The bit length of the plaintext message needs to be smaller than or equal to the length of the super increasing sequence of the private key, therefore this scheme does not seem to be very practical for encrypting long messages.

Example:

`go run examples/merklehellman/main.go`

### Chor-Rivest knapsack public-key encryption

TODO