Re: [Openvas-discuss] OpenVAS and Cygwin
On Montag, 2. Juni 2008, John Chajecki wrote: I have found that OpenVAS uses the Cygwin1.dll. Its in C:\Program Files\OpenVAS-Client\bin but its version 0.132 as opposed to verson 0.156 installed in C:\cygwin\bin. Replacing the file in C:\Program Files\OpenVAS-Client\bin with the one in C:\cygwin\bin seems to fix the problem. Fine, so this solves the probem. Is there any way of making OpenVAS use the already installed Cygwin? The installer needs to be made more clever. However, I'd like to switch from InnoSetup to NSIS eventually, so I hesitate to put work into InnoSetup. Maybe I find the time to switch to NSIS and add the cygwin test for the next release. Ideally, I'd like to have a native cross compilation environment and get rid of cygwin. Fully automized including the packaging, i.e. type make OpenVAS-Client.exe on a Linux mashine :-). But that'll take 2 or 3 extra days which I can not afforf ATM. Best Jan -- Dr. Jan-Oliver WagnerIntevation GmbH, Osnabrück Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/ Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] OpenVAS and Cygwin
Jan, I don't know whether this is a general problem of two Cgwin applications or OpenVAS build method. All I know is that when Cygwin is loaded (and I don't need to lanuch any Cygwin applications either) OpenVas won't launch. The reverse is also true. If I open OpenVAS first, then Cygwin won't run. The error I get in Cygwin (and I have to type it out because there seems to be no copy and paste in Cygwin - sigh!) is: 7 [main] ? (3856) C:\cygwin\bin\bash.exe: *** fatal error - system shared memory version mismatch detected - 0x75BE0084/0x8A88009C. This problem is probably due to using incompatible versions of the Cygwin DLL. Search for cygwin1.dll using the Windows Start-Find/Search facility and delete all but the most recent version. The most recent version *should* reside in x:\cygwin\bin, where 'x' is the drive on which you have installed the cygwin distribution. Rebooting is also suggested if you are unable to find another cygwin DLL. The Cygwin installation is vanilla so there should be no issues with multiple versions of DLLs lying around. If I shut down OpenVAS and start Cygwin, then it starts fine. I have found that OpenVAS uses the Cygwin1.dll. Its in C:\Program Files\OpenVAS-Client\bin but its version 0.132 as opposed to verson 0.156 installed in C:\cygwin\bin. Replacing the file in C:\Program Files\OpenVAS-Client\bin with the one in C:\cygwin\bin seems to fix the problem. Is there any way of making OpenVAS use the already installed Cygwin? _ John Chajecki Senior Infrastructure Engineer Information Division Resources Department Leicester City Council Jan-Oliver Wagner [EMAIL PROTECTED] 31/05/2008 20:19 On Thursday 22 May 2008 02:26, Tim Brown wrote: On Wednesday 21 May 2008 13:54:19 John Chajecki wrote: 1. The OpenVAS client seems to clash with with Cygwin and refuses to launch when Cygwin is active. We have installed OpenVAS client 1.0.3 on Windows. Not sure about that, I would wait and see what other people say on the subject. Jan is often a good bet since he builds the Windows client. I've heard about this type of problem once, quite a long time ago. IIRC, the Cygwin versions clashed somehow. Is this a general problem of two cygwin applications on the same machine or more a specfic problem of the OpenVAS build method? 2. We downloaded the manua but we can't read it. It seems to be written with something called LyX. We have downloaded LyX and we now have a pretty LyX associated with users-manual.lyx but when we click on it nothing appeared to happen. About 5 minutes later however, a web browser like window suddenly opened up on the desktop with the manual displayed. I realise this may be a LyX issue, but why can't the manuals be written in a common file format like html or PDF rather than some obscure format that no one has heard of (yes - I have asked around!)? In fact the PDF manual should open up if you click the respective menu item in the OpenVAS-Client GUI. The markup format we use for the manual is LaTeX. This is a pretty common, open format which is heavily within the science and technology community. Having said that, it's main use here is to allow the generation of HTML and PDFs from a single source. Maybe it would be worth updating the relevant packages to generate one of those formats as part of the distribution process. I think it's a fair point that end users shouldn't have to rely on having LyX (or another LaTeX editor) installed to use OpenVAS. Thoughts anyone? Well, currently LyX is only needed for modifying the manual. Just reading, a PDF viewer is sufficient. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/ Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
[Openvas-discuss] can not login to openvas server
hi! i try the today svn versions. when i try to login with the client and only user:pw (without ssl) i get: on the server [20295] gnutls_handshake: A record packet with illegal version was received. and on the client remote host is not using the good version of the nessus communication protocol (1.2) or is tcpwrapped with ssl enabled on the client i get: login failed user and pass are 100% correct. thanks for any hint! with friendly greetings, christian ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
[Openvas-discuss] Prototype for OID-to-NASL mapping web interface online
Hi, we've put a OID to NASL script mapping online as discussed for Change Request #1. It is simply so far. A URL like this: http://www.openvas.org/?oid=1.3.6.1.4.1.25623.1.0.61039 resolves to the SVN trunk version of the respective NVT. After all, the links applied in the PDF reports (since OpenVAS-Client release 1.0.3) will now lead to a helpful information. Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/ Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] can not login to openvas server
On Monday 02 June 2008 16:19, christian gattermair wrote: i try the today svn versions. when i try to login with the client and only user:pw (without ssl) i get: on the server [20295] gnutls_handshake: A record packet with illegal version was received. and on the client remote host is not using the good version of the nessus communication protocol (1.2) or is tcpwrapped that is absolutely OK. OpenVAS has no option to run without SSL. The SSL switch in the client is only available for compaibility with Nessus which allow for unencrypted use. Perhaps we should simply remove this option. Unencrypted connection has no real use-case IMHO. Other opinions? with ssl enabled on the client i get: login failed Should not happen. user and pass are 100% correct. That would have been my first guess :-) thanks for any hint! on which operating system (and which version, any other special things) did you try this? What does the log files of openvasd say? Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/ Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
