Handling exceptions

2017-12-02 Thread zavodnyrichard
Hello guys. I'm here again. How can I handle exceptions? I have app that string file with RSA. If the key is bad, my application fall, and I want change the app behavior, that the app will not fall, but only show error message. Right now app returning *InvertibleRSAFunction: computational

[cryptopp-users] Re: Hashing, encrypting, basically everything failing to build, except AES::DEFAULT_KEYLENGTH print to the console

2018-05-06 Thread zavodnyrichard
ld CryptoPP: download CryptoPP source code (from website) -> > open cryptest.sln -> Retarget solution (to use my version of Windows SDK - > 10.0.16299.0) -> Ok -> Batch Build -> tick cryptlib - Release|Win32 -> Build > > > cryptopp-test.cpp: > > > https://gis

[cryptopp-users] Re: CMake force linking to dynamic (FIPS) library, instead of static

2018-05-06 Thread zavodnyrichard
Fixed at https://groups.google.com/d/msg/cryptopp-users/4mZ5EZMIkeI/7-fSPZWSBQAJ On Thursday, May 3, 2018 at 7:04:49 PM UTC+2, zavodny...@gmail.com wrote: > > Let me explain my problem. I wanted implement hashing function into my > project but compiler throw me lot of errors, so I wrote this

[cryptopp-users] Re: Hashing, encrypting, basically everything failing to build, except AES::DEFAULT_KEYLENGTH print to the console

2018-05-06 Thread zavodnyrichard
-> tick cryptlib - Release|Win32 -> Build > > > cryptopp-test.cpp: > > > https://gist.github.com/zavodnyrichard/f51ec376cda91c9732ac822bab26189b#file-cryptopp-test-cpp > > > CMakeLists.txt: > > > https://gist.github.com/zavodnyrichard/f51ec376cda91c

[cryptopp-users] Re: Hashing, encrypting, basically everything failing to build, except AES::DEFAULT_KEYLENGTH print to the console

2018-05-01 Thread zavodnyrichard
gt; > open cryptest.sln -> Retarget solution (to use my version of Windows SDK - > 10.0.16299.0) -> Ok -> Batch Build -> tick cryptlib - Release|Win32 -> Build > > > cryptopp-test.cpp: > > > https://gist.github.com/zavodnyrichard/f51ec376cda91c9732ac822bab26189b

Re: [cryptopp-users] Hashing, encrypting, basically everything failing to build, except AES::DEFAULT_KEYLENGTH print to the console

2018-05-01 Thread zavodnyrichard
Actually I don't think problem is in CMake but somewhere between the linking process (when running msbuild cryptopp-test.sln) or building the library. Can you confirm that building the library this way: download CryptoPP source code (from website) -> open cryptest.sln -> Retarget solution (to

[cryptopp-users] Hashing, encrypting, basically everything failing to build, except AES::DEFAULT_KEYLENGTH print to the console

2018-05-01 Thread zavodnyrichard
://gist.github.com/zavodnyrichard/f51ec376cda91c9732ac822bab26189b#file-cryptopp-test-cpp CMakeLists.txt: https://gist.github.com/zavodnyrichard/f51ec376cda91c9732ac822bab26189b#file-cmakelists-txt $cmake .. https://gist.github.com/zavodnyrichard/f51ec376cda91c9732ac822bab26189b#file-cmake $msbuild

[cryptopp-users] Re: Hashing, encrypting, basically everything failing to build, except AES::DEFAULT_KEYLENGTH print to the console

2018-05-01 Thread zavodnyrichard
DK - > 10.0.16299.0) -> Ok -> Batch Build -> tick cryptlib - Release|Win32 -> Build > > > cryptopp-test.cpp: > > > https://gist.github.com/zavodnyrichard/f51ec376cda91c9732ac822bab26189b#file-cryptopp-test-cpp > > > CMakeLists.txt: > > > https://gis

[cryptopp-users] Re: Hashing, encrypting, basically everything failing to build, except AES::DEFAULT_KEYLENGTH print to the console

2018-05-03 Thread zavodnyrichard
299.0) -> Ok -> Batch Build -> tick cryptlib - Release|Win32 -> Build >> >> >> cryptopp-test.cpp: >> >> >> https://gist.github.com/zavodnyrichard/f51ec376cda91c9732ac822bab26189b#file-cryptopp-test-cpp >> >> >> CMakeLists.txt: >&

[cryptopp-users] CMake force linking to dynamic (FIPS) library, instead of static

2018-05-03 Thread zavodnyrichard
Let me explain my problem. I wanted implement hashing function into my project but compiler throw me lot of errors, so I wrote this question . However it firstly doesn't seemed to be problem of CMake, but after Jeffrey

[cryptopp-users] Re: Undefined reference to BufferedTransformation

2018-01-15 Thread zavodnyrichard
Any toughts? Dne sobota 13. ledna 2018 14:20:36 UTC+1 zavodny...@gmail.com napsal(a): > > Does anybody know why I'm getting this error? > https://pastebin.com/YeGA4dgN > > I just want make fingerprint of a file and put it into string. > CryptoPP::SHA256 sha256Hasher; > > CryptoPP::FileSource

Re: [cryptopp-users] Re: Undefined reference to BufferedTransformation

2018-01-17 Thread zavodnyrichard
Still the same. I tried to uninstall *cryptopp* and *cryptopp-devel* packages, then do *dnf clean all*, then install the packages back and still the same error. The problem is somewhere in this line: CryptoPP::FileSource createFileFingerprint(filePath.c_str(), true, new

Re: [cryptopp-users] Re: Undefined reference to BufferedTransformation

2018-01-15 Thread zavodnyrichard
What you mean by "entire build process"? I have installed CryptoPP from Fedora repos (5.6.3), then for build I do *g++ main.cpp -o main -std=c++17 -lcryptopp*. Nothing more. I don't use CMake and Make for this program yet. The error I get is pasted on Pastebin. Also, I want apology for my

Re: [cryptopp-users] Re: Undefined reference to BufferedTransformation

2018-01-13 Thread zavodnyrichard
5.6.3 from Fedora repo. Dne sobota 13. ledna 2018 16:39:15 UTC+1 Marcel Raad napsal(a): > > Am 13.01.2018 14:29 schrieb : > > Using the G++ option *-lcryptopp*. The program will compile if I keep the > *CryptoPP::SHA256 > sha256Hasher;* and comment the FileSource. > > >

Re: [cryptopp-users] Undefined reference to BufferedTransformation

2018-01-13 Thread zavodnyrichard
The same error when trying to hash string using *StringSource*. Dne sobota 13. ledna 2018 14:23:30 UTC+1 Marcel Raad napsal(a): > > Am 13.01.2018 14:20 schrieb : > > Does anybody know why I'm getting this error? > https://pastebin.com/YeGA4dgN > > I just want make

[cryptopp-users] Re: Undefined reference to BufferedTransformation

2018-01-13 Thread zavodnyrichard
The entire command to compile my project is *g++ main.cpp -o main -std=c++17 -lcryptopp*. *-Wall* option, show nothing. Dne sobota 13. ledna 2018 16:39:06 UTC+1 Jeffrey Walton napsal(a): > > > > On Saturday, January 13, 2018 at 8:20:36 AM UTC-5, zavodny...@gmail.com > wrote: >> >> Does anybody

[cryptopp-users] Re: Undefined reference to BufferedTransformation

2018-01-13 Thread zavodnyrichard
Oh sorry... If i add the *-Wall* option it show nothing more. I still getting the same error as I pasted into Pastebin. Dne sobota 13. ledna 2018 20:04:39 UTC+1 Jeffrey Walton napsal(a): > > > > On Saturday, January 13, 2018 at 11:42:22 AM UTC-5, zavodny...@gmail.com > wrote: >> >> The entire

[cryptopp-users] Re: Undefined reference to BufferedTransformation

2018-01-13 Thread zavodnyrichard
Using the G++ option *-lcryptopp*. The program will compile if I keep the *CryptoPP::SHA256 sha256Hasher;* and comment the FileSource. Dne sobota 13. ledna 2018 14:20:36 UTC+1 zavodny...@gmail.com napsal(a): > > Does anybody know why I'm getting this error? > https://pastebin.com/YeGA4dgN > >

[cryptopp-users] Undefined reference to BufferedTransformation

2018-01-13 Thread zavodnyrichard
Does anybody know why I'm getting this error? https://pastebin.com/YeGA4dgN I just want make fingerprint of a file and put it into string. CryptoPP::SHA256 sha256Hasher; CryptoPP::FileSource createFileFingerprint(filePath.c_str(), true, new CryptoPP::HashFilter(sha256Hasher, new

How to generate AES key if I can't use std::byte since I can't use C++17?

2018-01-02 Thread zavodnyrichard
Hi. I want cross-compile my project, that use CryptoPP using [MXE](http://mxe.cc/) (MinGW). The problem is *std::byte*, which is C++17 functionality. Since MXE only supports C++11 I need some alternative. The key generation and encryption looks something like this: byte key[32];

Re: [cryptopp-users] Wiki offline

2018-10-13 Thread zavodnyrichard
Can't confirm it. The wiki is still down. On Friday, October 12, 2018 at 6:16:43 AM UTC+2, jackso...@gmail.com wrote: > > Right on, working now. Thanks! > > On Thursday, October 11, 2018 at 9:14:12 PM UTC-7, Jeffrey Walton wrote: >> >> On Fri, Oct 12, 2018 at 12:02 AM wrote: >> > >> > Noticed