Re: Secure chat

From: Juergen Nieveler (juergen.nieveler.nospam_at_arcor.de)
Date: 09/14/05


Date: 14 Sep 2005 13:02:26 GMT

Volker Birk <bumens@dingens.org> wrote:

>> As I see it, that leaves only two things open: The amount of traffic
>> going over my TOR connection, and the fact that the Jabber-server will
>> know who I send messages to. The first can be taken care of by creating
>> random traffic over the TOR link when not chatting.
>> Is there such a thing as Onion-Routing-Messaging, or a Mixmaster-like
>> Jabber system to take care of the second issue?
>
> The random traffic is needed to avoid knowing anybody, when you're
> communicating.

Yes, but that only takes care of wiretaps on your own end. Anybody with
access to the server will be able to see who you send messages to, as
all messages are routed through the server. Hence the idea of a
Mixmaster-like messaging system - you send an encrypted IM to a random
contact, who decrypts it and receives instructions to pass the message
on to the next recipient. As it's encrypted, he doesn't know wether
it's the final recipient or just another forwarder.

Hang on... technically, one wouldn't even need to install this on the
server end, would one? This could be handled exclusively on the client
side, and it could be built into a client as default. As the
"Mixmaster"- messages are encrypted, it doesn't matter wether the
client sees the messages. Therefore, if you build a "Mixmaster" into
every IM client, to send non-traceable messages all you need to do is
choose a recipient at random from all the clients that are online at
that time. The client would decrypt the message, and if it's destined
for him, he'd show it to the local user. If not, he'd pass it on to the
next hop...

Any takers? Does this sound like a workable concept?

Juergen Nieveler

-- 
Speed-optimizing the code?!? Don't you have a PENTIUM PRO??!!


Relevant Pages

  • Re: Domain Change on SBS2003 R2 w/exchange 2003
    ... Regarding the client Connect to SBS VPN issue, ... on the SBS server to configure/update the server as VPN server to use the ... Go to Exchange System Manager and then locate to "Recipient Policies", ...
    (microsoft.public.windows.server.sbs)
  • NDR without numeric code
    ... no server error ... client and THEN get returned, ... this recipient. ... >and telnet to the mail server. ...
    (microsoft.public.outlook)
  • Outlook 2003 Can Not Connect To SSL Servers
    ... I am running Outlook 2003 on top of Vista Home Premium with Windows Live One Care for security. ... For last few months no problems, then I began receiving error "0x800CCC7D" and could no longer connect to outgoing SMTP server; according to MS article kb/289967 this is allegedly an error on server side. ... They also confirmed all of my client settings are correct. ... Unless anyone can suggest other alternatives, my next step is to uninstall and reinstall Outlook client. ...
    (microsoft.public.outlook)
  • Re: Outlook 2003 Can Not Connect To SSL Servers
    ... I am running Outlook 2003 on top of Vista Home Premium with Windows Live One ... Care for security. ... and could no longer connect to outgoing SMTP server; ... They claim it is client issue. ...
    (microsoft.public.outlook)
  • Re: Secure chat
    ... but that only takes care of wiretaps on your own end. ... > all messages are routed through the server. ... you're communicating, but it does not know, to whom. ... The client would decrypt the message, ...
    (comp.security.misc)