If I have a directory and it has 10 files and I have 10 separate keys
such that key1 is for file1 and key2 is for file2 (etc.); is there a
way to automate the encryption process like that?
Or do I have to run each of the commands separate and instead of
having 10 separate keys in a single keyfile
Does it matter whether it's ia32 or ia64 even for an x64 processor?
Shouldn't there be some way for me to check whether AES is enabled or
being used (other than running a speed test) either in dmesg or /proc/
or with openssl itself? I'm a little confused, and surprised/shocked
that there isn't a w
On Thu, Mar 14, 2013, Ewen Chan wrote:
> So this is a partial continuation from the discussion thread that I
> started yesterday in regards to using AES-CBC.
>
> I've got an Intel Core i7 3930K that supports AES-NI and I spent the
> greater part of last night trying to get openssl to work or at l
Bob,
I have never seen dynamic locks being created, only static ones. I have
added dynamic locks because the documentation says that I'll avoid trouble in
the future by doing it now. I only added them recently and had been running
without them for years with no problems reported.
Gordon,
Just quick question for you, have you seen any dynamic mutex lock been created
while your openssl application is running? I implemented both static and
dynamic locking mechanism in my application. I can see that there are a total
of 41 static mutex locks been created during initializati
Hi Rich!
Glad to hear from you and hope all is well!
Thanks for the tip, but I haven't cracked this nut yet. I've tried several
permutations of:
- the UTF8 flag on req - openssl req -x509 -newkey rsa:1024 -out
rootcacert.pem -utf8 -outform PEM
- the no UTF8 flag on req - openssl req -x509 -new
Hi all
I trying to create a csr (in a c program) that uses a hardware private
public key and I am accessing this token by pkcs11. However, the csr is
always invalid, with the following message:
$ openssl req -verify -in wltx.csr
verify failure
1996:error:0D07207B:asn1 encoding routines:ASN1_g
Hi all
I trying to create a csr (in a c program) that uses a hardware private
public key and I am accessing this token by pkcs11. However, the csr is
always invalid, with the following message:
$ openssl req -verify -in wltx.csr
verify failure
1996:error:0D07207B:asn1 encoding routines:ASN1_get
I’m trying to understand some code someone wrote as a wrapper for the
openssl library / tool, with a view to updating it.
I'm completely new to openssl and PKI in general. I found the following
docs / references to help navigate but I wasn't able to find answer to my
question.
http://users.dcc.uc
Hi John!
Looking at apps/req.c, it seems you want to use the -utf8 flag (or put utf8:
yes in your conf file [req] section) and not prefix the string with an
identifier.
--
Principal Security Engineer
Akamai Technology
Cambridge, MA
Hi Walter,
Thanks for that, but I have tried those options also, I must be missing
something else?
commonName = UTF8String:Root
45:d=5 hl=2 l= 3 prim: OBJECT:commonName
50:d=5 hl=2 l= 15 prim: PRINTABLESTRING :UTF8String:Root
commonName = UTF8
But even if it isn't enabled in the BIOS, shouldn't the output be
something like this when you probe it (even if it isn't available or
enabled in BIOS, but openssl itself supports it)?
$ openssl engine
(aesni) Intel AES-NI engine (no-aesni)
(dynamic) Dynamic engine loading support
(I haven't bee
Hello John,
I had the same problem; the solution is just:
UTF8String or UTF8 and not UTF8STRING
Walter
On 14.03.2013 17:06, rasmu...@us.ibm.com wrote:
I'm using the following configuration file section in an attempt to
create a CA with UTF8 characters in subject (and other) fields.
string_m
I'm using the following configuration file section in an attempt to create
a CA with UTF8 characters in subject (and other) fields.
string_mask = utf8only
prompt = no
[ req ]
default_bits= 2048
default_keyfile = /opt/rasmussjCa/private/cakey.pem
So this is a partial continuation from the discussion thread that I
started yesterday in regards to using AES-CBC.
I've got an Intel Core i7 3930K that supports AES-NI and I spent the
greater part of last night trying to get openssl to work or at least
recognize it, but it doesn't seem to want to
hi,
you should check the .so or .a libraries with :
a) nm | grep HMAC
b) ar -l | grep HMAC
Bye
On Wed, Mar 13, 2013 at 8:27 PM, Mouad Djedidi wrote:
> Hello,
>
> I'm trying to install the *openpana* project (
> https://sourceforge.net/projects/openpana/) on my ubunto 12.40, which
> need th
I am not sure whether this mail even reached to the openssl-users
Regards,
Azhar
On Thu, Mar 14, 2013 at 11:01 AM, azhar jodatti wrote:
> Is this the right place to ask ? Please suggest
> -- Forwarded message --
> From: "azhar jodatti"
> Date: Mar 13, 2013 11:14 PM
> Subject:
2013/3/13 Mouad Djedidi :
> Hello,
>
> I'm trying to install the openpana project
> (https://sourceforge.net/projects/openpana/) on my ubunto 12.40, which need
> the openssl library. Although I have installed openssl correctly I keep
> having this message when I try to configure (./configure) openp
Hello,
I'm trying to install the *openpana* project (
https://sourceforge.net/projects/openpana/) on my ubunto 12.40, which need
the openssl library. Although I have installed openssl correctly I keep
having this message when I try to configure (./configure) openpana:
Error! You need to have ssl
19 matches
Mail list logo
