We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
General Issue.
Vuls imports some text data from Database such as NVD/JVN... and so on. But Vuls code is not normalize charset before parse or store to DB and so on.
The text was updated successfully, but these errors were encountered:
I think the default character code is UTF-8.
As for input, I seems deal with below.
As for output, When the data of go-cve-dictionary use UTF-8 or convert to UTF-8
-report-mail -lang=ja
Content-Type: text/plain; charset=utf8
Mail header require charset, because Sometimes the mail software can not identify the character code. Other report option seems to UTF-8.
I think, if the input charactor code is unified in UTF-8, output character code will be the default UTF-8.
Sorry, something went wrong.
I send pull request #280. It fix Content-Type header issue. The rest, output UTF-8 charset from go-cve-dictionary when Other multi byte country data.
No branches or pull requests
General Issue.
Vuls imports some text data from Database such as NVD/JVN... and so on.
But Vuls code is not normalize charset before parse or store to DB and so on.
The text was updated successfully, but these errors were encountered: