Timeline for engineer list by rozzin, page 101
rozzin
engineer
Thursday, 29-Nov-0001 19:00:00 EST
-
@bobbyc Now I just need someone on Verizon + someone on Sprint/Nextel (remember Nextel!?) & that'll cover the entire US #wireless #market
-
@mk, I think the idea is, if #SPF ever achieved #saturation (100% deployment), the list of "Received" headers would become trustworthy
-
@rozzin that sounds like the evolution of spam origin analysis: first, all Received: headers were checked; but then it was seen that those could actually be spoofed, too - *except* for the origin machine of the last hop. Looks like SPF picked up on that 'wisdom' and doesn't bother itself with what could be fake anyway. But thanks, I hadn't realized that about SPF (though …
-
#Tmobile's #SMS gateway is just eating mail from my server. Not sure whether it's just because they've broken something, or because my whole subnet is(!) on some shitty #blacklist (which could affect users on other wireless services). Gathering data....
-
@mmn, you didn't break SMS support :) @bobbyc's helping test delivery from my server to different WSPs.
-
@bobbyc, can you ping me back when/if you get this via SMS?
-
@mk, you're actually being too nice to #SPF: it doesn't even verify the envelope sender beyond the last hop in the delivery path. It (sort of, sometimes...) `facilitates' traceability... but depends on `everyone else' doing work: the people who want to benefit from SPF need SRS all allong both their inbound and outbound delivery paths, and the people who'd need to implement SRS aren't the ones who benefit from SPF.
-
@mk, I'm pretty sure you and I are in agreement about SPF vs. DKIM/PGP/SMIME: all of that latter group operate on the message, not the envelope, and verify the origin in a user-compatible way regardless of the delivery path.
-
@boneidol, we need to get past the idea that !crypto's too complicated & too slow for everyday use. It works better than the alternatives.
-
@boneidol, I'd rather bank on #DKIM. Or #PGP. Or S/MIME.
-
@mk @rozzin you miss the point. A spam domain can have a strong SPF record. But if bank.com published a strong SPF record, it would be easy to identify email from bank.com
-
Though... we're going to run out of places to put #snow, soon. Thinking about boxing it up, shipping it to @palmella's family down south.
-
Round 2 of #noreaster, today. Only 1' of snow. Barely exciting after the first round last week: https://status.hackerposse.com/attachment/6659
-
!TIL how to make #hollandaise sauce. Now I just need to learn #restraint....
-
I really do wish #IPv6 would hurry up and become viable: http://thread.gmane.org/gmane.org.user-groups.linux.gnhlug/23514
-
Day 4 with #Invisalign. #teeth shifting.
-
@boneidol, are we making progress on the "banks requiring their customers use the most insecure browser available" problem?
-
Lots of the #SPAM I'm getting that passes #SPF checks also has forged "From: " headers.
-
I'm getting an awful lot of #SPAM that passes #SPF checks.
-
Oh, awesome: the #RadioShack down the street actually has !analog multimeters. Wasn't expecting that.
Joshua Judson Rosen
Temporary Marjolein
kat
All Hacker Poesy content and data are available under the