Josh Pennell wrote:
> 
> A note on java security:
> 
> Well if your dealing with non-1.2 java security ie. applets and
> browsers, you can use the netscape capabalities api and IE's cab and
> sign technology to break out of the sandbox.  I've used them and they
> both work fairly well.

No, this will not work with Netscape because the Netscape capabilities
api requires that the calls are placed in the object requesting to break
out of the sandbox, and as this is one of the javax.comm objects, and
you do not have the source for that, you are out of luck.

-- S�ren

> 
> -Josh
> 
> Daniel Lintjens wrote:
> >
> > Jan Peter Hecking wrote:
> > >
> > > On Mon, May 10, 1999 at 11:57:27AM -0400, Daniel Lintjens wrote:
> > > > Well, I know OCF supports applets, but I haven't got any luck with it
> > > > though.
> > > > The ocf routines i have use the javax.comm library to access the com
> > > > port, and with the current implementation of javax.comm it is not
> > > > possible to do that in an applet under 1.2. It should be possible with
> > > > 1.1.7, but no luck on my side...it is a security problem, but applets
> > > > and security are a big jungle to me.
> > >
> > > Why is it that javax.com cannot be used in an applet under 1.2?
> > ok, get a good grip. You're not going to like this.
> > Sun apperently knows about this problem, and it will be fixed in the
> > next release. I'm not accusing anyone, but some voices say sun
> > dilibretly put the bug in there because at the time jdk1.2 wasn't
> > finished, and the security model wasn't stable yet. There is no mention
> > about this anywhere (-the not working under 1.2 applets part-) but after
> > extensive research I found a newsgroup which is only accesable using a
> > java program from the usnpages and the people there told me this was a
> > known bug. Took me like 5 weeks to figure it out, and made my boss very
> > happy (with Sun.)
> >
> > > I'm also trying to use OCF in an applet and I always get a weird
> > > NullPointerException that I can't figure out when I try to use the
> > > java-plugin for 1.2. It works with 1.2 and 1.1.6 when run as an
> > yep, sound all to familiar!
> >
> > > application. It also runs when run as an applet under 1.1.6. But then it
> > > fails with a SecurityException because I haven't had any luck with
> > > signing jar's with jdk1.1.6's javakey either.
> > > (javakey -gk Jan DSA 512 throws a NullPointerException)
> > same here, the 1.1.x security model is just uncomprihensible
> > at least to me it is, never got it to work, and never met people who got
> > it to work eighter.
> >
> > p.s. I found some other bug in javax.comm 2.0 (=latest version) ANYONE
> > who knows where to report this ? And don't start with try sun's page,
> > because I put 2 hours in searching where to report this (since it
> > doesn't fall under any "class" like jdk1.2, swing, awt, etc...
> > frustrating" an) and when I finaly got a mail adress it bounced back at
> > me! Sun isn't that popular here anymore ...
> >
> > Daniel
> > <><
> > Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
> > access to documentation, code, presentations, and OCF announcements.
> > -----------------------------------------------------------------------------
> > To unsubscribe from the OCF Mailing list, send a mail to
> > "[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
> > message.
> Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
> access to documentation, code, presentations, and OCF announcements.
> -----------------------------------------------------------------------------
> To unsubscribe from the OCF Mailing list, send a mail to
> "[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
> message.
Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
access to documentation, code, presentations, and OCF announcements.
-----------------------------------------------------------------------------
To unsubscribe from the OCF Mailing list, send a mail to
"[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
message.

Reply via email to