Email Address Issue
-
@aaronstuder said in Mangolassi is leaking everyone's email address!:
@scottalanmiller @tonyshowoff I am not seeing emails anymore, just my own now.....
Confirmed, they're not there anymore, at least not in this request.
-
Seems to be fixed.....
-
Thanks for catching this, good work everyone tracking that down.
-
@scottalanmiller said in Mangolassi is leaking everyone's email address!:
Thanks for catching this, good work everyone tracking that down.
I'm not seeing it in any of the requests either, the long polling ones nor the ones from just scrolling down the page. I guess it's gone.
-
@tonyshowoff said in Mangolassi is leaking everyone's email address!:
@scottalanmiller said in Mangolassi is leaking everyone's email address!:
Thanks for catching this, good work everyone tracking that down.
I'm not seeing it in any of the requests either, the long polling ones nor the ones from just scrolling down the page. I guess it's gone.
Sigh of relief.
-
@scottalanmiller said in Mangolassi is leaking everyone's email address!:
https://community.nodebb.org/topic/8776/nodebb-email-exposure-bug
Why don't you make an actual bug report on the github?
https://github.com/julianlam/nodebb-plugin-gravatar/issues -
@JaredBusch said in Mangolassi is leaking everyone's email address!:
@scottalanmiller said in Mangolassi is leaking everyone's email address!:
https://community.nodebb.org/topic/8776/nodebb-email-exposure-bug
Why don't you make an actual bug report on the github?
https://github.com/julianlam/nodebb-plugin-gravatar/issuesProbably get a faster response from more people that way, it wasn't exactly a minor issue. I've reported things on github, they were ignored, then I emailed the owner and they were like "oh, I didn't see that." Doesn't look super active on github, if it was, I'd definitely say do that first.
-
Also tagging the developer @julian
-
-
-
-
@scottalanmiller did you report the reload bug yet?
-
@aaronstuder said in Mangolassi is leaking everyone's email address!:
@scottalanmiller did you report the reload bug yet?
I want to wait for 1.0.4 which is just about to drop before putting in a report on 1.0.3. Don't want to create noise if it is already addressed or just something in our code base download.
