Michael Seney <[EMAIL PROTECTED]> writes:
> No I thought I was already registered to misc when I sent that and then
> noticed
> that it didn't post. So I registered thinking that first message would never
> post and sent another.
What you're describing is most likely just normal greylisting
beh
No I thought I was already registered to misc when I sent that and then noticed
that it didn't post. So I registered thinking that first message would never
post and sent another.
Steve Shockley <[EMAIL PROTECTED]> wrote:Your message at 9:00 wasn't enough, so
you sent another one at 9:22?
If so
At least, disallow hacker to physical touch your OpenBSD box.
You be free of threat.
--
View this message in context:
http://www.nabble.com/OpenBSD-Memory-Sniffer-Protection-tp16365938p16366134.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.
Michael Seney wrote:
Recently I have taken notice in a growing number of articles
concerning memory sniffing threats. Today's post at The Register they
talk about the DaisyDukes memory sniffer. Is this truly a threat if I
am running OpenBSD?
Your message at 9:00 wasn't enough, so you sent anoth
Recently I have taken notice in a growing number of articles concerning memory
sniffing threats. Today's post at The Register they talk about the DaisyDukes
memory sniffer. Is this truly a threat if I am running OpenBSD?
http://www.theregister.co.uk/2008/03/28/memory_sniffer_unveiled/
http://cit
Recently I have taken notice in a growing number of articles concerning memory
sniffing threats. Today's post at The Register they talk about the DaisyDukes
memory sniffer. What disturbed me the most was seeing SSH mentioned. Is this
truly a threat if I am running OpenBSD?
http://www.theregist
6 matches
Mail list logo
