That is ok, the pull request for the bug did not come until August. And then, it needs to be reviewed for security, because right now it is too aggressive protecting the user data, and we rather err on the side of safety, than have a security hole in our hands.
Miguel On Mon, Sep 22, 2014 at 11:24 AM, Edward Ned Harvey (mono) < edward.harvey.m...@clevertrove.com> wrote: > > From: Miguel de Icaza [mailto:mig...@xamarin.com] > > Sent: Monday, September 22, 2014 9:50 AM > > > >> We've had a pull request outstanding > >> since April https://github.com/mono/mono/pull/1004 > > > > Perhaps the best thing to do is to file a companion bug, and raise the > priority > > of that bug to "major" whenever a patch is available, to trigger a > review. > > This one has been sitting around since April. I don't have access to > raise the priority. > https://bugzilla.xamarin.com/show_bug.cgi?id=19274 > > We had to implement a workaround into our product for customer release, to > workaround this issue. >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
