Giovanni Barillari
Giovanni Barillari
tbh, I don't see any actual security exposure here. Thus, given the code changes needed are definitely not trivial, at this stage this is a very low priority to me.
> As long as Granian has no (known) security issues (or anything that could be exploited) - this is not a problem. > > However, if something is found/introduced in...
@mollymorphous I'd say it's a nice feature to add. I won't say this would fit into 2.3 release – I'd like to have that out next week hopefully – but...
@mollymorphous fyi in the next few weeks I gonna start working on 2.4 (https://github.com/emmett-framework/granian/milestone/21). If you have any status updates, feel free to share. It's also fine to move the...
> I'm hoping to have some time to get to it towards the second half of this month. Maybe targeting 2.5 makes more sense? Yeah no rush :) I'll move...
@mollymorphous in the next weeks I'm going to work on 2.5 release. Do you have any status updates to share on this?
@mollymorphous good news! In regards of > Is this an issue in the context it's called from? we definitely want to keep that in place to prevent security attack vectors...
> My concern was that `Path::canonicalize` would block the worker thread while it was checking the file system. You're definitely right here, good catch. I'm not also sure whether the...
IPv6 support is now enabled on all of Sentry's ingestion endpoints 🚀
My _2 cents_: the 2 keys vs single tuple key won't really change that much, the latter just simplify the message parsing on the server side. I would say the...