UAC && Java applet

  • Thread starter Thread starter wb
  • Start date Start date
W

wb

not sure how one can get really granular in allowing certain java apps to run
without having to fully turn off UAC.

after an auto update of java my users cannot run a certain java app now
without turning off UAC for the user. i can see the java app in the terminal
debug window and the problem being perm/access.

so how does one in Vista allow certain apps under this security policy
without turning off UAC for the user?
 
wb said:
not sure how one can get really granular in allowing certain java apps to
run
without having to fully turn off UAC.

after an auto update of java my users cannot run a certain java app now
without turning off UAC for the user. i can see the java app in the
terminal
debug window and the problem being perm/access.

so how does one in Vista allow certain apps under this security policy
without turning off UAC for the user?
Click to expand...
Try asking other Sun Java users:
http://forums.sun.com/forum.jspa?forumID=32 . Maybe the Java application has
to be modified.
 
There is a platform SDK security newsgroup. If they don't help it is likely
because the question is easily answered by reading the documentation. So
read the documentation if possible and if you don't get help there, ask in
the programmer's security newsgroup. In this newsgroup (the one this thread
is in) and this question, you are more likely to get sarcasm than answers.

Your program should check for errors whenever there is a possibility of
errors. Probably if you are thorough enough in checking errors, you would
have an idea of what the problem is. Security people will say that instead
of attempting to provide more privileges for the program, you must eliminate
the need for more privileges unless the requirements of your application
needs the additional privileges. Security programmers will insist that you
determine why the program requires Administrator privileges or whatever, so
unless I misunderstand what you are saying you should do something to
diagnose the problem instead of concluding you must allow the program to do
whatever it decides to do.

What if your program got infected by malware? It would not be your fault
except your customers will likely blame you anyway for allowing the malware
to do it's thing. Even if that is not the case now, it is the type of thing
that can happen by solving problems by guessing.

If you are thinking that you can't diagnose the problem because the error
exists only in other systems but not in your system, then you need to learn
about debugging and diagnosis; you are not the first to be in that
situation.
 
I believe this is a profile issue (possibly something under HKCU). I'd
recommend trying to create a new Windows profile for the users.
 
Back
Top