DO NOT REPLY [Bug 29501] New: - creates a new pop-up
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=29501. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=29501 creates a new pop-up Summary: creates a new pop-up Product: Fop Version: 0.20.4 Platform: HP OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I am running my fop on a HP box with iplanet. the web page has 2 frames. the 1'st frame has links to other pages. the second frame if used to display the contents of jsp's and fop generated pdf files. step 1) i click on a button that shows me the pdf document using fop. step 2) i go to a different page using the links in frame 1. step 3) i click on the browser back button and try to return to the pdf page. the pdf is not visible (because the history.go(-1) will not send a request to the iplanet server). PROBLEM: --- if i click on any one of the links, a new browser window pops open with the link page. a new window should not open. this is a bug.
CVS vulnerabilities?
I don't know who this should go to (they probably already know), but according to Reuters[1], the CVS system has some fairly significant holes. I know Forrest moved to SVN not too long ago. Have we thought of doing it ourselves? Web Maestro Clay [1] http://news.com.com/More+flaws+foul+security+of+open-source+repository/ 2100-7344_3-5229750.html?tag=macintouch
Re: CVS vulnerabilities?
There's a big push within Apache to adopt Subversion, and I suppose it will get to us in the near future. However, if we go there, I don't think it would be for this reason primarily. What are the security vulnerabilities of SVN? Nobody knows yet, and SVN has not been targeted. At least there is a major focus on security issues now with CVS. You could ask on [EMAIL PROTECTED] about the security status of Apache's CVS server and the relative security of SVN. All CVS updates are SSH tunnelled, AFAIK. Peter Clay Leeds wrote: I don't know who this should go to (they probably already know), but according to Reuters[1], the CVS system has some fairly significant holes. I know Forrest moved to SVN not too long ago. Have we thought of doing it ourselves? -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
