For my README.md, BitBucket reports "This file contains invisible Unicode characters that have been substituted and highlighted. Executing code that contains these invisible characters can have unexpected and malicious results." The only highlighted area is at the end of the file shows '<U00a0>' which is a no-break space, and comes at the end of a footnote just before a link back to the footnote in the text - `<a class="footnote-backref" href="#fnref:1" title="Jump back to footnote 1 in the text">↩</a>`.
My guess is that the Markdown parser that BitBucket uses to render footnotes is putting that Unicode equivalent of ` ` before the backlink, and AFTER that happens, BitBucket runs the 'check for potentially malicious invisible Unicode characters' plugin.
This doesn't harm anything, but it is demonstrably a false-positive warning.
I recommend either moving the Unicode check to before the Markdown render, or whitelisting the offending Unicode character U00a0 in the Unicode checker, or change the setting of the Markdown renderer to avoid emitting characters that will trigger the malicious Unicode checker.
Same thing is happening now in our README.md files. You've just recently released an update that broke our formatting in README files. How do we disable this functionality?
Hi @osep_redmine,
Welcome to the community and thank you for reaching out!
I have reached out to the development team regarding this issue, I will let you know as soon as I have an update.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @osep_redmine and @marius.guscius ,
Our development team has deployed on production a fix for this issue.
Could you please let me know if the issue is resolved for you?
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the update and you are very welcome!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.