However, if I am reading this correctly, your PoC falls in the category described here: https://react2shell.com/
> Anything that requires the developer to have explicitly exposed dangerous functionality to the client is not a valid PoC. Common examples we've seen in supposed "PoCs" are vm#runInThisContext, child_process#exec, and fs#writeFile.
> This would only be exploitable if you had consciously chosen to let clients invoke these, which would be dangerous no matter what. The genuine vulnerability does not have this constraint. In Next.js, the list of server functions is managed for you, and does not contain these.
Context: This is from Lachlan Davidson, the reporter of the vulnerability
This sounds like a great idea for a feature for the OP. Cool feature to kickstart the database. Take a photo. Something something AI. 150 rows filled in
Seems like general good advice, but for me it was simply a matter of `atuin import auto`. The initial response was similar (as in, here is no history, where is my history, this is useless). Then I read this page where it said to import, which seemed relevant:
The description of the repo is "A compendium of absurd "open-source" licenses." Which I think is relevant to change the title to (the addition of the word "absurd" specifically.
The word "bad" is also used several times, and can be argued is also useful to put in the title
This made me think of http://prose.io which I remember was a thing 10 years ago. Pleasantly surprised it still is a website, not sure if it still works. But I remember the basic idea being similar, except Jekyll only.
You can pull the images by simply switching from using docker pull ubuntu:16.04 to docker pull public.ecr.aws/docker/library/ubuntu:16.04. We automatically push images to ECR Public when they are updated on Docker Hub so you will get all the latest releases wherever you pull from.
You can pull the images by simply switching from using docker pull ubuntu:16.04 to docker pull public.ecr.aws/docker/library/ubuntu:16.04. We automatically push images to ECR Public when they are updated on Docker Hub so you will get all the latest releases wherever you pull from.
Replying to myself. I guess I read that a bit too quickly:
> In Node.js, the answer involves a WebSocket to TCP socket proxy, Asyncify, and patching deep PHP internals like php_select. It's complex, but there's a reward. The Node.js-targeted PHP build can request web APIs, install composer packages, and even connect to a MySQL server.
I did know of those, I'm just assuming its going to cause some sort of problem with network calls and sockets and what not (they mention this specifically as part of the caveats)
> There's another thing that really split the community, many want automatic security updates to Drupal core, but the Drupal core devs have taken a hard stance against this.
That might have been true at some point, but certainly is not the case anymore. In fact, automatic updates is a "strategic initiative" for Drupal core:
This still means there is no out of the box way to update Drupal core automatically _yet_, but you can in fact do so with a contributed project, developed and maintained by people that are contributing to the core initiative.