David Irvine | 1 Nov 17:39 2011
Picon

Re: RSA Key handling

Managed to find a method that works. It uses a combination of some of
the code found on the wiki (excellent addition to cryptopp). For
anyone interested here is the snippet of some helper functions. I hope
this helps, but also recognising that these should be used strictly
when serialising right out of the app, it's not advised to use strings
in the app. Even in this case memset the string to '0' is advised
after marshalling from what I can tell.

namespace {
 void EncodeKey(const CryptoPP::BufferedTransformation& bt,
std::string *key) {
    CryptoPP::StringSink name(*key);
    bt.CopyTo(name);
    name.MessageEnd();
}

 void Decode(const std::string& key, CryptoPP::BufferedTransformation
*bt) {
    CryptoPP::StringSource file(key, true /*pumpAll*/);
    file.TransferTo(*bt);
    bt->MessageEnd();
}

}  // Unnamed namespace

void EncodePrivateKey(const PrivateKey& key, std::string *priv_key) {
    CryptoPP::ByteQueue queue;
    key.DEREncodePrivateKey(queue);
    EncodeKey(queue, priv_key);
}
(Continue reading)

Nick Murdoch | 4 Nov 14:03 2011
Picon

Having trouble building pycrytopp 0.5.29 on Debian

Hi all,

I'm having trouble compiling pycryptopp 0.5.29 on a Debian sid box
with python2.5.

$ python setup.py build
running darcsver
setup.py darcsver: using extant version file ['pycryptopp/
_version.py', 'embeddedcryptopp/extraversion.h']
running build
running build_py
running egg_info
writing requirements to pycryptopp.egg-info/requires.txt
writing pycryptopp.egg-info/PKG-INFO
writing top-level names to pycryptopp.egg-info/top_level.txt
writing dependency_links to pycryptopp.egg-info/dependency_links.txt
reading manifest file 'pycryptopp.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'pycryptopp.egg-info/SOURCES.txt'
running build_ext
building 'pycryptopp._pycryptopp' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -
Wstrict-prototypes -fPIC -I. -I/usr/include/python2.5 -c
embeddedcryptopp/cryptlib.cpp -o build/temp.linux-x86_64-2.5/
embeddedcryptopp/cryptlib.o -w
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid
for Ada/C/ObjC but not for C++ [enabled by default]
embeddedcryptopp/cryptlib.cpp:33:26: error: uninitialized const
‘CryptoPP::g_nullNameValuePairs’ [-fpermissive]
embeddedcryptopp/cryptlib.h:321:20: note: ‘const class
(Continue reading)

Ott, David E | 8 Nov 22:10 2011
Picon

Upcoming hw RNG from Intel

Hi,

 

Wondering if the Crypto++ development team is familiar with Intel’s hardware-based digital RNG (DRNG) to appear early next year?

Essentially, it is a hardware RNG implemented on the processor chip, providing highly entropic output and with very low latency.  Since access is through a single instruction added to the Intel 64 instruction set, it’s also quite easy to use.  Its application, among other things, is cryptographic key generation.

 

Was thinking that it might  provide a robust seeding mechanism for the PRNG implementation in osrng.h, or perhaps a PRNG alternative when the library executes on a machine supporting the feature.

 

Note that it’s NIST SP800-90 compliant and FIPS-140-2 (level 2) certifiable.

 

Here are some links for additional information:

 

http://spectrum.ieee.org/semiconductors/processors/behind-intels-new-randomnumber-generator/?utm_source=techalert&utm_medium=email&utm_campaign=090111

http://software.intel.com/en-us/articles/download-the-latest-bull-mountain-software-implemenation-guide/

Note discussion by the Linux community and Linus Torvald's later comments at:

http://lkml.org/lkml/2011/7/29/353

 

Thoughts?

 

David Ott

 

--
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.

Arash Partow | 8 Nov 22:27 2011
Picon

Re: Upcoming hw RNG from Intel

On 09/11/11 08:10, Ott, David E wrote:
> Note discussion by the Linux community and Linus Torvald's later
> comments at:
>
> http://lkml.org/lkml/2011/7/29/353
>

That was a very entertaining read :)

--

-- 
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.

Alan | 14 Nov 00:08 2011
Picon

ECDSA Signing without Hashing

I have no problem creating Priv/Pub ECDSA key pairs, but it requires
me to specify a hash function as one of the template parameters.  If I
understand correctly, this is to provide a single operation for
signing a plaintext message.  The problem is that I need to use a
custom hashing algorithm, and would prefer to pre-hash the message
myself and apply the EC operations on that without any hash function.
But I just can't figure out how to do this!

Some ideas I have is:
--Define an ECP object with the curve parameters I need (just
secp256k1), and reimplement the signing algorithm using EC math (seems
ridiculous, though)
--Try to create a custom IteratedHashFunction object (just like
SHA256) which defines my hash function:  this looks complicated,
though and I know it's going to end up being a linking disaster even
if I could figure out how to define all the methods it needs
--Define/find an "identity" hash function to plug in for the template
parameter, then when the ECDSA object "hashes" it, it won't do
anything... which is fine because I already hashed it before I called
the signing method (seems like the best solution)

I hope someone here can help me figure out what is the best way to do
this.  So far, it seems unnecessarily difficult...

--

-- 
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.

Brad Tilley | 15 Nov 15:10 2011
Picon

Salsa20 Fails cryptest v

I wanted to pass this along. It does not impact me, but I thought it
might others. I'm running Debian 6 Testing and while installing Crypto+
+ from source (5.6.1) Salsa20 failed cryptest v. It was the only
failure to occur:

678 Salsa validation suite running...
679
680 Testing SymmetricCipher algorithm Salsa20.
681 ......incorrectly encrypted: 5E5E71F90199340...
682
683 Test failed.
684 Skipping to next test.
685 ....
686 Testing SymmetricCipher algorithm XSalsa20.
687
688 Tests complete. Total tests = 107. Failed tests = 1.
689 SOME TESTS FAILED!

g++ --version
g++ (Debian 4.6.1-15) 4.6.1

I simply unzip the source, run `make` and `cryptest v` as a normal
user and then `make install` as root. I'll be glad to provide more
details about my build environment if that will be helpful.

Brad

--

-- 
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.

Zooko O'Whielacronx | 27 Nov 21:40 2011

Re: Salsa20 Fails cryptest v

Hello Brad Tilley:

Thanks for the report.

Since the same problem hasn't been reported by anyone else, I wonder
if it was a sporadic problem on your specific system, such as a
hardware issue. Was the failure reproducible or sporadic?

Thanks!

Regards,

Zooko

On Tue, Nov 15, 2011 at 7:10 AM, Brad Tilley <kj4eit <at> gmail.com> wrote:
> I wanted to pass this along. It does not impact me, but I thought it
> might others. I'm running Debian 6 Testing and while installing Crypto+
> + from source (5.6.1) Salsa20 failed cryptest v. It was the only
> failure to occur:
>
> 678 Salsa validation suite running...
> 679
> 680 Testing SymmetricCipher algorithm Salsa20.
> 681 ......incorrectly encrypted: 5E5E71F90199340...
> 682
> 683 Test failed.
> 684 Skipping to next test.
> 685 ....
> 686 Testing SymmetricCipher algorithm XSalsa20.
> 687
> 688 Tests complete. Total tests = 107. Failed tests = 1.
> 689 SOME TESTS FAILED!
>
>
> g++ --version
> g++ (Debian 4.6.1-15) 4.6.1
>
> I simply unzip the source, run `make` and `cryptest v` as a normal
> user and then `make install` as root. I'll be glad to provide more
> details about my build environment if that will be helpful.
>
> Brad
>
> --
> You received this message because you are subscribed to the "Crypto++ Users" Google Group.
> To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
> More information about Crypto++ and this group is available at http://www.cryptopp.com.

--

-- 
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.

Zooko O'Whielacronx | 27 Nov 21:50 2011

Re: Salsa20 Fails cryptest v

Oh, look this is a known bug that has been fixed by Wei Dai in trunk:

http://sourceforge.net/apps/trac/cryptopp/ticket/12

Sorry for incorrectly saying that nobody else had reported it.

Regards,

Zooko

On Sun, Nov 27, 2011 at 1:40 PM, Zooko O'Whielacronx <zooko <at> zooko.com> wrote:
> Hello Brad Tilley:
>
> Thanks for the report.
>
> Since the same problem hasn't been reported by anyone else, I wonder
> if it was a sporadic problem on your specific system, such as a
> hardware issue. Was the failure reproducible or sporadic?
>
> Thanks!
>
> Regards,
>
> Zooko
>
> On Tue, Nov 15, 2011 at 7:10 AM, Brad Tilley <kj4eit <at> gmail.com> wrote:
>> I wanted to pass this along. It does not impact me, but I thought it
>> might others. I'm running Debian 6 Testing and while installing Crypto+
>> + from source (5.6.1) Salsa20 failed cryptest v. It was the only
>> failure to occur:
>>
>> 678 Salsa validation suite running...
>> 679
>> 680 Testing SymmetricCipher algorithm Salsa20.
>> 681 ......incorrectly encrypted: 5E5E71F90199340...
>> 682
>> 683 Test failed.
>> 684 Skipping to next test.
>> 685 ....
>> 686 Testing SymmetricCipher algorithm XSalsa20.
>> 687
>> 688 Tests complete. Total tests = 107. Failed tests = 1.
>> 689 SOME TESTS FAILED!
>>
>>
>> g++ --version
>> g++ (Debian 4.6.1-15) 4.6.1
>>
>> I simply unzip the source, run `make` and `cryptest v` as a normal
>> user and then `make install` as root. I'll be glad to provide more
>> details about my build environment if that will be helpful.
>>
>> Brad
>>
>> --
>> You received this message because you are subscribed to the "Crypto++ Users" Google Group.
>> To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
>> More information about Crypto++ and this group is available at http://www.cryptopp.com.
>

--

-- 
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.

Griffin Milsap | 27 Nov 21:54 2011
Picon

Re: Signature format (C++/Java)

I don't suppose you're still around and could post relevant code snippets from your working code... ?


I'm having the same problems at the moment, and I can't figure out how to fix 'em.

--
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.
ibiza | 28 Nov 15:37 2011
Picon

Crypto++ library dependency problem

Hi dear Crypto++ contributors,

I downloaded and built successfully the Crypto++ library.

If I look at it with depends.exe<http://www.dependencywalker.com/>, I
get this picture : http://i.imgur.com/bGjUy.png.

The "call hierarchy" to the problematic external module seems to be
(from
depends.exe) :

CRYPTOPP.DLL/ ADVAPI32.DLL/ USER32.DLL/ POWRPROF.DLL/ SETUPAPI.DLL/
USERENV.DLL/ GPSVC.DLL

In the Crypto++ source code, I noticed in osrng.h, there is a

#pragma comment(lib, "advapi32.lib")

I am on Win7 64bit and using the files here<http://sourceforge.net/
projects/cryptopp/files/≥ (latest version).

Anyone could help me understand why there is an unresolved external
module
from the DLL? I can't use it because of that.

Many thanks,
Bruno

--

-- 
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe <at> googlegroups.com.
More information about Crypto++ and this group is available at http://www.cryptopp.com.


Gmane