TheAssassin
TheAssassin
(Disclaimer: AppImage project maintainer and long-time PrusaSlicer user here.) The issue appears to be related to three facts: - a) Prusa decides not to bundle WebKit - b) WebKit >=...
This is probably a bug in LXQt. But it could be caused by us flushing the icon cache, so I'm willing to share some of the blame. Nevertheless, this shouldn't...
@TobiGr I think we need a more permanent solution at some point because it just broke again (and was fixed automatically, apparently). We use the automated DNSSEC feature of our...
I also don't see how this could be exploited on our page.
Please demonstrate an attack vector that does not depend on user-provided content.
Sorry, but you still have not demonstrated that this is in any way relevant to us. Letting "AI" generate security "fixes" just doesn't work yet.
This potentially copies many unrelated files into the AppDir. I don't see an improvement in this approach.
Apparently, this AppImage uses a nonstandard runtime. It claims to be compatible with type 2, but tools like appimagelint cannot easily analyze it therefore. It does not seem to use...
So this AppImage is using [uruntime](https://github.com/VHSgunzo/uruntime), a third-party runtime. Internally, it is using [DwarFS](https://github.com/mhx/dwarfs), which libappimage has no support for. This explains why AppImageLauncher cannot work with it. A quick...
Is it necessary to close this issue? I don't think so. I'd like to keep this feature request around.