Re: ASL Kernel (grsec) breaks Plesk Licence Key Update (SOLV
Posted: Fri Oct 29, 2010 8:39 pm
I do not know the /path/to/dangerous/application. The only information about this is contained above.
Parallels will not assist with changes to ASL config. It is not their job.
I have already re-opened the Parallels Support Ticket ticket after disabling TPE. This is the "next step" and, as you can see, Parallels have recommended "load usual stock kernel instead of art's kernel." I would have to ask them /path/to/dangerous/application and then let them try again. What will the next thing be that I must disable? I do not want to lose their assistance at this stage. I cannot keep making minor changes and then send them off to try again, make another minor change, etc, etc.
Where are the "many other ASL users who also use Dr. Web?" They are not a part of this topic. Please read the topic subject ((SOLVED) = it is not! btw) I am a server administrator with basic server administration skills. I am not a server security expert. I want affective server security and effective server antivirus. I do NOT want server security that is so effective that it disallows other important programs (like antivirus) to run. There will be many people out there who want the same thing - who are not server security experts. If they were to stumble upon this post, it may assist in their "layman's" assessment regarding your product purchase or their desicion to use the ASL kernel.
I have invested 2 months of my time and money to arrive at the point where we are now. I will not be paying US$225.00, as you have quoted, to solve this problem. I will not be spending any more time and I will be selecting the quickest solution from this point.
The quickest solution seems to be "load standard kernel" and I wonder how complicated this is and can I manage this myself?
Because the other alternative is to ask you if you know the /path/to/dangerous/application OR ask Parallels for the /path/to/dangerous/application then run the command and wait to see what the next kernel-related issue is. I do not want to lose Parallels support in this process when they say the issue is clearly "grsec"
Parallels will not assist with changes to ASL config. It is not their job.
I have already re-opened the Parallels Support Ticket ticket after disabling TPE. This is the "next step" and, as you can see, Parallels have recommended "load usual stock kernel instead of art's kernel." I would have to ask them /path/to/dangerous/application and then let them try again. What will the next thing be that I must disable? I do not want to lose their assistance at this stage. I cannot keep making minor changes and then send them off to try again, make another minor change, etc, etc.
Where are the "many other ASL users who also use Dr. Web?" They are not a part of this topic. Please read the topic subject ((SOLVED) = it is not! btw) I am a server administrator with basic server administration skills. I am not a server security expert. I want affective server security and effective server antivirus. I do NOT want server security that is so effective that it disallows other important programs (like antivirus) to run. There will be many people out there who want the same thing - who are not server security experts. If they were to stumble upon this post, it may assist in their "layman's" assessment regarding your product purchase or their desicion to use the ASL kernel.
I have invested 2 months of my time and money to arrive at the point where we are now. I will not be paying US$225.00, as you have quoted, to solve this problem. I will not be spending any more time and I will be selecting the quickest solution from this point.
The quickest solution seems to be "load standard kernel" and I wonder how complicated this is and can I manage this myself?
Because the other alternative is to ask you if you know the /path/to/dangerous/application OR ask Parallels for the /path/to/dangerous/application then run the command and wait to see what the next kernel-related issue is. I do not want to lose Parallels support in this process when they say the issue is clearly "grsec"
)