Timeline for Is there a practical way to identify security vulnerabilities that were published following a full disclosure policy?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2016 at 18:08 | comment | added | signus | Thanks! Well the point is that independent members of the platform and/or community search for bugs and submit them, for which they are fully involved in the process to not only describe the problem (software bug or security vulnerability), but to help resolve the problem if they can). They probably only get pertinent information. Unfortunately I do not know of any such programs by name. | |
| Jun 28, 2016 at 16:39 | comment | added | AleVe | An awesome read indeed. Thank you! I've never been involved in a bug bounty program, do members really get first-hand (or let's say, extra) information about vulnerabilities found within the program? It surely varies among programs, but if yes, would you happen to know which ones? | |
| Jun 27, 2016 at 19:01 | history | answered | signus | CC BY-SA 3.0 |