Verifies the signature
for the data
using a message digest algorithm digest
and a public key pkey
.
Returns true
if the signature is successfully verified, false
otherwise. The caller must check the return value.
See sign
for the signing operation and an example.
See also the man page EVP_DigestVerify(3).
Derives a shared secret from pkey and peer_pkey. pkey must contain the private components, peer_pkey must contain the public components.
Verifies a timestamp token by checking the signature, validating the certificate chain implied by tsa_certificate
and by checking conformance to a given Request
. Mandatory parameters are the Request
associated to this Response
, and an OpenSSL::X509::Store
of trusted roots.
Intermediate certificates can optionally be supplied for creating the certificate chain. These intermediate certificates must all be instances of OpenSSL::X509::Certificate
.
If validation fails, several kinds of exceptions can be raised:
TypeError
if types don’t fit
TimestampError
if something is wrong with the timestamp token itself, if it is not conformant to the Request
, or if validation of the timestamp certificate chain fails.
Performs a certificate verification on the OpenSSL::X509::Certificate
cert.
chain can be an array of OpenSSL::X509::Certificate
that is used to construct the certificate chain.
If a block is given, it overrides the callback set by verify_callback=
.
After finishing the verification, the error information can be retrieved by error
, error_string
, and the resulting complete certificate chain can be retrieved by chain
.
The type of the token.
Reparse the value and return the parse result.
Reparse the file and return the parse result.
Reparse the string and return the parse result.
Lazily initialize the parse result.
Creates a new DNS
name from arg
. arg
can be:
Get whether this list is empty.
Creates a new LOC::Size
from arg
which may be:
Creates a new LOC::Coord
from arg
which may be:
LOC::Coord
returns arg
.
String
arg
must match the LOC::Coord::Regex constant
Creates a new LOC::Alt
from arg
which may be:
For full_name
, verifies the certificate chain
is valid, the digests
match the signatures signatures
created by the signer depending on the policy
settings.
If key
is given it is used to validate the signing certificate.
Raises an exception if a security policy that verifies data is active. Old
format gems cannot be verified as signed.
Is the tar entry empty?
Specifies a gem dependency with the given name
and requirements
. You may also supply options
following the requirements
options
include:
RubyGems does not provide any autorequire features so requires in a gem dependencies file are recorded but ignored.
In bundler the require: option overrides the file to require during Bundler.require
. By default the name of the dependency is required in Bundler
. A single file or an Array
of files may be given.
To disable requiring any file give false
:
gem 'rake', require: false
Place the dependencies in the given dependency group. A single group or an Array
of groups may be given.
See also group
Only install the dependency on the given platform. A single platform or an Array
of platforms may be given.
See platform
for a list of platforms available.
Install this dependency from an unpacked gem in the given directory.
gem 'modified_gem', path: 'vendor/modified_gem'
Install this dependency from a git repository:
gem 'private_gem', git: 'git@my.company.example:private_gem.git'
Install this dependency from the gist ID:
gem 'bang', gist: '1232884'
Install this dependency from a github git repository:
gem 'private_gem', github: 'my_company/private_gem'
Set
to true
to include submodules when fetching the git repository for git:, gist: and github: dependencies.
Use the given commit name or SHA for git:, gist: and github: dependencies.
Use the given branch for git:, gist: and github: dependencies.
Use the given tag for git:, gist: and github: dependencies.
Loads dependencies from a gemspec file.
options
include:
The name portion of the gemspec file. Defaults to searching for any gemspec file in the current directory.
gemspec name: 'my_gem'
The path the gemspec lives in. Defaults to the current directory:
gemspec 'my_gem', path: 'gemspecs', name: 'my_gem'
The group to add development dependencies to. By default this is :development. Only one group may be specified.
Is this activation request for a development dependency?