Re: how to apply gnuplot_fixed to octave 2.9.16 MSVC

[Tatsuro MATSUOKA]

Hello Michael

It seems to be deep problem.

You doubt that the securities problem.
It is NO.

I know securities problem warining when wgnuplot is executed directly.
See the following the snapshot.

http://www.geocities.jp/tmoctwin/files/0711119.html 

Sorry two shots are written in Japanese.

The first waring appeared when I first time executed a cvs wgnuplot from

http://www.ring.gr.jp/pub/text/TeX/ptex-win32/utils/gnuplot-43pl0w32.zip

and it was able to exectuted normally after proper treatment.
What you would like to say this kind of warning?

For your binary, the second snapshot appeared.
This is not secutity waring but application execution error.
It might be a bug of the my windows but it was never secuty issue.

> In summary, I think this problem will disappear when gnuplot will
> be bundled with the binary package and installed normally with
> the installer.

I hope so.  However it will not be so, how will you treat the issue?

Anyway I will wait for your next version with hope.

Tatsuro

--- Michael Goffioul <address@hidden> wrote:

> On 11/18/07, Tatsuro MATSUOKA <address@hidden> wrote:
> > Hello Michael
> >
> > I again thought about this issue. This is not an easy problem to treat.  If 
> > you will bundle
> > (w)pgnuplot in gnuplot_fixed.zip in the next release of MSVC-Octave, there 
> > are certian amount
> of
> > people who will not able to gnuplot as graphic backend.  So this problem 
> > will be hopefully
> fixed.
> 
> Indeed, I plan to ship the "fixed" gnuplot with the next binary release of
> octave. I'm not going to support 2 versions of gnuplot, mainly because
> (besides additional work) the previous version just does not work with
> any plot requiring a colormap.
> Honestly, I doubt the problem you have is linked to the changes I made
> to gnuplot, which resumes to using
> 
>     fread(&c, 1, 1, stdin);
> 
> instead of
> 
>     ReadFile(_get_osfhandle(fileno(stdin)), &c, 1, &cRead, NULL);
> 
> I don't see how such change would make an executable not-runnable with
> the error message you get (both versions of gnuplot have been compiled
> on the same system, with the same compiler and the same flags...).
> 
> I might be wrong, but I still think the problem is related to security: an
> .exe file installed regularly with an installer can be executed without
> any problem, while an .exe compiled on another computer that is
> simply uncompressed from a zip file cannot be run for security
> reasons (at least without any specific action from the user). This is
> how I interpret the warning dialog I see on my system when I try
> to run the decompressed pgnuplot.exe, while on your system it
> might turn directly into an error, because you have higher security
> settings than me.
> In summary, I think this problem will disappear when gnuplot will
> be bundled with the binary package and installed normally with
> the installer.
> 
> Michael.
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www.cae.wisc.edu/mailman/listinfo/help-octave
> 


--------------------------------------
New Design Yahoo! JAPAN  2008/01/01
http://pr.mail.yahoo.co.jp/newdesign/