Sussen is a GNOME2 client for the Nessus Security Scanner Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 12917 [details] sussen 0.2 ebuild
Created attachment 12922 [details] sussen-0.2 ebuild (fixed version) The last version had a typo in the workiing directory for building the source. That has been corrected.
Created attachment 12923 [details] sussen-0.2 ebuild The last version had a typo in the workiing directory for building the source. That has been corrected.
Created attachment 12981 [details] sussen-0.2-r1.ebuild Had a DEPEND on gconf-1.2, but it should have been gconf-2. My bad.
you don't need to versionbump proposals it needs to use the gnome2 eclass, gconf-1.2 is probably just fine. if ssl is optional hardcode the switch if it's possible (don't depend on autodetection). can you make those changes ?
Created attachment 12994 [details] sussen-0.2-r2.ebuild - ebuild now inherits gnome2 - ssl is not optional, changed the dependency - left the GConf2 depend, as I'm pretty sure it needs 2.x. - in src_install (): added call to gnome2_src_install
Created attachment 12995 [details] sussen-0.2-r2.ebuild Attached the wrong ebuild. D'oh :)
I bumped the version on the ebuild anyway, sorry. I'll let you rename it, rather than upload another version. Bugzilla is probably getting tired of my attachments :)
when you use gnome2 eclass you should be able to drop parts of the ebuild (src_install src_compile) look at other gnome2 ebuilds.
Created attachment 12998 [details] sussen-0.2.ebuild Dropped un-necessary parts of ebuild due to gnome2.eclass
Created attachment 13386 [details] sussen-0.3.ebuild new version of sussen released.
Created attachment 13988 [details] sussen-0.4.ebuild new version of sussen released - added dependencies on mysql and gnet-2 to ebuild
Created attachment 15570 [details] sussen-0.5.ebuild sussen-0.5 ebuild
Does anyone actually read these reports? Are we just wasting our time making these ebuilds?
We have at this time a very small team with a lot of packages to take care of, we are reluctant to add packages right away without proper review (which isnt the easiest thing with sussen i think) since we also are comitted to properly maintaining them afterwards. Every package we add adds to the burden. We read the reports, but there's a lot of reports to read for us. No you are not forgotten, please be patient and thank you for updating the ebuilds trough this time. I really hope we can add this soon. Is there anyone one on the gnome@g.o CC who can test this application btw ? Now back to the ebuild, at least the gnomedb dep should contain a version number. The other deps should be sharper i think (quick ChangeLog check). It probably also needs some buildtime deps like pkgconfig . Since it needs nessus, shouldnt that also be a runtime dep (not sure if it needs it to build) ?
Created attachment 15738 [details] sussen-0.5.ebuild updating depends in ebuild
Thanks for getting back to me. I updated the ebuild to put in the version number for libgnomedb. I also was more explict in the depends with packages/versions. I also added pkgconfig and gettext. As far as Nessus goes, Sussen depends on Nesssus like Evolution depends on a mail server. There is no build dependency on Nessus anymore, I've removed and/or re-wrote all the Nessus code in Sussen. By the way in terms of testing, we are developing Sussen under Gentoo and we test against Gentoo before each release. So you shouldn't have much/any trouble getting it going. If you do find anything let us know.
Created attachment 15740 [details] sussen-0.5.ebuild added RDEPEND section to ebuild.
Created attachment 15741 [details] sussen-0.5.ebuild Forgot a quote in my last ebuild update.
i'll take this one if i can foser, i think i'll actually have some use to test it with thanks.
Loren: feel free to correct me in anyway you see fit, but I've download the 0.5.tar.gz twice (fearing corruption) and in both instances, make bombs out with: driver@zen sussen-0.5 $ make make: *** No rule to make target `m4/codeset.m4', needed by `aclocal.m4'. Stop. I had a brief look in your CVS tree and indeed I did see codeset.m4 in m4/ but alas, it's missing from the tarball. Whether this is sussen end or my end, would you mind having a quick check, because it's going to be hard to test for portage without compiling. I've also fixed up your ebuild, only slightly as it was generally of good quality, which I'll post as soon as this build issue is sorted out. So if you could please check the tarball and/or Makefile for the missing file thanks, after that I'll get on with the ebuild.
Hey Mike, Yup that was bug. I've updated the m4/Makefile.am and put in the missing files. I tested it out on another Gentoo box and it's now working. Thanks for letting me know! Anyway, I've released sussen 0.5.1. I just uploaded it to SourceForge. So just bump your .ebuild up a version and you should be good to go. Let me know if anything else comes up.
Created attachment 16051 [details] sussen-0.5.2.ebuild sussen 0.5.2 ebuild
Never heard back if 0.5.1 worked or not. Let me know about 0.5.2.
okay, i guess this sort of twists the bug report concept around. i've got the 0.5.2 ebuild installing fine. i've setup mysql + use gnome-database-properties to add a datasource that i can access (using the test functionality in there works fine). however on launching sussen i'm just told. warning: failed to load external entity "/home/driver/.sussen/backend.xml" libgnomedb/libgda were both rebuilt with USE="mysql" and they seem to be working okay. not sure what step i've missed, but i can't see any doc to help me anywhere, could you please fill me in on what actually needs to be done to get it up and running. i've allready done install db+libgnomedb+libgda. setup db. add datasource to libgnomedb. thanks.
Sounds you ran Sussen previously and it's got only part of a configuration. Try and delete /home/driver/.sussen and re-run the program. The README mentions mentions doing this if you used a previous version. On startup Sussen checks for the existance for .sussen to determine if this is the first time it's run. It's possible the directory got created by not all the config files were created. The file in question ~user/.sussen/backend.xml tells Sussen what DSN, username, and password to use when starting up. If sussen can't parse the file/connect to this, it informs the user and quits. Did you go through the 'Getting Started' druid? The 2nd step of it allows you to either select a current DSN or create a new one. You shouldn't have to go outside Sussen to create a DSN anymore (unless you want to). See screenshot: http://sussen.sourceforge.net/sussen-17.png In 0.5.3 (or whatever the next release ends up being) if it can't connect on startup it will pop up a GnomeDbLoginDialog widget to make things more user friendly.
yep, i'd deleted my ~/.sussen left over from my previous version (which i had the same problem with). in the getting started druid i get "Getting Started" -> "Nessus Server Information" -> "Sussen has the necessary information to proceed" -> (click apply) -> Error box: "fatal: Unable to make connection to database backend". I found away around this, if I go all the way through to "Sussen has the necessary info..." and then go <- Back instead of Apply, I get taken to the "Database Information" druid window. So for some reason, it skips straight from "Nessus Server Info" -> "Got all settings", bypassing the "Database Info" step. Can you have a look at why it would be doing that? aside from that, I now have sussen working, but we'll need to get this sorted out before it goes into portage. Thanks.
What version of the Gtk+/Gnome are you using? Also what CFLAGS did you use to compile Sussen? I've seen this happen under RedHat 9, but not Gentoo. Apart from my main devlopment box running Gentoo, I've tested it on two other boxes I have here and all of them display the druid correctly. All my Gentoo boxes are running ~x86 with Gnome/Gtk+ v2.2.2 installed. The code in Sussen for the druid looks fine to me. Basically when you click "Next" on page1 of the druid (Server Information) the code is: Get server information Save server information Set next page to database config call gnome_druid_set_page() to change the page One other thing you can try if you don't mind, if you go into the file sussen-getting-started-druid.c in the sussen source and go to line 299. You should be in the function gs_page1_next(), and on line 299 you'll see this function call: gnome_druid_set_page (GNOME_DRUID(the_druid),GNOME_DRUID_PAGE (next_page)); Insert this line before it and then re-compile Sussen: gnome_druid_set_show_finish (GNOME_DRUID(the_druid), FALSE); Let me know if that fixes it for you.
i'm running gtk+2.2.1-r1 and gnome2.2.2. unfortunately that change didnt fix it, so i'm not sure where the problem is. CFLAGS are just -march=pentium4 -O3 -pipe. i've tried with gtk+2.2.2-r1, and also with -O2, and the problem still occurs. i think we need an extra tester to check this, or try and reproduce it in some way.
Created attachment 16097 [details] getting started druid modified sussen-getting-started-druid.c to stop it from skipping pages.
I'm compiling with "-march=pentium3 -O3 -pipe -fomit-frame-pointer". We seem to have the same versions of software/libraries. If it didn't work on my systems, I'd be inclined to think it was a GNOME bug. I'm using their API and if you call gnome_druid_set_show_finish() and it still shows the end page that's a broken API call. But since it does work on my boxes that can't be the case or if should fail for me as well. I found one thing that might be an issue. I went over my code again and in the GNOME documentation it says that the handlers for "previous"/"next" should be returning a boolean (TRUE/FALSE) value. I wasn't doing that. I've created a new attachment to this bug which is a modified version of sussen-getting-started-druid.c. Can you try compiling with that and tell me if it works or not. Thanks.
I tried my fix on a RedHat 9 box and it worked. If you tell me it works for you, I'll release this version as sussen 0.5.3. Let me know ASAP. Thanks.
(looks like we had a "mid air collision" .. both posted at the same time, here's mine) okay, that definitely fixed my wizard problems, which is great. however now, when i go to connect, i enter my username/password, and click "Login", then sussen spits out: "invalid protocol" to the terminal, and freezes. running it through gdb, it looks like it's segfaulting. i've attached the bt which might help. sorry if it seems like all i do is pick up problems :/, but i actually really would like to get this in and start using it, that's why i'm trying to resolve these issues.
Created attachment 16104 [details] the backtrace for sussen 0.5.2
I got caught in a blackout so I haven't been able to get to this until now. Anyway, regarding the "Invalid Protocol" message, did you disable SSL support on the nessusd as per the README? (putting ssl_version = none into nessusd.conf) Also can you confirm you are using Nessus 2.0.7 as that we the only version we have been testing against. I re-wrote all the networking in Sussen to use the GNet library. That doesn't currently support SSL, though it's being worked on. As soon as they put it out, we'll renable it in Sussen. If you did disable SSL support and are using Nessus 2.0.7 can you send me your nessud.conf because I can't reproduce it with those steps. Thanks for helping get rid of the bugs btw!
okay, was definitely my fault, i hadnt disabled ssl support. i've added an einfo message to the end of the sussen ebuild to remind people about this. looks like we're almost good to go, so i'll endeavour to get it in this afternoon. thanks for your help (and sussen is very cool, well done).
Glad to hear you got it working. I'll release sussen 0.5.3 shortly then. I'd do it now , but I'm still having some Internet access issues due to "Blackout 2003" or whatever the CNNMBCNCFOXABC is calling it now. I'll let you know as soon as I manage to get through to sourceforge.net and make the release. Thanks again for your help.
Okay I figured a work around to my access issues and I managed to get Sussen 0.5.3 uploaded/released to SourceForge. Everything should be ready now for whenever the Sussen ebuild appears in Portage. Let me know if there are any more problems. Thanks.
okay, well was a long bug but got there in the end. thanks for your help on this one, there was a fair bit of back and forward. 0.5.3 is in now and i'll keep up to date with the versions on gnome-announce-list.
That's great thanks. If you have any problems going forward let us know as well, either through SourceForge or just email us (sussen@starchamber.ca) and we'll do whatever we can to help.
