I have that error" Windows XP could not start because the following
file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM " can i
fix this from bios without Windows cd? Thx in advance
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/
On 6/12/2010 2:50 AM, Kaspar Brand wrote:
>
> The statement about the SignerIdentifier is definitely incorrect. It
> seems that Microsoft does not yet fully understand the issue - does
> anyone here have straight contact to the Outlook dev team, or know
> people who have? I'd be happy to help (
On 2010-06-12 12:49 PDT, Robin H. Johnson wrote:
> On Sat, Jun 12, 2010 at 12:15:07PM -0700, Matt McCutchen wrote:
>> On Jun 12, 2:25 pm, Nelson B Bolyard wrote:
>>> On 2010-06-10 22:59 PDT, Robin H. Johnson wrote:
The testcase has been run on Arch and Fedora now, and both of those
cases
On Sat, Jun 12, 2010 at 12:15:07PM -0700, Matt McCutchen wrote:
> On Jun 12, 2:25 pm, Nelson B Bolyard wrote:
> > On 2010-06-10 22:59 PDT, Robin H. Johnson wrote:
> > > The testcase has been run on Arch and Fedora now, and both of those
> > > cases it works fine.
> > Does that mean this problem is
On Jun 12, 2:25 pm, Nelson B Bolyard wrote:
> On 2010-06-10 22:59 PDT, Robin H. Johnson wrote:
> > The testcase has been run on Arch and Fedora now, and both of those
> > cases it works fine.
>
> Does that mean this problem is resolved?
As I read, it is not; it was reported on Gentoo Linux.
--
M
On 2010-06-10 22:59 PDT, Robin H. Johnson wrote:
> On Thu, Jun 10, 2010 at 10:45:03PM +, Robin H. Johnson wrote:
>> Testcase 2:
>> (see attached minimal C code, based on posts to the list and used in the
>> modutils source AND Mozilla).
> Bah, forgot the actual file.
>
> The testcase has been
On 2010-06-12 00:50 PDT, Kaspar Brand wrote:
> Sigh. I just came across this:
>
> http://support.microsoft.com/kb/2142236
> Non-Outlook email clients unable to decrypt email sent from Outlook 2010
>
> which states under "Cause":
>
>> Outlook 2010 now more fully implements the Cryptographic Mess
> As seen from the table above, this is currently a non-issue (Outlook
> will always encode SignerIdentifier with issuer name + serial). But
> I agree that the Outlook developers should pay attention to this as
> well when they are touching the code to fix the RecipientIdentifier
> stuff.
Sigh. I
8 matches
Mail list logo