-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Create rule "Windows services or other local OS services" #8
Comments
For Java JNI, override rules from community |
For windows file path and DLLs, related existing rule: https://github.com/windup/windup-rulesets/blob/master/rules/rules-reviewed/azure/azure-os-specific.windup.xml |
I believe this rule is about the Java application communicating with an existing process in running in the background, on the OS. This can be done with things like IIOP or localhost HTTP (which is covered in a different ruleset). You may want to look at IIOP and/or RMI. Another solution is D-BUS. This is substantially different than issue #10 where it talks about launching an external process. |
We have the following rules already:
For CORBA, shall we just look for For DBus, would we just look into https://www.freedesktop.org/wiki/Software/dbus ? I don't know if this is the right place |
We can look for CORBA and then close this issue. DBus for after the MVP. |
CORBA PR is on its way: windup/windup-rulesets#1008 I've created a DBus issue for after the MVP: #113 |
It is a best practice for applications running in Azure App Service or Azure Kubernetes Service to be self-contained and not depend on OS-level services. Service Control Manager access is disallowed in the App Service sandbox. Some users install custom Windows services which is not possible in Azure App Service environments and not recommended in containers. Although Java apps are unlikely to interact with Windows services, they should generally not interact with local Linux services.
For .NET, identifying this metadata is possible by looking for use of the System.ServiceProcess namespace.
PRs
The text was updated successfully, but these errors were encountered: