<div dir="ltr">Security sensitive issues are marked as security sensitive, which means that only the reporter and core team members can view the issue. However, as it's all open source someone can monitor commits and figure out exploits that way.<div><br></div><div>Once we have a supported version of Keycloak ready we'll have a channel to distribute patches to customers prior to disclosing any details and code to the community.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 May 2016 at 01:23, Brian Watson <span dir="ltr"><<a href="mailto:watson409@gmail.com" target="_blank">watson409@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey all,<div><br></div><div>I love the fact that your backlog is very transparent, and that I can see a list of all tasks completed for a given release.</div><div><br></div><div>However, I was wondering how you handle tasks for compromising bugs? For instance, one could look in the backlog for a bug that states "If you send '123' to the master realm token endpoint at precisely 6:59am on a Tuesday, and you will be granted an admin token! Please Fix!", and use that information to gain access to the systems of those using Keycloak.</div><div><br></div><div>Thank you in advance.</div></div>
<br>_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br></blockquote></div><br></div>