Re: [cryptopp-users] TOTP implementation

2023-11-04 Thread Arik Agazarian
We Need wallet address of 7 months for clean transactions, traceable on Blockchain, Ratio 45%/45%/10% Sender/Reciever/Mandate Telegram sender: @Arik_loader On Thu, Nov 2, 2023, 7:23 PM Catherine Issabel wrote: > > $500 million dollars available only for good and trusted receiver or > mandate >

Re: [cryptopp-users] TOTP implementation

2023-11-02 Thread Catherine Issabel
$500 million dollars available only for good and trusted receiver or mandate Kindly contact the sender for more information:+1 (336) 345-9681 On Friday, August 4, 2023 at 6:28:39 PM UTC+1 phamba...@gmail.com wrote: > Also, their version of Base32Decoder uses DUDE instead of RFC 4648. > > On

Re: [cryptopp-users] TOTP implementation

2023-08-04 Thread phamba...@gmail.com
Also, their version of Base32Decoder uses DUDE instead of RFC 4648. On Friday, August 4, 2023 at 2:14:12 PM UTC+1 Steven Green wrote: > Shouldn't... > > * hmac.Update(byteArray, sizeof(byteArraySize));* > > be simply.. > > > * hmac.Update(byteArray, byteArraySize); * > > Otherwise you passing in

Re: [cryptopp-users] TOTP implementation

2023-08-04 Thread Steven Green
Shouldn't... *hmac.Update(byteArray, sizeof(byteArraySize));* be simply.. *hmac.Update(byteArray, byteArraySize); * Otherwise you passing in sizeof(size_t) rather than the size of the byteArray (which is sizeof(uint64_t)). Although on a 64 bit system I would expect them both to be 8 bytes,

[cryptopp-users] TOTP implementation

2023-08-03 Thread Aravindh B
Need to get some information how counter value is handled in this library. std::string generateTOTP(const std::string& secretKey) { using namespace CryptoPP; const int timeStep = 30; // Time step in seconds SecByteBlock key(HMAC::DEFAULT_KEYLENGTH); StringSource(secretKey, true, new