You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 25, 2024. It is now read-only.
Again, same point as before. ncurses-rs does not do any processing on top of just handing data to/from ncurses.
However, I appreciate your intention and I don't want to leave people using ncurses-rs thinking (and apparently knowing nothing about ncurses) that this could possibly be a safe library, so I've added the following: a52dbb3
I would be open to a PR marking all of the appropriate fns unsafe, but not any more PRs or issues around making ncurses-rs do anything more than its purpose. There are safer TUI libraries for Rust; hell, there are far safer TUI libraries for C, even.
This is a memory safety problem, since many functions in the rust stdlib are UB if you have a non-utf8 string.
These functions should be changed to ensure that only valid utf8 is input.
See rustsec/advisory-db#106, although it's unclear if there's a way for this to be exploitable (unlike the others).
The text was updated successfully, but these errors were encountered: