i have deleted your last “who can help me” posting for now. It is seen as bad netiquette to push a thread like this within a few hours without a response. Please have some patience and if some one knows an answer you should get an answer.
Thanks Jan. You said otp is a very old internal protocol between manager and scanner and It doesn’t solve the coding problem.I want to know why the otp protocol cann’t solve the coding problem in design.Can you tell me more about it? Thanks a lot!
I want to know whether the current GVM version supports UTF-8 coding. I wrote a third-party NASL in Chinese, which is displayed in garbled code on the page. I want to know whether there are any methods to solve it at present
I have queried the data in redis and can display Chinese normally. The problem is that after OpenVAS scanner reads the redis data, the resulting data is not normally encoded in UTF-8. Gvmd supports UTF-8 encoding. When my newly created NASL file is read to the database by gvmd, it will be garbled
Because I’m from NASL_ Debugsecurity_ The Chinese returned in the message method is in fprintf (stdout, “”% s \ \ n ", DUP) of OpenVAS scanner; I want to know how OpenVAS returns data to gvmd in the next step. Is there any coding problem in this process