@charliesome is this a real statement? none of it makes sense to me.
-
-
Replying to @lstoll
@lstoll prepare to be amazed:https://github.com/ImageMagick/ImageMagick/blob/master/coders/url.c#L194 …1 reply 1 retweet 5 likes -
Replying to @charliesome
@charliesome current google searchpic.twitter.com/eQljRWaUvQ
1 reply 2 retweets 3 likes -
Replying to @lstoll
@lstoll@charliesome well, it has to be able to handle external entities somehow.. XML is sooo beautiful :)1 reply 0 retweets 1 like -
Replying to @sghctoma
@sghctoma@lstoll@charliesome No, external entities are a bug. Any xml impl that supports them is nothing but a toy. Not deployable.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@lstoll@charliesome Ext. entities are part of the XML spec. Arguably a bad design decision, so yeah, it could be called a bug..1 reply 0 retweets 0 likes -
Replying to @sghctoma
@RichFelker@lstoll@charliesome +AFAIK ever major XML lib supports them. a few were opt-in, the majority opt-out 2 years ago, IDK about now1 reply 0 retweets 0 likes -
Replying to @sghctoma
@sghctoma@lstoll@charliesome Support should be completely removed, not just opt-in. The "feature" (external entities) is broken by design.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@sghctoma@charliesome because everyone sure loves it when software authors ignore standards and do what they want.1 reply 0 retweets 0 likes -
Replying to @lstoll
@lstoll@sghctoma@charliesome In principle you're right, but if you follow that principle here, xml is a useless std. Nowhere safe to use.1 reply 0 retweets 0 likes
@lstoll @sghctoma @charliesome Same is true of some legacy RFCs like SMTP. They specify behaviors that are inherently insecure. Must ignore.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.