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]
Date:   Sat, 6 Aug 2022 20:52:00 +0300
From:   Jarkko Sakkinen <jarkko@...nel.org>
To:     Kalle Valo <kvalo@...nel.org>
Cc:     James Bottomley <James.Bottomley@...senpartnership.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Peter Huewe <peterhuewe@....de>,
        Jason Gunthorpe <jgg@...pe.ca>,
        David Howells <dhowells@...hat.com>,
        Paul Moore <paul@...l-moore.com>,
        James Morris <jmorris@...ei.org>,
        "Serge E. Hallyn" <serge@...lyn.com>,
        linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
        keyrings@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [GIT PULL] tpmdd updates for v5.20

On Fri, Aug 05, 2022 at 08:43:30AM +0300, Kalle Valo wrote:
> James Bottomley <James.Bottomley@...senPartnership.com> writes:
> 
> > On Thu, 2022-08-04 at 09:35 +0300, Kalle Valo wrote:
> >> Jarkko Sakkinen <jarkko@...nel.org> writes:
> > [...]
> >> > M...rten Lindahl (1):
> >> >       tpm: Add check for Failure mode for TPM2 modules
> >> 
> >> Some encoding problems in the name? At least my Gnus didn't show them
> >> correctly.
> >
> > My mail tool correctly renders the 'å' character, and lore has it too:
> >
> > https://lore.kernel.org/all/20220803210228.158993-1-jarkko@kernel.org/
> >
> > So I think you have a local UTF-8 translation problem.
> 
> Odd, I haven't noticed any UTF-8 problems in my setup but Gnus/Emacs is
> known to be picky. After some more investigation I noticed this in
> Jarkko's email:
> 
> Content-Type: text/plain; charset=y
> 
> I admit I'm not up to par with the latest cool stuff but that charset
> can't be valid, right? :)
> 
> -- 
> https://patchwork.kernel.org/project/linux-wireless/list/
> 
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

I must have pressed 'y' and enter, instead of enter,
when git send-email asked whether to use UTF-8 or
something like that.

Sorry about that :-) I don't recall doing that but
that is what it looks like for me.

BR, Jarkko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ