The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

HomomorphicEncryption: BFV, BGV, CKKS Schema for Fully Homomorphic Encryption

Implements the Brakerski-Fan-Vercauteren (BFV, 2012) <https://eprint.iacr.org/2012/144>, Brakerski-Gentry-Vaikuntanathan (BGV, 2014) <doi:10.1145/2633600>, and Cheon-Kim-Kim-Song (CKKS, 2016) <https://eprint.iacr.org/2016/421.pdf> schema for Fully Homomorphic Encryption. The included vignettes demonstrate the encryption procedures.

Version: 0.9.0
Depends: polynom, stats, HEtools
Suggests: covr, knitr, rmarkdown, testthat (≥ 3.0.0)
Published: 2024-01-09
DOI: 10.32614/CRAN.package.HomomorphicEncryption
Author: Bastiaan Quast ORCID iD [aut, cre]
Maintainer: Bastiaan Quast <bquast at gmail.com>
License: GPL (≥ 3)
NeedsCompilation: no
Materials: README NEWS
CRAN checks: HomomorphicEncryption results

Documentation:

Reference manual: HomomorphicEncryption.pdf
Vignettes: BFV 2
BFV-addition
BFV in base R
BFV-multiply
BFV relinearization
BFV
BGV 2
BGV ModSwitch
BGV addition 2
BGV-addition
BGV-multiply
BGV
CKKS encode 3
CKKS encode encrypt 2
CKKS encode encrypt
CKKS encode
CKKS

Downloads:

Package source: HomomorphicEncryption_0.9.0.tar.gz
Windows binaries: r-devel: HomomorphicEncryption_0.9.0.zip, r-release: HomomorphicEncryption_0.9.0.zip, r-oldrel: HomomorphicEncryption_0.9.0.zip
macOS binaries: r-release (arm64): HomomorphicEncryption_0.9.0.tgz, r-oldrel (arm64): HomomorphicEncryption_0.9.0.tgz, r-release (x86_64): HomomorphicEncryption_0.9.0.tgz, r-oldrel (x86_64): HomomorphicEncryption_0.9.0.tgz
Old sources: HomomorphicEncryption archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=HomomorphicEncryption to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.