Portscan logs - public or concealed?

[tonyingesson]

I have a hardware firewall (an old PC) with Snort protecting my LAN. It also doubles as a web server. I was thinking of having it print the portscan.log document generated by Snort (actually I set cron to copy the portscan.log every 30 minutes into a text file in another directory), thus making the contents of portscan.log accessible from any web browser. I thought it could be a convenient way of keeping an eye on my firewall when I'm not at home. However, since I'm not that well-versed in the ways of security I thought I'd ask you if there's any potential security hazard in making the contents of said document public like that?

[tebbens]

Is it public, where anyone can view it ?
If so, password protect it.... Apache has options for that.

Its always a security risk to give out ANY information about your setup, expecially security logs !

[tonyingesson]

One of the points was to be able to show my neighbours that there's a lot of portscanning activity targeting computers in this area, as a way to encourage them to improve their protection. So if there's no strong incentive to conceal the data in question I'd prefer to make it public. After all, it only shows the IP & port of the attacker and IP & port of the potential victim along with the time, nothing else.