Liu Gang even thought: "Did he find a loophole and secretly download the development team's code?"
If this were the case, he would not hesitate to come out and accuse the entire company of the vulnerability team stealing their development results, and threaten to resign to ask the company to fire this person!
"The occurrence of this problem is related to the input string, which is very random."
Meng Fei ignored the shock of everyone present, his eyes flashed with strange confidence, and he said while operating:
"But I found such a combination that can reproduce this problem 100%."
He entered the same sentence again, and sure enough, the input method got stuck again.
"Now I'll try to fix it."
After speaking, he opened the program directory "Program files" under the system, and then found the directory "MantisSoft" of the Mantis software.
Next is the intranet security "IntranetSecurity", and he found a file "Misnetgate.dll".
Mantis Software Intranet Security Gate is a dynamic library, and it is undoubtedly a product of Liu Gang and his team.
Open the file and you will see a large area of dense binary code. This is not source code, this is machine code.
In human eyes, this is just a bunch of meaningless numbers.
Programmers can understand machine code. But that would require taking thousands of pages of instruction manuals and looking them up one by one.
Can anyone remember the machine code for all the instructions? Maybe there is such a perversion, but in this conference room, it certainly doesn't exist!
What's more, remembering is useless. Instructions are just instructions. Without the specific execution logic and environment, they are nothing.
The final execution code compiled by Liu Gang and others has gone through various obfuscations and virtualizations to prevent it from being cracked.
Even if you, Meng Fei, know that there is a BUG here, can you find the correct modification point?
However, under his intensely questioning gaze, Meng Fei first backed up the file, then clicked the mouse and keyboard to modify several strings of numbers.
Can he understand machine code?
Of course not!
But he has the strongest BUG system. The program caught his eye, and it didn't take much for him to scan for bugs.
As for modifying the machine code, he can just change some bytes blindly.
Doesn't he want to change things if he makes random changes?
What does it matter if you change things for the worse? Just let the system be repaired instantly.
With so many people watching, no one could spot anything fishy?
Of course not.
What everyone sees is a bunch of numbers, and you have a quick eye and quick hands, so who can see clearly what you changed.
Save and restart your computer. Open it again and enter the same sentence.
Extremely smooth, no lag!
Meng Fei restored the backup file he had kept before the modification, restarted the system, and entered the same sentence again.
Sure enough, it stalled again!
Modify, test, problem solve.
Restore, test, problem reappears.
The ironclad evidence leaves no room for doubt.
Luo An, who was used to seeing too many big scenes, didn't have much shock on his face, but his admiration and satisfaction for Meng Fei was obvious.
Liu Gang, on the other hand, was so anxious that his face almost twisted.
He has completely failed in this matter.
No matter how serious the problem is, whether it is a BUG, or whether the vulnerability team has raised this problem and whether they have rejected changes.
Their problems caused users to complain, and when they were demonstrated on the spot in front of the big boss, he was completely defeated.
But Luo An didn't let it go and continued to ask Meng Fei:
"You said you mentioned this BUG before, but the development team refused to fix it?"
Meng Fei clicked the mouse and found an old email from four months ago.
Even Ouyang Cong admired him. How did you manage to tie things together over such a long time span and pull them all out to counterattack?
Of course he didn't know that Meng Fei had already prepared the system for one-stop service, from scanning for bugs to looking for user complaints and emails for pre-submitting bugs.
“The principle of this is actually very simple.
"Internal network security systems prevent programs from having untrustworthy access to the external network.
“And this input method will try to pop up advertisements when users enter certain strings.
“Advertising comes from many different sources.
“Most of these source URLs have been added to the trust list, so there will be no lag at all when typing text.
“But there are a very small number of advertising source URLs that are not in the whitelist and are blocked by the intranet security system.
“Originally, if the connection is directly interrupted, there will be no ads and the input will be normal.
"But the way our security system blocks it is not by interrupting the connection, but by hanging."
Hanging means it is blocked and there is no reply. You don't know if the road is open or not, you just know it's blocked. Then the input method has no choice but to wait.
It got stuck while waiting. It may take several seconds.
Normally, a few seconds of lag for other operations is acceptable. If there is a pause when typing text, it will feel like stammering, and the user will feel uncomfortable.
"A few months ago, when we were testing, we found that the way the security system blocked it was to hang, so we sent this email to the development team."
Meng Fei read out the content of the email: "The suspension method will cause unpredictable freezes and may affect the user experience. It is recommended to directly interrupt the connection."
"But there was no reply from the development team."
Meng Fei hammered the last nail on the coffin lid without mercy. There was silence.
In fact, Liu Gang was very wronged in this matter.
Suspend or interrupt is just a matter of strategy.
If it hangs, the connection is still alive and the program will not die. In theory, it is gentler than violent interruption.
You say it should be interrupted now, but who knows if weirder problems will arise under other circumstances after changing it to interruption?
The bug team only needs to ask questions and suggest improvements.
However, there is no need or control over whether this suggestion is feasible or whether releasing it will cause trouble.
After making modifications, is it not the development team itself that ultimately takes the blame?
Therefore, it is reasonable for their people to not reply directly after reading the email, or to reply with reasons and refuse to modify it.
But it's too late to say anything now. User complaints and on-site evidence are all in front of you.
The bug team raised the issue four months ago, accurately predicting the likelihood of user complaints, and they refused to fix it!
If he continues to debate whether he should interrupt or drop such an unanswerable topic, it will only make Luo An feel that he is irresponsible and unwilling to take responsibility.
"This is indeed our problem."
Liu Gang admitted defeat with a sullen face.
"In the future, I will supervise the development team's follow-up on reported bugs and ensure that every problem is properly resolved."
Luo An also nodded appreciatively:
"It's good if we can find the problem. Today's meeting took too long, so we'll end it here. Liu Gang, please go back and write down the minutes of the meeting and send out specific improvement measures in the future."
Luo An's style is like this, his joy and anger are invisible.
He never criticized anyone directly in front of everyone. This will make the person being criticized lose face and dampen their enthusiasm.
But the problems that should be solved must also be solved. It is useless to express determination. You must see concrete measures that can be implemented.
Mere measures are not enough. In the future, it will also depend on whether the measures are implemented and what the results are.
He will chase you like a wolf. Once you are targeted by him, you must either actively solve the problem or wait for him to solve you.
Liu Gang felt extremely stressed for a moment, so he packed up his things and left with the development team.
"Meng Fei, you stay."
Just when everyone was about to disperse, Luo An suddenly said something.
…
(This book is still in its early stages and urgently needs feedback from readers. If there are any problems, I still have time to revise them. If you are interested in helping me, you can add me on WeChat, 16191935)
