MIR for nagios-nrpe.
Bug #492340 reported by
Chuck Short
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nagios-nrpe (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
I would like to include nagios-nrpe-* in main which is required by the canonicala-
https:/
If you have any questions please let me know.
Regards
chuck
Changed in nagios-nrpe (Ubuntu): | |
assignee: | nobody → Kees Cook (kees) |
Changed in nagios-nrpe (Ubuntu Lucid): | |
milestone: | none → lucid-alpha-2 |
Changed in nagios-nrpe (Ubuntu Lucid): | |
assignee: | Kees Cook (kees) → Chuck Short (zulcss) |
Changed in nagios-nrpe (Ubuntu Lucid): | |
milestone: | lucid-alpha-2 → lucid-alpha-3 |
To post a comment you must log in.
Debian 547092 is kind of important, even if nrpe usage is generally over secure networks and the data gathered isn't usually considered private. Gaining full SSL support would be much nicer, though. I'd prefer it was handled upstream, though. Can you ping the Debian group about it?
For maximal happiness, I would like to see nagios-nrpe include the "hardening- includes" package and to have the rules file adjusted to include the $(HARDENING_CFLAGS) and $(HARDENING_ LDFLAGS) in the respective variables for the build. (See evince, for example. You can check the resulting build is PIE by using the "hardening-check" utility.)