Does Jnode fall into the Default Permit trap?

I just discovered Jnode today and have been reading all about it. Its all very interesting how you did certain things. I am just wondering if Jnode will be the first operating system (that I know of) that will finally put an end to the issue of "Default Permit"

The basic idea is today's operating system allows by default any program to to run, do disk io, open sockets, etc.

You can read more about it here:
http://www.ranum.com/security/computer_security/editorials/dumb/

And btw, I hope you guys take a hint from Eclipse and try to make Jnode useable enough (not necessarily useable for general/public use) to start dev in itself ASAP! (Anything that is broken, you [i]will[/i] fix, since you are using it Eye-wink)

no default permission

Hi and welcome to JNode !

By default, JNode gives absolutely no permission. You must declare in each plugin the permissions that you give to the plugin's classes.

For eclipse, running it inside of JNode is one of my wish. But it's a long time goal since JNode and Classpath are not fully ready for running any Swing application.

Moreover, the widget components of eclipse (SWT) probably need to be ported to JNode.

Fabien

What about JNI?

What prevents somebody writing an Java app that called native assembly methods?

Wouldn't that allow full access to the computer?

(Sorry if that is a noob question, I'm trying to learn =)

Native code

Java apps cannot run native assembly methods, because they run inside a virtual machine that does not allow it.
JNode does not support native methods, except for a single class deep inside the VM.

Ewout

Having the open source

Having the open source license to IntelliJ(limited to the project members) we, for a start, don't have to port SWT to get a good IDE running under JNode.

Martin

also JBuilder

Martin,
I would like to add that JBuilder could also be used. Since it is using swing ... but not the next version, that may be based on eclipse and so on SWT.

Fabien

The Article

Thanks for the link, that's an interesting article. I think the hard thing about that is that the system needs to remain usable at the same time, without requiring home users to consult a system administrator when they downloaded a new application.

Sebastian