With all the recent discussion on the topic of Habeas, I thought I'd
post directly to THEIR technical discussion list. While the list is a
bit forlorn (and the archive could be cleaned up), they ARE listening
and working to improve the solution.
I received this response from Des Cahill, and am sending it to this list
with his permission. My understanding is the solution described below
will allow direct confirmation of the authenticity of a message together
WITH an enforceable action against abuses for copyright violation.
- Bob
--- orignal message ---
Bob -
Thanks for pinging us directly on tech discussion list. While we've
certainly heard a lot of direct SA user feedback re: current spam run,
we weren't aware of SA forum discussions. But we are listening and acting.
a. SA 3.0 will have a new Habeas ruleset to utilize the header *and* the
whitelist (or HUL, Habeas Users List) together. So any spoofing of the
header alone by a spammer will be irrelevant. I understand SA 3.0 is 6-8
weeks away.
b. We're testing the new SA 3.0 Habeas rules for backward compatibility
with current versions of SA. So we hope (no promises - depending on
testing results) to be able to get the rules and instructions out asap
as an interim solution to SA 2.x users prior to their upgrade to 3.0.
c. The legal work against the spammers currently spoofing habeas
continues. We've traced them down on a number of angles - extensive
legal and technical discovery has been going on - we have had a
large team of people on it. I can't say anymore, other than we are on
the case.
More next week as our work testing the Habeas rules in SA 3.0 for
backward compatibility continue.
thanks - Des
Des Cahill
CEO
Habeas, Inc.
[...]
http://www.habeas.com
Habeas means deliver
post directly to THEIR technical discussion list. While the list is a
bit forlorn (and the archive could be cleaned up), they ARE listening
and working to improve the solution.
I received this response from Des Cahill, and am sending it to this list
with his permission. My understanding is the solution described below
will allow direct confirmation of the authenticity of a message together
WITH an enforceable action against abuses for copyright violation.
- Bob
--- orignal message ---
Bob -
Thanks for pinging us directly on tech discussion list. While we've
certainly heard a lot of direct SA user feedback re: current spam run,
we weren't aware of SA forum discussions. But we are listening and acting.
a. SA 3.0 will have a new Habeas ruleset to utilize the header *and* the
whitelist (or HUL, Habeas Users List) together. So any spoofing of the
header alone by a spammer will be irrelevant. I understand SA 3.0 is 6-8
weeks away.
b. We're testing the new SA 3.0 Habeas rules for backward compatibility
with current versions of SA. So we hope (no promises - depending on
testing results) to be able to get the rules and instructions out asap
as an interim solution to SA 2.x users prior to their upgrade to 3.0.
c. The legal work against the spammers currently spoofing habeas
continues. We've traced them down on a number of angles - extensive
legal and technical discovery has been going on - we have had a
large team of people on it. I can't say anymore, other than we are on
the case.
More next week as our work testing the Habeas rules in SA 3.0 for
backward compatibility continue.
thanks - Des
Des Cahill
CEO
Habeas, Inc.
[...]
http://www.habeas.com
Habeas means deliver