2013/3/5 Bob Beck b...@openbsd.org:
On Mon, Mar 4, 2013 at 4:24 PM, Bob Beck b...@openbsd.org wrote:
You too can have a GIANT buffer cache etc. etc...
Great.. and now I have people mailing me dmesg's from machines with 16
and 32 Gigs of ram. I only have 8 I feel so. small...
My
Date: Wed, 6 Mar 2013 09:25:51 +0100
From: Janne Johansson icepic...@gmail.com
2013/3/5 Bob Beck b...@openbsd.org:
On Mon, Mar 4, 2013 at 4:24 PM, Bob Beck b...@openbsd.org wrote:
You too can have a GIANT buffer cache etc. etc...
Great.. and now I have people mailing me dmesg's
2013/3/6 Mark Kettenis mark.kette...@xs4all.nl
My amd64 testbox running this has only 6G, so we can cry over red wine
together.. 8-(
the 1TB boxes at work have too many cores for obsd to run on them so I
can't really make dmesg pr0n on them.
Even when you disable HyperThreading?
No,
It's not entirely obvious that -x509 actually means produce a
csr, self-sign it (defaulting to SHA1), throw away the csr and write
the cert and this had me stuck for a long time when I wanted to
play with DSA server certs.
So here's a diff which moves DSA cert generation instructions
to the same
Hi,
When ls -l is run on a directory which has no execute permissions, ls
fails but the return value is 0.
bash-4.2$ ls -ld /tmp/foo/
drw-r-xr-x 3 sac wheel 512 Mar 6 18:11 /tmp/foo/
bash-4.2$ ls -l /tmp/foo/
bash-4.2$ echo $?
0
bash-4.2$
I see in the traverse function:
Hi,
In if_trunk.c there's an explicit if_down() for trunk ports being
removed from the trunk. This seems unnecessary to me and is there since
the trunk feature has initially added to OpenBSD.
Greetings,
Matthias
===
diff --git
On 05/03/13(Tue) 21:57, Claudio Jeker wrote:
On Tue, Mar 05, 2013 at 12:03:49PM +0100, Mike Belopuhov wrote:
On 5 March 2013 11:55, Mark Kettenis mark.kette...@xs4all.nl wrote:
Date: Tue, 5 Mar 2013 11:36:36 +0100
From: Martin Pieuchot mpieuc...@nolizard.org
The ifaddr structure
On 2013/03/06 13:05, Stuart Henderson wrote:
It's not entirely obvious that -x509 actually means produce a
csr, self-sign it (defaulting to SHA1), throw away the csr and write
the cert and this had me stuck for a long time when I wanted to
play with DSA server certs.
So here's a diff which
On 2013/03/06 15:24, Silamael wrote:
Hi,
In if_trunk.c there's an explicit if_down() for trunk ports being
removed from the trunk. This seems unnecessary to me and is there since
the trunk feature has initially added to OpenBSD.
I looked at this some time ago (because it's super annoying if
On Wed, Mar 06, 2013 at 03:58:22PM +0100, Mark Kettenis wrote:
Date: Wed, 6 Mar 2013 15:25:34 +0100
From: Martin Pieuchot mpieuc...@nolizard.org
On 05/03/13(Tue) 21:57, Claudio Jeker wrote:
On Tue, Mar 05, 2013 at 12:03:49PM +0100, Mike Belopuhov wrote:
On 5 March 2013 11:55, Mark
On Wed, Mar 06, 2013 at 01:05:16PM +, Stuart Henderson wrote:
It's not entirely obvious that -x509 actually means produce a
csr, self-sign it (defaulting to SHA1), throw away the csr and write
the cert and this had me stuck for a long time when I wanted to
play with DSA server certs.
So
Hi,
I've started using spamlogd, and since then, every single
connection attempt results in the host being whitelisted.
I log some `rdr-to 127.0.0.1 port spamd` connection attempts into pflog,
and it would seem like spamlogd filter (for port 25)
is picking up the original dport, not the
On Wed, Mar 06, 2013 at 22:27, Sylvestre Gallon wrote:
Do you know if miscfs is the best place to put my code ?
I think so.
Do I keep the device code (fuse_device.c) in the same directory than the
filesystem code?
I'd prefer that. sys/dev is kind of cluttered as it is, and since the
dev
Bob, I agree, the hdr-rewritten approach is not good.
I think the best approach here would be to not add any new entries
on incoming connections in the first place, but only keep updating
the existing ones (when the connection is incoming).
In addition to not whitelisting greylisted or
No constatine - that is not the best approach. if you are whitelisting
grelisted connections
or blacklisted connections that are blocked you have your pf.conf or
spamlogd setup wrong.
On Wed, Mar 6, 2013 at 2:54 PM, Constantine A. Murenin c...@cns.su wrote:
Bob, I agree, the hdr-rewritten
Indeed, this is what I typically do.
and make sure I only log the real mailserver connections to pflog1,
and point spamlogd at that.
On Wed, Mar 6, 2013 at 2:14 PM, Stuart Henderson s...@spacehopper.org wrote:
On 2013/03/06 13:47, Bob Beck wrote:
No constantine - the solution is to simply not
I'm simply logging greylisted connections;
it's spamlogd that whitelists them just because they're logged.
It doesn't make sense that logging greylisted or blacklisted connections
would immediately turn them into being whitelisted by spamlogd.
Same goes for logging connections that are
Yes, one could log stuff into different pflog interfaces, but I don't
understand why pf.conf `pass in ... log ... port smtp ...` is effectively
redefined to mean `add spamd-white` when spamlogd is running,
http://www.openbsd.org/cgi-bin/man.cgi?query=spamlogd
and RTFM for the first two
18 matches
Mail list logo
