Melroy van den Berg
Melroy van den Berg
> I would appreciate if this is supported upstream as well. Me too that is why I created this pr. @ebassi @anholt somebody?
@trick77 Could you please merge this? It would help myself in the upcoming future again..
> Hey @melroy89 I think there is a problem with that PR. It currently removes the first rule in the INPUT chain, which may not always be the intended rule....
Ow sorry your Readme only saids to add the blacklist to top chain it seems.
The bad weather test was out-dated with IPFS v0.20.0, thus removed. Which already helped quite a lot with the `test_dht` test
I see, thank you for you remarks. Ideally you should use CMake, which interact very well with an existing CMake project. But I will test if `pkg-config` config you provided...
Yes so `zipper.pc.cmakein` is an input file for the `configure_file` of CMake, generating the final file. Which is exported to: `${PROJECT_BINARY_DIR}/zipper.pc`, so under the CMAKE [project binary directory](https://cmake.org/cmake/help/latest/variable/PROJECT_BINARY_DIR.html) with final...
I indeed got a "Scrapy denial of service vulnerability" CVE-2017-14158. But there is no fixed release, right?
Follow-up, PR: https://github.com/jekyll/jekyll-seo-tag/pull/481
You should be able to do this as well for tags & categories at the top of your markdown file, an example: ```yaml --- title: Post title example author: Melroy...