(1) This is a cryptographically signed message in MIME format.

(2) This element is then digested and cryptographically signed.

(3) These two keys are related cryptographically.

(4) These keys are stored in cryptographically protected key store and upon successful login, the user's keys are loaded into the kernel and associated with the kernel processes.

(5) These keys are stored in a cryptographically protected key store and upon successful login, and the user's keys are loaded into the kernel and associated with the process credentials.

(6) In order to be cryptographically secure it needs to be as random as possible.

(7) The best defense against poisoning is developing a cryptographically secure cookie.

(8) The signature is still cryptographically valid, as the body element in question has not been modified (but simply relocated).

(9) When overridden in a derived class, fills an array of bytes with a cryptographically strong random sequence of values.

(10) It is not at all uncommon for these security tokens to have no cryptographically verifiable information.

(11) By attaching a digital signature to Java code, the origin of that code can be established in a cryptographically secure and unforgeable way.

(12) The best defense against cookie poisoning is developing a cryptographically secure cookie.

(13) The contest seeks to find a strong replacement for the current family of hash functions, some of which have been shown to be cryptographically weaker than originally thought.

(14) Then finally we hit on this idea of, "Why don't we just store money in the handheld devices?" The next iteration was this thing that would do cryptographically secure IOU notes.

(15) A set of endorsed claims is usually represented as a security token that is digitally signed or cryptographically protected by the authority.

(16) One thing the servers and clients in Parts 1, 2, and 3 had in common is that they operated completely in the clear, cryptographically speaking.

(17) You can harden a hashed password further by adding salt (a cryptographically secure random value) to the hash.

(18) If you deliver your components as a community component with an automated installation procedure, then you should sign your components cryptographically.