summaryrefslogtreecommitdiff
path: root/Data/OpenPGP
AgeCommit message (Collapse)Author
2019-11-09Ed25519 support.Joe Crayne
2019-07-16Add hex function to curse fingerprints with.Joe Crayne
2019-07-15Switched fingerprint to a wrapped ByteString.Joe Crayne
2019-07-03Big-num optimization.Joe Crayne
2019-07-03More big-num changes.Joe Crayne
2019-07-01randomS2K utility.joe
2019-07-01Completed cryptonite support.joe
2019-07-01WIP: support for cryptonite.joe
2019-07-01decryptSecretKey now a no-op for unenciphered keys.joe
2019-07-01encryptSecretKeyjoe
2019-07-01white spacejoe
2017-08-29Include derived file Arbitrary.hs in repoAndrew Cady
This allows the git repo to be used as a dependency for stack builds.
2016-04-25Import Control.Applicative (for older base).joe
2016-04-25Key generation.joe
2016-04-14Merged openpgp package into openpgp-utiljoe
2014-01-04Build against older libsjoe
2013-12-15Adapted to new ecc solutoin for OpenPGP-Haskelljoe
2013-12-14use toStrictBS with Data.Binary in order to drop cereal dependency.joe
2013-12-14Refactoring.joe
2013-12-14New package openpgp-util as alternative to OpenPGP-CryptoAPI.joe
2012-04-27Hide internal stuff that is used by testsStephen Paul Weber
2012-04-25Split OpenPGP.Crypto out into a seperate packageStephen Paul Weber
2012-04-25fix for MD5 without BaseConvertStephen Paul Weber
2012-04-25hlintStephen Paul Weber
2012-04-25Remove BaseConvertStephen Paul Weber
We only use it for hex, which is in base, and base even has a utility for arbitrary-base conversions.
2012-04-25Make SignaturePacket opaque, emit trailerStephen Paul Weber
Instead of the Put instance emitting the actual packet header, it emits the start of the trailer data (which is the same bytes as the packet header). SignaturePacket is opaque and there is a smart constructor, signaturePacket, that takes all the data *except* the trailer and auto-generates the trailer, making sure the trailer is always valid, so that the above becomes possible. WARNING: SignaturePacket is not *fully* opaque. You *may* still update fields directly using record syntax (on an already constructed packet). This may be useful, but if any of the values that make up the trailer are changed this will MAKE THE PACKET INVALID. This trade-off is deemed acceptable for now, but may change in the future. Any fields that do not affect the trailer (unhashed subpackets, etc) may be safely updated in this way. Other fields MUST be updated by constructing a new SignaturePacket with the smart constructor. This usage is exemplefied by Data.OpenPGP.Crypto The major upside of this is that it is now possible to re-emit unmodified (or even modified, if only fields not in the trailer are modified) SignaturePackets without invalidating the signature. Closes #11
2012-04-24typo in commentStephen Paul Weber
2012-04-24Some fixes for signature verificationStephen Paul Weber
2011-08-12docs typosStephen Paul Weber
2011-08-12Refactor sign to handle keysStephen Paul Weber
Also, now if you pass in a message with a signature packet we'll just use that one instead of making a default one. Return value is now just the new/filled-in signature packet, update example accordingly.
2011-08-10Ability to sign a message with RSAStephen Paul Weber
2011-08-08haddockStephen Paul Weber
2011-08-08Move into Data hierarchyStephen Paul Weber