Modulecrypton-2.1.7Haskell2010

Crypto.PubKey.RSA.PSS

1 type
10 values

Packagecrypton-2.1.7
Exports11
LanguageHaskell2010
LicenceBSD-3-Clause AND MIT AND ISC
SourcePSS.hs

datadata PSSParams hash seed output

Parameters for PSS signature/verification.

Constructors

PSSParams
- pssHash :: hash
  Hash function to use
- pssMaskGenAlg :: MaskGenAlgorithm seed output
  Mask Gen algorithm to use
- pssSaltLength :: Int
  Length of salt. need to be <= to hLen.
- pssTrailerField :: Word8
  Trailer field, usually 0xbc

valuedefaultPSSParams

:: (ByteArrayAccess seed, ByteArray output, HashAlgorithm hash)
=> hash
-> PSSParams hash seed output

Default Params with a specified hash function

valuedefaultPSSParamsSHA1 :: PSSParams SHA1 ByteString ByteString

Default Params using SHA1 algorithm.

Sign and verify functions

8 declarations

valuesignWithSalt

:: HashAlgorithm hash
=> ByteString
Salt to use
-> Maybe Blinder
optional blinder to use
-> PSSParams hash ByteString ByteString
PSS Parameters to use
-> PrivateKey
RSA Private Key
-> ByteString
Message to sign
-> Either Error ByteString

Sign using the PSS parameters and the salt explicitely passed as parameters.

the function ignore SaltLength from the PSS Parameters

See Blinder for what the optional blinder covers and when leaving it out is a decision rather than a default. signSafer generates one for you.

valuesignDigestWithSalt

:: HashAlgorithm hash
=> ByteString
Salt to use
-> Maybe Blinder
optional blinder to use
-> PSSParams hash ByteString ByteString
PSS Parameters to use
-> PrivateKey
RSA Private Key
-> Digest hash
Message digest
-> Either Error ByteString

Sign using the PSS parameters and the salt explicitely passed as parameters.

the function ignore SaltLength from the PSS Parameters

See Blinder for what the optional blinder covers and when leaving it out is a decision rather than a default. signSafer generates one for you.

valuesign

:: (HashAlgorithm hash, MonadRandom m)
=> Maybe Blinder
optional blinder to use
-> PSSParams hash ByteString ByteString
PSS Parameters to use
-> PrivateKey
RSA Private Key
-> ByteString
Message to sign
-> m (Either Error ByteString)

Sign using the PSS Parameters

See Blinder for what the optional blinder covers and when leaving it out is a decision rather than a default. signSafer generates one for you.

valuesignDigest

:: (HashAlgorithm hash, MonadRandom m)
=> Maybe Blinder
optional blinder to use
-> PSSParams hash ByteString ByteString
PSS Parameters to use
-> PrivateKey
RSA Private Key
-> Digest hash
Message digest
-> m (Either Error ByteString)

Sign using the PSS Parameters

See Blinder for what the optional blinder covers and when leaving it out is a decision rather than a default. signSafer generates one for you.

valuesignSafer

:: (HashAlgorithm hash, MonadRandom m)
=> PSSParams hash ByteString ByteString
PSS Parameters to use
-> PrivateKey
private key
-> ByteString
message to sign
-> m (Either Error ByteString)

Sign using the PSS Parameters and an automatically generated blinder.

valuesignDigestSafer

:: (HashAlgorithm hash, MonadRandom m)
=> PSSParams hash ByteString ByteString
PSS Parameters to use
-> PrivateKey
private key
-> Digest hash
message digst
-> m (Either Error ByteString)

Sign using the PSS Parameters and an automatically generated blinder.

valueverify

:: HashAlgorithm hash
=> PSSParams hash ByteString ByteString
PSS Parameters to use to verify, this need to be identical to the parameters when signing
-> PublicKey
RSA Public Key
-> ByteString
Message to verify
-> ByteString
Signature
-> Bool

Verify a signature using the PSS Parameters

valueverifyDigest

:: HashAlgorithm hash
=> PSSParams hash ByteString ByteString
PSS Parameters to use to verify, this need to be identical to the parameters when signing
-> PublicKey
RSA Public Key
-> Digest hash
Digest to verify
-> ByteString
Signature
-> Bool

Verify a signature using the PSS Parameters

Following RFC 8017, the signature is rejected unless it is exactly as long as the modulus (section 8.1.2, step 1) and its integer representative is below the modulus (RSAVP1, section 5.2.2, step 1). The public-key operation normalises any multiple of the modulus away, so without the second check s + n would verify as readily as s, and a third party could turn one valid signature into another without the private key.