CRYPTO NEWS

Is it safe to "compress" an IV in AES256-CTR?

Alice is using AES256 in CTR mode to send encrypted messages to Bob. The messages are 4 byte values. Along with each encrypted message, Alice sends along a random 16 byte IV. f maps a 4 byte value v to the 16 byte values v|v|v|v (concatenates it with itself 4 times). Would it be secure for Alice to randomly generate 4 bytes s, encrypt her message using IV = f(s) and send Bob the encrypted message along with s (assuming Bob uses the same f to recompute the IV on his end)?

How can i listen emitted event faster on ETH

i try to listen any movement from a contract, it’s working but i receive the result above 40sec after the block is minted. But on BNB chain i receive the information instantly but on ETH it’s take so long time. MyContract.events.allEvents() .on(‘data’, (event) => { console.log(event) }) Do you have any idea to get the::Listen

i try to listen any movement from a contract, it’s working but i receive the result above 40sec after the block is minted. But on BNB chain i receive the information instantly but on ETH it’s take so long time.

MyContract.events.allEvents() .on('data', (event) => {     console.log(event) }) 

Do you have any idea to get the info instantly, is it from my node of something else ? Thanks !!

Is it safe to "compress" an IV in AES256-CTR?

Shopping cart
There are no products in the cart!
Continue shopping
0