Hi,
I'm using a TP-LINK WDR3600 with a bigger flash. Since some time the router
hangs in an endless boot loop. I see the following message:
...
[0.402716] spi-nor spi0.0: BFPT parsing failed. Please consider using
SPI_NOR_SKIP_SFDP when declaring the flash
[0.413217] spi-nor: probe of
(On my phone, Gmail mobile only sends html emails, sorry for that)
As this is a legal issue, should we get SFC opinion first ?
Since you deem it a legal issue, yes, get their opinion.
___
openwrt-devel mailing list
Hi Sam,
On Sun, Mar 31, 2024 at 03:32:59PM -0700, Sam Petrov wrote:
> I have a project for work I'm shopping around: I have access to an
> existing SDK from Morse Micro
> (https://drive.google.com/drive/folders/18vAzb6E4E33axyx20E9QvXI0NfQVF6S8?usp=sharing).
> I'm trying to get AHM26108D
>
I have a project for work I'm shopping around: I have access to an
existing SDK from Morse Micro
(https://drive.google.com/drive/folders/18vAzb6E4E33axyx20E9QvXI0NfQVF6S8?usp=sharing).
I'm trying to get AHM26108D
(https://www.alfa.com.tw/products/ahm26108d?variant=39922067898440) to
work with
> Le 31 mars 2024 à 19:06, Thibaut a écrit :
>> Le 31 mars 2024 à 18:46, Daniel Golle a écrit :
>>
>> I've seen that, and by itself it does not present a security risk in
>> the context libarchive is intended to be used.
BTW in case that isn’t obvious, the deadliest exploits typically
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Branch: refs/heads/master
> Le 31 mars 2024 à 18:46, Daniel Golle a écrit :
>
> On Sun, Mar 31, 2024 at 12:05:03PM +0200, Thibaut wrote:
>>
>>> Le 31 mars 2024 à 01:07, Elliott Mitchell a écrit :
>>>
Normally upstream publishes release tarballs that are different than the
automatically generated ones in
On Sun, Mar 31, 2024 at 12:05:03PM +0200, Thibaut wrote:
>
> > Le 31 mars 2024 à 01:07, Elliott Mitchell a écrit :
> >
> >> Normally upstream publishes release tarballs that are different than the
> >> automatically generated ones in GitHub. In these modified tarballs, a
> >> malicious version
> Le 31 mars 2024 à 01:07, Elliott Mitchell a écrit :
>
>> Normally upstream publishes release tarballs that are different than the
>> automatically generated ones in GitHub. In these modified tarballs, a
>> malicious version of build-to-host.m4 is included to execute a script
>> during the
Hi,
ne 31. 3. 2024 v 1:07 odesílatel Elliott Mitchell napsal:
> On Sat, Mar 30, 2024 at 10:54:00PM +0100, Oldřich Jedlička wrote:
> >
> > so 30. 3. 2024 v 16:31 odesílatel Daniel Golle
> > napsal:
> > > Hiding a malicious change in a commit is infinitely harder than hiding
> > > it in a
On 31.03.24 01:07, Elliott Mitchell wrote:
On Sat, Mar 30, 2024 at 03:30:49PM +, Daniel Golle wrote:
unchanged. Git has a lot of security built-in, and by using tarballs
as a base for our package builds we are basically throwing all that
away, for the sake of saving a negligible amount of
11 matches
Mail list logo
