I wish I had found this earlier. Nothing like looking at thousands of EV charger logs all day to mak you appreciate something like this.
Log File Viewer for the Terminal
21–30 of 60 posts
Re: Log File Viewer for the Terminal
#22Super useful tool but need to be aware that this is reading potentially untrusted input (e.g. in the case of http request logs) and written in c++, so a possible attack vector. I use lnav where I trust the logs, but do wish a safe implementation existed.
Re: Log File Viewer for the Terminal
#23I'm a little disappointed that it's not written in Rust.
Re: Log File Viewer for the Terminal
#24> ssh playground@demo.lnav.org Really appreciate this way to demo it quickly, very nice!
Just be aware of the risks! https://security.stackexchange.com/questions/38128/what-are-...
Re: Log File Viewer for the Terminal
#25[dead]
Re: Log File Viewer for the Terminal
#26Super useful tool but need to be aware that this is reading potentially untrusted input (e.g. in the case of http request logs) and written in c++, so a possible attack vector. I use lnav where I trust the logs, but do wish a safe implementation existed.
Memory safety doesn't mean it's safe. And C++ doesn't mean it's unsafe.
Browsers are in C++, do you not use them? Curl is in C, do you not use it? Kernel is C...
Re: Log File Viewer for the Terminal
#27I'm a little disappointed that it's not written in Rust.
I sense an opportunity for you.
Re: Log File Viewer for the Terminal
#28Re: Log File Viewer for the Terminal
#29Re: Log File Viewer for the Terminal
#30Super useful tool but need to be aware that this is reading potentially untrusted input (e.g. in the case of http request logs) and written in c++, so a possible attack vector. I use lnav where I trust the logs, but do wish a safe implementation existed.
Memory safety doesn't mean it's safe. And C++ doesn't mean it's unsafe. Browsers are in C++, do you not use them? Curl is in C, do you not use it? Kernel is C...
Chrome uses sandboxing and a lot of safe tooling (wuffs, rust) for untrusted data.
curl is heavily fuzzed and you still mostly control what you are downloading unless the target is compromised.
With logs the attacker controls what goes into your logs.
And you don't need to really look very hard, there are a fair number of very recent stack and heap overflows: https://github.com/tstack/lnav/issues?q=is%3Aissue%20heap%20...