21–30 of 60 posts
In my firefox it looks like four "a"s with a little rat sitting on top of the first of them.
Same, I actually assumed that's what the string was supposed to be, now opening this in chrome I can see wildly different it looks
Fun story about one of the devices mentioned there that I worked on. We used to store the saved wifi creds in a file named exactly what the SSID was. Some user managed to break things, and with their permission we gathered detailed wifi logs and found they were connected to an SSID that was an ASCII depiction of the equation: [redacted] plus [redacted] equals [redacted]. The issue was the forward slashes, presumably…
Sounds like a directory traversal to me :) It's generally a bad idea to have the user in control of filenames you create if those files are not on a device they own.
In my firefox it looks like four "a"s with a little rat sitting on top of the first of them.
I've got some dirt on my screen. Be right back.
It's really crazy, looks completely different on my bsd-box compared to my linux-laptop LOVE IT!!
Earlier quoted context omitted.
Sounds like a directory traversal to me :) It's generally a bad idea to have the user in control of filenames you create if those files are not on a device they own.
In this case, it sounds like the files were on a device owned by the user?
Fun story about one of the devices mentioned there that I worked on. We used to store the saved wifi creds in a file named exactly what the SSID was. Some user managed to break things, and with their permission we gathered detailed wifi logs and found they were connected to an SSID that was an ASCII depiction of the equation: [redacted] plus [redacted] equals [redacted]. The issue was the forward slashes, presumably…
