• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Porting windows app to OS X and it's extremely huge as a result
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Porting windows app to OS X and it's extremely huge as a result


  • Subject: Re: Porting windows app to OS X and it's extremely huge as a result
  • From: Platon Fomichev <email@hidden>
  • Date: Sun, 25 May 2008 04:12:49 +0400

Greg,

It looks like you're trying to catch me on something? No way - it seems you've overestimated things

First - Java applet can download code from the host (Applets are not allowed to open network connections to any computer, except for the host that provided the .class files)
Second - in corporate environments it is common to install so-called SecurityManagers that can check and provide a specific applet a specific permission.
Third - Java has gzip stream from JRE 1.3 (and in corporate environments MS JVM based on 1.1.8 is still used)
Fourth - I said sandboxing 'like' Java Applet because many other sandboxes do exist - in fact even IE in Vista tries to sandbox its browsing module f.ex, thus my sandbox may be absolutely different from Java


And sure I may have my reasons not to tell the whole picture because of my own motifs which are just by the way much simpler and purer that you might expect.

Best regards,
            Stauff__

If you're running a sandboxed Java applet, then I don't see how you could download and execute ANY native code at all. Java's sandbox is expressly designed to prevent this.

At the very least, you need file-system access of SOME kind in order to write an executable file, i.e. the code compiled by gcc that you said is too big. You can't load anything directly into memory and execute it. The Java applet would then need to be signed in order to perform a Runtime.exec() call. That should be an unavoidable prerequisite, and if it's not, then you have a security flaw.

This is such a vast gap, an unsigned Java applet vs. native code compiled by gcc, that I suspect there's something fundamental you're not telling us. As you've described things so far, it just doesn't make sense. Or to be more precise, the only way it makes sense is if you are exploiting a security hole.


And for completeness, Java has gzip stream decompression that requires no special security, i.e. is available to unsigned applets. See the classes in java.util.zip whose names start with GZIP.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: Porting windows app to OS X and it's extremely huge as a result
  • Next by Date: Re: Porting windows app to OS X and it's extremely huge as a result
  • Previous by thread: Re: Porting windows app to OS X and it's extremely huge as a result
  • Next by thread: debugging offscreen graphics
  • Index(es):
    • Date
    • Thread