Justin Mason writes:
> Has anyone figured out what's up with this?  Does someone out there
> think that FoRK needs some MIME tutoring?
I was puzzled at first, but I think I understand what happened.
First, I approved the post because it didn't appear to be spam, even
though it wasn't from a member.  I thought it was odd that someone
wanted to send the MIME blurb to the list, but it was not really that
different from causing the New York Times web site to send a story to
the list.  (Except that the bits here are antediluvian, but old bits are
a problem to be solved by social opporobrium, not technical constraints.)
But I think what actually happened is that some idiot got infected by
Klez and had both FoRK and the pine-robot autoresponder address in their
mailbox or addressbook, so Klez forged mail from fork@xent.com to the
autoresponder, which responded.  To FoRK.

No, hits=-4.3 required=7.0
	tests=FROM_ENDS_IN_NUMS,KNOWN_MAILING_LIST,QUOTED_EMAIL_TEXT,
	      REFERENCES,SPAM_PHRASE_02_03,USER_AGENT_OE
	version=2.40-cvs

> Now, to do this, we all know they have to be cracking the strong crypto used
> on all transaction in order to process them... So this has some preaty heavy
> implications, unless it's just BS.
Anybody buying a box like this is undoubtledly going to integrate it into their
crypto infrastructure.  What's the point of putting in a box like this if it's
not an active participant in your security framework?
> Or.... you could just not bloat it 20x to begin with. Nah! (that was the
> whole point of XML afterall, to sell more CPUs - much like Oracle's use of
> Java allows them to sell 3x more CPU licenses due to the performance hit)
Blah, blah, blah.  The marketing FUD gets compounded by the Beberg FUD, talk
about 20x bloat.
> Again, see above... they _are_ claiming to decode the crypto...
What gives you the impression that's what they're doing?  That's not what the
text says.  It's largely fluff anyway.
> > "Our XG3 execution core converts XML to machine code," said Kelly,
> Mmmmmmmmmmm, machine code, never a good idea ;)
Uhhh, fundamentally it's all machine code.  Kelly's comment seems more like
drivel from a clueless marketroid than anything of technical concern.
Having what appears to be a silicon XML router would be a cool thing.  Having
one integrated with your crypto environment would kick ass.  Let it
deserialize/decrypt/repackage the XML before handing it off to the app servers.
The question, of course, is does it work with actual applications in the field
without tremendously reworking them.  Somehow I doubt it...
-Bill Kearney