guanxingyun79

@guanxingyun79

9 Following

13 Followers

guanxingyun79 pfp

Good Morning. What good day.

3 replies

5 recasts

11 reactions

nthb.27 pfp

What’s a morning 😍

1 reply

2 recasts

3 reactions

guanxingyun79 pfp

0 reply

0 recast

0 reaction

guanxingyun79 pfp

0 reply

0 recast

0 reaction

Claireccc pfp

gm, my frens! Rumors say eth might go below $1000 . What do you think?

1 reply

0 recast

2 reactions

guanxingyun79 pfp

0 reply

0 recast

0 reaction

Claireccc pfp

GM Love is red Red is passion

3 replies

1 recast

4 reactions

guanxingyun79 pfp

1 reply

2 recasts

2 reactions

guanxingyun79 pfp

it is terry ！ why？ who will be responsible for it? https://x.com/cnnbrk/status/1904777545066700894

0 reply

0 recast

0 reaction

guanxingyun79 pfp

it is terry ！ why？ who will be responsible for it? https://x.com/cnnbrk/status/1904777545066700894

0 reply

0 recast

0 reaction

guanxingyun79 pfp

it gives many human hope!!

0 reply

0 recast

0 reaction

guanxingyun79 pfp

With chain abstraction and non-custody becoming the trend, UniversalX has huge room for growth. Backed by Particle Network, the future token airdrop is expected to be very impressive, and early users are likely to enjoy ecological dividends

0 reply

3 recasts

3 reactions

guanxingyun79 pfp

On April 26th, we detected an internal problem with the generation of the 21 characters. 2 out of the 3 random functions that we use in the code were not generating an authentic random sequence. It was possible to request a password change for a customer ID, and then find the "unique" URL emailed to the customer by brute force. The problem was found by an internal developer on April 26th at 11:03:14 and it was fixed at 12:54:13. The cause of the problem was linked to the rand function used in this part of the code. It was not patched to the same extent as the rest of the code at the time of activating the script execution cache. We have replaced the old function of 3 sequences to generate 21 characters with 2 authentic random functions to generate 64 characters.

0 reply

1 recast

1 reaction

guanxingyun79 pfp

We then ran searches on our databases to verify whether the loophole had been exploited and if so, when. We tracked the log of password changes for your IDs for the last 3 years. We actually have authorisation from the CNIL (the French data protection authority) to archive and exploit all our back office logs for the last 10 years, precisely for this type of situation.

0 reply

0 recast

0 reaction

guanxingyun79 pfp

If you still have 7 characters of entropy, that's 60^7 combinations. If the attacker hacked the account in one hour (as they claim), how did the attacker sent 777600000 requests per second for one hour without them noticing? One billion requests per second, that's not something you usually handle. Nor your servers, you would crash anytime.

0 reply

3 recasts

2 reactions

guanxingyun79 pfp

If you still have 7 characters of entropy, that's 60^7 combinations. If the attacker hacked the account in one hour (as they claim), how did the attacker sent 777600000 requests per second for one hour without them noticing? One billion requests per second, that's not something you usually handle. Nor your servers, you would crash anytime.

0 reply

3 recasts

2 reactions

guanxingyun79 pfp

We then ran searches on our databases to verify whether the loophole had been exploited and if so, when. We tracked the log of password changes for your IDs for the last 3 years. We actually have authorisation from the CNIL (the French data protection authority) to archive and exploit all our back office logs for the last 10 years, precisely for this type of situation.

0 reply

0 recast

0 reaction

guanxingyun79 pfp

On April 26th, we detected an internal problem with the generation of the 21 characters. 2 out of the 3 random functions that we use in the code were not generating an authentic random sequence. It was possible to request a password change for a customer ID, and then find the "unique" URL emailed to the customer by brute force. The problem was found by an internal developer on April 26th at 11:03:14 and it was fixed at 12:54:13. The cause of the problem was linked to the rand function used in this part of the code. It was not patched to the same extent as the rest of the code at the time of activating the script execution cache. We have replaced the old function of 3 sequences to generate 21 characters with 2 authentic random functions to generate 64 characters.

0 reply

1 recast

1 reaction

zhouzeqing pfp

Preparing to pull my former colleague into the fold, he’s the coding powerhouse of our department, getting him to help me with Monad’s script I gave a fierce demo of on-chain operations like a tiger, and after watching, he calmly said, “Writing it in Python is pretty simple” But I forgot about claiming the water, used a new wallet and messed around on the official site for ages without getting it, so embarrassing My new venture ended before it even started

0 reply

1 recast

1 reaction

zhouzeqing pfp

Preparing to pull my former colleague into the fold, he’s the coding powerhouse of our department, getting him to help me with Monad’s script I gave a fierce demo of on-chain operations like a tiger, and after watching, he calmly said, “Writing it in Python is pretty simple” But I forgot about claiming the water, used a new wallet and messed around on the official site for ages without getting it, so embarrassing My new venture ended before it even started

0 reply

1 recast

1 reaction