summaryrefslogtreecommitdiff
path: root/Data
AgeCommit message (Collapse)Author
2012-04-27SignatureExpirationTimePacket, ExportableCertificationPacket, ↵Stephen Paul Weber
TrustSignaturePacket
2012-04-27Handle signature subpacket critical bitStephen Paul Weber
Currently throws away the data. Suboptimal
2012-04-27Hide internal stuff that is used by testsStephen Paul Weber
2012-04-26Second openpgp-cereal package using CPPStephen Paul Weber
When you compile with make CEREAL=1
2012-04-25A signature may be multiple MPIsStephen Paul Weber
2012-04-25Use mapM_ for Message putStephen Paul Weber
2012-04-25Higher-order "get until end of input as list"Stephen Paul Weber
2012-04-25this list is always tiny, Data.Map is overkillStephen Paul Weber
2012-04-25move find_key logit out of CryptoStephen Paul Weber
2012-04-25fix haddock warningStephen 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-25better TODO errorStephen Paul Weber
2012-04-25s2k values are really optional, not undefinedStephen Paul Weber
Should they be grouped in some way? Should encrypted_data also be grouped with them in some way?
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
2012-04-24Represent unsupported packets and subpackets by their literal bytesStephen Paul Weber
2012-04-24suppress warningStephen Paul Weber
2012-04-24actually handle encoding s2k countStephen Paul Weber
2012-04-24private_hash may be inside the encrypted blobStephen Paul Weber
2012-04-24Unknown algorithms and EnumStephen Paul Weber
Closes #6 Closes #7
2012-04-24some formatting cleanupStephen 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-12Was encoding/reading MPI backwardsStephen Paul Weber
2011-08-10Ability to sign a message with RSAStephen Paul Weber
2011-08-10make fingerprint_material able to read SecretKeyPacketStephen Paul Weber
2011-08-10export calculate_signature_trailerStephen Paul Weber
2011-08-10fix signature subpacket parsingStephen Paul Weber
2011-08-08hlint cleanStephen Paul Weber
2011-08-08haddockStephen Paul Weber
2011-08-08Haskel98 parsing compatStephen Paul Weber
2011-08-08Move into Data hierarchyStephen Paul Weber