On Wed, Oct 24, 2018 at 12:05 AM Johannes Berg
wrote:
>
> From: Johannes Berg
>
> These files have a long history of code changes, but analysing
> the remaining code leads to having only a few changes that are
> not already owned by Intel, notably from
> - Andy Lutomirs
On Mon, Oct 2, 2017 at 10:26 PM, Herbert Xu wrote:
> On Mon, Oct 02, 2017 at 09:18:24PM -0700, Andy Lutomirski wrote:
>> > On Oct 2, 2017, at 7:25 PM, Jia-Ju Bai wrote:
>> >
>> > The SCTP program may sleep under a spinlock, and the function call path is:
>> &
> On Oct 2, 2017, at 7:25 PM, Jia-Ju Bai wrote:
>
> The SCTP program may sleep under a spinlock, and the function call path is:
> sctp_generate_t3_rtx_event (acquire the spinlock)
> sctp_do_sm
>sctp_side_effects
> sctp_cmd_interpreter
>sctp_make_init_ack
> sctp_pack_cook
On Tue, Dec 13, 2016 at 3:35 AM, Kalle Valo wrote:
> Andy Lutomirski writes:
>
>> Eric Biggers pointed out that the orinoco driver pointed scatterlists
>> at the stack.
>>
>> Fix it by switching from ahash to shash. The result should be
>> simpler, fas
Eric Biggers pointed out that the orinoco driver pointed scatterlists
at the stack.
Fix it by switching from ahash to shash. The result should be
simpler, faster, and more correct.
Cc: sta...@vger.kernel.org # 4.9 only
Reported-by: Eric Biggers
Signed-off-by: Andy Lutomirski
---
Compile
On Mon, Oct 17, 2016 at 12:37 AM, Ard Biesheuvel
wrote:
> On 17 October 2016 at 08:28, Johannes Berg wrote:
>> On Sat, 2016-10-15 at 18:16 +0100, Ard Biesheuvel wrote:
>>> The CCM code goes out of its way to perform the CTR encryption of the
>>> MAC using the subordinate CTR driver. To this end,
On Oct 13, 2016 6:46 AM, "Johannes Berg" wrote:
>
> On Thu, 2016-10-13 at 22:42 +0900, Sergey Senozhatsky wrote:
> >
> > > > https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/commi
> > > > t/?h=x86/vmap_stack&id=0a39cfa6fbb5d5635c85253cc7d6b44b54822afd
> > > > https://git.kernel.org/cgit
On Wed, Oct 12, 2016 at 7:22 AM, Johannes Berg
wrote:
>
>> > Can you elaborate on how exactly it kills your system?
>>
>> the last time I saw it it was a NULL deref at
>> ieee80211_aes_ccm_decrypt.
>
> Hm. I was expecting something within the crypto code would cause the
> crash, this seems strange
On Thu, Aug 25, 2016 at 12:29 AM, Luca Coelho wrote:
> Hi Andy,
>
> Sorry for the really long delay in replying. :(
>
> On Sun, 2016-08-07 at 01:54 -0700, Andy Lutomirski wrote:
>> My Intel 7265 used to work flawlessly, but for the past week or two
>> it
>> has se
My Intel 7265 used to work flawlessly, but for the past week or two it
has seemed to be very unreliable. It's also throwing errors. I see
problems on firmware versions 16 and 21, although I haven't gotten the
warning and backtrace on firmware 16 yet.
I have:
iwlwifi :3a:00.0: enabling devic
Hi-
My laptop has SPLC implemented like this:
Name (SPLX, Package (0x04)
{
Zero,
Package (0x03)
{
0x8000,
0x8000,
0x8000
},
Package (0x03)
{
has irq: 1)!
[ 1441.958506] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
I assume that's what's causing the problem.
Thanks,
Andy
--
Andy Lutomirski
AMA Capital Management, LLC
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body
If I switch my laptop into airplane mode (hardware switch) and then
suspend and resume, my wireless is dead on resume and it spews all
over the kernel log (see below). I can rescue it by switching
airplane mode off and then suspending and resuming again.
This problem has existed on all kernel ver
On Mon, Jun 1, 2015 at 8:50 AM, David Howells wrote:
> Andy Lutomirski wrote:
>
>> > You can also fudge the signature (or a hash) by adding extra data to or
>> > modifying the data blob and by switching signature values between signature
>> > blobs.
>>
>
On Fri, May 29, 2015 at 5:40 AM, David Howells wrote:
> Andy Lutomirski wrote:
>
>> This is insecure because PKCS#7 authenticated attributes are broken (see
>> RFC2315 section 9.4 note 4). You need to either require that everything have
>> authenticated attributes or r
[resending with further gmane screwups fixed]
On 05/28/2015 08:48 AM, David Howells wrote:
Modify the sign-file program to take a "-F " parameter. The
name is a utf8 string that, if given, is inserted in a PKCS#7 authenticated
attribute from where it can be extracted by the kernel. Authenticat
On Thu, May 21, 2015 at 9:51 AM, Petko Manolov wrote:
> On 15-05-21 09:39:50, Andy Lutomirski wrote:
>>
>> It's also a performance cost because the average user of this signature stuff
>> doesn't actually want IMA, and IMA is checking the wrong think anyway.
>>
On Thu, May 21, 2015 at 9:43 AM, Petko Manolov wrote:
> On 15-05-21 16:51:49, David Howells wrote:
>>
>> I do have patches to parse PGP key data and add the public keys found therein
>> onto the kernel keyring, but that would mean adding an extra key data parser.
>
> PGP is widely used so i would
firmware in the first place.
>
> > > 3. PKCS#1 v1.5, really? PKCS#1 v1.5 is known to be insecure unless
> > > very cafefully validated. For example:
> > >
> > > https://www.imperialviolet.org/2014/09/26/pkcs1.html
> > >
> > > Could we please consi
19 matches
Mail list logo
