gpg: failed to create temporary file '/var/lib/lurker/.#lk0x57b2f100.hantslug.org.uk.23519': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: verify signatures failed: Unknown system error
On Sat, Jul 26, 2008 at 06:47:45PM +0100, Tim B (Systems) wrote:
> I can understand blocking smtp, and perhaps vpn, but why would you block ssh?
Block everything. Only allow the things you know you want to allow:
DNS and HTTP. Possibly GRE and the negotiation ports for PPTP VPNs.
Just possibly IMAP, IMAPS and POP3. What else would anybody want?
> The (relatively few) people who are aware of ssh, are mostly going to use it
> to access the command line anyway.
The key here is the phrase "very few". They don't get many people
complaining about the lack, so there's no point in them putting in
extra effort to unblock it.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- "I don't like the look of it, I tell you." "Well, stop ---
looking at it, then."
