Hi everyone,
I'm trying to write a CGI program to generate timestamps for the
Authenticode(TM) digital signature system.
I'm having trouble extracting the original ContentInfo from the timestamp
request (the ContentInfo is required to generate a valid reply). Since the
requests are
Your ASN.1 looks a lot like what I am sending in my own signing
tools (developed independently from the sf project you mention).
I ran your example request through Peter Gutman's dumpasn1 with
my old config file, and here is the output, which looks like the
same requests I generate (no
Hi
Thanks for your valuable suggestion. I didn't understand some points
which you described in the previous posting, may because of my lack of
exposure to the socket technology.
I have tried one more method to read the data from the socket, which was
partially successful it is
Hello again.
I'm reading these documents and I've seen that the IO struct for these
is the BIO struct.
My idea is do something like following (I've generated rsa_public.key
with genrsa):
$ openssl rsautl -encrypt -in legible_file -pubin -inkey
rsa_public.key -out encrypted_file
But in my
Hi Tim,
Thank you very much. I moved forward using your suggestion. But again Iam stuck
at one point.
(1) Iam facing problem in creating my specific .so. Iam having error:
ld: fatal: relocation error: R_SPARC_H44: file ssl/s2_meth.o: symbolunknown:
relocations based on the ABS44 coding model
Thanks for your help, Jacob.
Where can I find your signing tools? A quick Google search
revealed no useful links.
Alternatively, can you suggest me how to complete the original
ASN.1 structures so as to add the explicit [0] tag? I have already
searched the official OpenSSL documentation for
any takers from the openssl team? true, false? known issue, user error?
anything?
On 10-08-17 04:23 PM, Jeff Saremi wrote:
I apologize if this shows up more than once. I've been having problems
sending emails out, all day.
First I encountered this with valgrind but then I decided to have
Raj wrote:
I have tried one more method to read the data from the socket,
which was
partially successful it is defined as follows
do
{
dwReadDataLen = SSL_read(Serverssl,pBuff,iBufferSize); // Gets
the
data from the server side
