Ticket #54 (closed Problem: Rejected)
Undefined value as a SCALAR reference in /site-report.pl
| Reported by: | robin | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Bro | Version: | 1.4 |
| Keywords: | Cc: |
Description
(This is after applying the patch in #51 but I don't think that's related. -Robin)
From: Peter Hart-Davis
Something else I have picked up since is that running site-report.pl
returns the following error: " Can't use an undefined value as a SCALAR
reference at ./site-report.pl line 1278." Any suggestions would be
appreciated.
Change History
comment:2 Changed 3 years ago by tim@…
I encountered the same problem, my work around was to change the summary_only option to 0 on line 70 of the site-report.pl script. My line 70 now looks like
$DEFAULT_CONFIG->{'summary_only'} = 0;
comment:3 Changed 2 years ago by edwarddean3@…
While the error can be avoided by setting the summary-only variable to
0, you then will not get full reports generated.
The error seems to be that several variables containing the reportable
data are not set due to the if-statement on line 492. This if
statement sets variables (header, incident_summ, incident_details,
system_summ, scan_summ, signature_distribtution) only if summary_only
is set to 0. I do not see any reason for this if statement and upon
removing it, I am able to get full reports rather than just the
summary.
comment:4 Changed 15 months ago by seth
(Mostly directed at Robin) Are we going to be shipping the site-report.pl script with the next release? I don't even know what it does.
comment:5 Changed 15 months ago by robin
On Fri, Nov 19, 2010 at 16:11 -0000, you wrote:
(Mostly directed at Robin) Are we going to be shipping the site-report.pl
script with the next release? I don't even know what it does.
It's part of Bro Lite. No, that's going to be removed.
Robin
comment:6 Changed 15 months ago by seth
It's part of Bro Lite. No, that's going to be removed.
Are we even going to bother fixing problems like this in another final point release of 1.5? Just wondering if I should close the ticket or not.
comment:7 Changed 15 months ago by robin
On Fri, Nov 19, 2010 at 17:42 -0000, you wrote:
Are we even going to bother fixing problems like this in another final
point release of 1.5? Just wondering if I should close the ticket or not.
Just close it. I'm wondering whether we should indeed do another
1.5.x, but even if so, I don't want to spend time on fixing things
we'll be throwing out anyway. If we do 1.5, then it will be pretty
much what's in SVN now, perhaps with a few more patches back-ported
from git depending on when we do it.
Robin
PS: I'm sure I could close this ticket somehow already with this
mail into the tracker?