|
|
|
|
|
by ohyeshedid
1637 days ago
|
|
I don't have a link handy, nor currently familiar with LP's site or extensions: The part of the site that shows the recent connections to your account, with IP's. People were sharing those IP's and thoughts in the linked thread. That data came from somewhere; if it's related to this bug then this bug is also pushing incorrect data into other parts of the service. It's also entirely possible that it wasn't a bug, and instead a security issue, and that data is correct, and they're bending words to play it off as just a bug. I can understand a bug triggering a warning system, but when it's also presenting related data in the account security logs; it's either a complicated bug or there's more to the story. |
|
I showed you pseudo-code which could trigger this issue. It was trivial code which could cause it in practice. Yet you claim it must be complicated or more to the story. I have no idea why you feel that classifying a request in a certain way must be caused by a complicated bug - very strange.
I think you're into FUD-mode now because even after being shown wrong, you continue to spread misinformation.
Also, you are referring to LP functionality which to my knowledge doesn't even exist, and when asked you say you don't know the software being discussed.
Very strange behavior by you.