linux-kernel - Re: Query: Patches break with Microsoft exchange server.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTimVMUvJLG2N5dPYAHpw8wyLdQpYaUF+F4Trw8eb@mail.gmail.com>
Date:	Mon, 9 Aug 2010 23:12:22 +0100
From:	Valeo de Vries <valeo@...eo.co.cc>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Query: Patches break with Microsoft exchange server.

On 9 August 2010 22:56, Justin P. Mattock <justinmattock@...il.com> wrote:
> On 08/09/2010 02:28 PM, David Woodhouse wrote:
>>
>> On Mon, 2010-08-09 at 21:15 +0300, Mihai Donțu wrote:
>>>
>>> Wait. I don't think we're on the same page here. I'm talking about
>>> message
>>> signing (which does not require the receiving end to have any key - it's
>>> the
>>> same plain text e-mail with a blob after it) while you refer to actually
>>> encrypting the message. Mm? Or am I being extremely slow today? :-)
>>
>> Only when you assume that Exchange would pass signed messages without
>> corrupting them. It really is that broken.
>>
>
> figured the encryption would be kind of a last resort situation..but if it's
> that broken to where it wont pass it along without corrupting, then the best
> solution is to figure out what Microsoft needs in terms of encoding, i.e. is
> there a way to have the scanner scan but not throw everything around after
> it scans.(if this is what it's doing)

The link I posted earlier seems to give the impression that
quoted-printable might do that. I may have misread that, though...

Valeo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/