Bug 426364 - nessus-update-plugins appears to be missing
Summary: nessus-update-plugins appears to be missing
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nessus-core
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-20 14:57 UTC by Vic Ricker
Modified: 2011-09-07 19:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-17 02:56:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 273241 0 medium CLOSED nessus rpm package didn't install nessus-update-plugins 2021-02-22 00:41:40 UTC

Internal Links: 273241

Description Vic Ricker 2007-12-20 14:57:26 UTC
Description of problem:
This probably belongs to nessus-server but that's not a component choice. The
'nessus-update-plugins' command appears to be missing.

Version-Release number of selected component (if applicable):
Version: 2.2.9
Release: 2.fc7

Steps to Reproduce:
1. nessus-fetch --register <code> calls nessus-update-plugins which isn't available

Comment 1 Andreas Bierfert 2007-12-21 00:18:50 UTC
Actually it is not missing but not included on purpose. Most plugins provided
are not GPL'd and thus providing the nessus-update-plugins script is a bit
strange... however there should at least be a dummy script I guess...

Comment 2 Vic Ricker 2007-12-21 13:42:23 UTC
I didn't ask for the plugins to be included, just the update script.  Or is that
what you're saying isn't GPL?

Regardless, I think that's pretty unfortunate as Nessus is not very useful
without the plugins. :-)


Comment 3 Tony 2008-04-10 20:34:25 UTC
I concur (having just wasted hours trying to resolve this problem) without the
update script this installation of Nessus is pretty much useless. You should
remove it from the repository.

Comment 4 Bug Zapper 2008-05-14 15:11:17 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2008-06-17 02:56:54 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.