Hi Wei and All,
I am experiencing problems with DSA key generation. For some reasons,
when I select the pair (2048 bit, 256 bit) as parameter size, only the
prime divisor q is of 256 bit, but the private key (x) is of 224 bit.
The other three values are ok. It does work properly with the other
Hi All,
I haven't received an answer, so I am giving it another try Does
anybody have a clue?
Ingo
-- Forwarded message --
From: Ingo Naumann cyberurc...@gmail.com
Date: Fri, Aug 13, 2010 at 3:44 PM
Subject: GDSA: Bit length of private key
To: Crypto++ Users cryptopp-users
Dear Michele,
How do you initialize the string variable Sign?
And, BTW, one comment on item 4) in your first mail. The command you
are using in your code is for signing a message. The message gets
hashed and then the RSA function is applied to this hash (simplified
explanation). In your case,
scheme use
SHA1...
Variable string Sign is the end of StringSink, i define it in class Sign
(chek my last post) and i initialize that so:
void SignHash()
{
DigitalSign = ;
}
Il giorno sabato 14 luglio 2012 18:47:49 UTC+2, Ingo Naumann ha scritto:
Dear Michele,
How do you initialize
Hi,
I'm trying to compile a c++ program that I inherited support of, and running
into some issues when trying to compile it on Mountain Lion, with XCode
4.4.1 installed, and g++ (gcc) v4.2.1.
$ g++ -arch x86_64 -I cryptopp -l cryptopp -o my_program.cpp
I'm not sure why you'd need '-l
In which directory does Cryptopp install the file libcryptopp.so.5.6? In
/usr/lib or in /usr/local/lib?
On 09/25/2017 06:40 PM, Richard Závodný wrote:
> I installed CPP using dnf (*cryptopp* package), that's all. Now i
> tried to build the library using guide on wiki page you posted, but
> still
Dear All,
I've just upgraded from an older version to Crypto++ 5.6.5 and my
Valgrind is seriously unhappy about it. Even the "cryptest.exe v"
command crashes with "Illegal instruction" (details on request) when
calling it with
valgrind --tool=memcheck --leak-check=full --show-reachable=yes
Hi,
Thanks a lot for your answer.
> I've just upgraded from an older version to Crypto++ 5.6.5 and my
> Valgrind is seriously unhappy about it. Even the "cryptest.exe v"
> command crashes with "Illegal instruction" (details on request) when
> calling it with
>
>
> []
> We
Hi,
>> You might be able to work around it by removing the `-march=native`
>> from CXXFLAGS. Open GNUmakefile and delete the line that adds it.
>> However, you will loose a fair amount of performance because the
>> source files depend on some of the options included in
>> `-march=native`.
Wo-ho!
