Hello
Greeetings to you please did you get my previous email regarding my
investment proposal last week friday ?
MS.Zeliha ömer faruk
zeliha.omer.fa...@gmail.com
I have a confidential deal for you, please contact me for more details via
this
email immediately.
Hi Herbert,
We already have an interface that can handle asymmetric keys and it is easy
to extend with new key formats and key types. So lets use that. I can
clearly see that after RSA, we get DSA, ECDH etc. So having a simple way to
handle these key formats is a good idea. That
On Tue, Aug 04, 2015 at 09:33:27PM -0700, Marcel Holtmann wrote:
I think it actually is the correct interface. And it will still stay a purely
algorithmic interface. It is just that the algorithm is bound to specific
hardware with a specific key. I really do not understand your distinction
On Mon, Aug 03, 2015 at 12:25:31AM -0700, Marcel Holtmann wrote:
RSA Private Key is n + e + d (including 6 other fields). RSA Public Key is n
+ e (no other fields).
So for RSA you would make setkey to take RSA Private Key and setpubkey to
take RSA Public Key. Meaning you only have to use
Hi Herbert,
RSA Private Key is n + e + d (including 6 other fields). RSA Public Key is n
+ e (no other fields).
So for RSA you would make setkey to take RSA Private Key and setpubkey to
take RSA Public Key. Meaning you only have to use one of them since if you
have the private key, you
Am Sonntag, 2. August 2015, 22:28:33 schrieb Marcel Holtmann:
Hi Marcel,
Hi Tadeusz,
I think we need to split the akcipher_alg setkey callback into a setkey and
setpubkey.
diff --git a/include/crypto/akcipher.h b/include/crypto/akcipher.h
index 69d163e39101..ca93952b6d19 100644
---
Hi Stephan,
I think we need to split the akcipher_alg setkey callback into a setkey
and
setpubkey.
diff --git a/include/crypto/akcipher.h b/include/crypto/akcipher.h
index 69d163e39101..ca93952b6d19 100644
--- a/include/crypto/akcipher.h
+++ b/include/crypto/akcipher.h
@@ -91,6 +91,8 @@
Hi Stephan,
I think we need to split the akcipher_alg setkey callback into a setkey and
setpubkey.
diff --git a/include/crypto/akcipher.h b/include/crypto/akcipher.h
index 69d163e39101..ca93952b6d19 100644
--- a/include/crypto/akcipher.h
+++ b/include/crypto/akcipher.h
@@ -91,6 +91,8 @@
Am Montag, 3. August 2015, 00:03:03 schrieb Marcel Holtmann:
Hi Marcel,
Hi Stephan,
I think we need to split the akcipher_alg setkey callback into a setkey
and
setpubkey.
diff --git a/include/crypto/akcipher.h b/include/crypto/akcipher.h
index 69d163e39101..ca93952b6d19 100644
Hi Tadeusz,
I think we need to split the akcipher_alg setkey callback into a setkey and
setpubkey.
diff --git a/include/crypto/akcipher.h b/include/crypto/akcipher.h
index 69d163e39101..ca93952b6d19 100644
--- a/include/crypto/akcipher.h
+++ b/include/crypto/akcipher.h
@@ -91,6 +91,8 @@ struct
Hi,
I am Mr. Vincent Cheng; I have a Business Proposal of $30,500,000.00
for you .
I will need you to assist me in transferring this funds to a secured
account.
If interested, please reply to this email, mrchengvic...@yahoo.com.hk
Regards,
Vincent Cheng.
--
To unsubscribe from
PROTECTED]
Sent: Monday, May 19, 2008 9:01 PM
To: Loc Ho
Cc: Evgeniy Polyakov; Sebastian Siewior; Shasi Pulijala;
linux-crypto@vger.kernel.org
Subject: Re: Linux CryptoAPI Userspace API proposal
On Thu, May 15, 2008 at 01:16:03PM -0700, Loc Ho wrote:
Linux Crypto User Space Interface Requirement
On Thu, May 15, 2008 at 01:16:03PM -0700, Loc Ho wrote:
Linux Crypto User Space Interface Requirement:
1. Support crypto and hashing/digest
2. Flexible to support compression in the future
3. Flexible to support PKA (public key acceleration) in the future
I think extensibility as you've
if the
underlying algorithm support it. Hardware algorithm (such as HMAC
hashing) have a limit. This requirement complicate the interface. May
not support initially.
Linux Crypto User Space Interface Proposal:
1. Use file descriptor named '/dev/crypto'
2. Each opened file creates a new 'crypto' context
* Herbert Xu | 2008-05-14 19:03:11 [+0800]:
On Wed, May 14, 2008 at 12:32:24PM +0200, Sebastian Siewior wrote:
This should add support for OpenSSL. Please note that user of this patch
musts patch OpenSSL. The OpenSSL patch can be found in OCF-Linux as this
interface uses the same I/O control
On Wed, May 14, 2008 at 01:57:30PM +0200, Sebastian Siewior ([EMAIL PROTECTED])
wrote:
Great. Here a few ideas for a new interface:
- /dev/crypto:
- open file, creates a new ctx which may be one of crypto/hash/...
- set type via ioctl / netlink
- set key / other attributes via ioctl
Hi.
On Wed, May 14, 2008 at 08:40:43AM -0700, Loc Ho ([EMAIL PROTECTED]) wrote:
Option #2:
1. Use syscall with algorithm name and its associated parameters
2. Operation such as encrypt, decrypt, hash, and etc are operated via
another two system call - crypto_read and crypto_write
3. For this
18 matches
Mail list logo
