-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run Velociraptor in Deno ^1.13.0 #75
Comments
@umbopepato @c4spar Will the fix be as simple as removing this line? If yes, I'd be happy to send a PR! velociraptor/src/scripts_config.ts Line 200 in cf89005
|
Hey @sant123, thanks for reporting! Does one of your scripts use the @paambaati right, |
Hey @umbopepato, you can execute Edit: deno install -qAn vr https://deno.land/x/velociraptor@1.0.1/cli.ts So looking at the installer in my $PATH I encountered this:
#!/bin/sh
# generated by deno install
exec deno run --allow-read --allow-write --allow-net --allow-env --allow-run --allow-plugin --allow-hrtime --quiet 'https://deno.land/x/velociraptor@1.0.1/cli.ts' "$@" So the workaround for everybody having this issue is re-installing velociraptor: deno install -qfAn vr https://deno.land/x/velociraptor@1.0.1/cli.ts After that execute Now running the cat command you will see the flags being updated #!/bin/sh
# generated by deno install
exec deno run --allow-read --allow-write --allow-net --allow-env --allow-run --allow-ffi --allow-hrtime --quiet 'https://deno.land/x/velociraptor@1.1.0/cli.ts' "$@" And velociraptor works again without issue 😁 |
Definitely the |
@umbopepato |
Since this issue has been resolved and there's already a pull request to change allow-plugin for allow-ffi. I'm closing this one. |
Thank you so much @paambaati and sorry for the delay in merging your PR, your changes are now live in |
The change introduced in flags by $ deno run -A https://code.velociraptor.run upgrade |
Native plugins have been removed denoland/deno#10908.
So executing this command will raise an error:
vr
The text was updated successfully, but these errors were encountered: