On 2019-03-06 12:31, Jo-Philipp Wich wrote:
> Hi,
>
> the random PARTUUID has been chosen to ensure that a given boot grub
> partition (containing grub config, kernel, sysupgrade restore tarball)
> boots the correct corresponding rootfs in case multiple openwrt
> partitions are present on the devi
On Thu, Mar 7, 2019 at 10:36 AM Jo-Philipp Wich wrote:
> Hi,
>
> > Could this be a CLI parameter to make, or something that's written to
> > the .config?
>
> Once it is set in .config it will remain the same with every subsequent
> rebuild, defeating its purpose entirely.
>
> ~ Jo
>
>
Users who s
Hi,
> Could this be a CLI parameter to make, or something that's written to
> the .config?
Once it is set in .config it will remain the same with every subsequent
rebuild, defeating its purpose entirely.
~ Jo
signature.asc
Description: OpenPGP digital signature
__
On Wed, Mar 6, 2019 at 5:32 AM Jo-Philipp Wich wrote:
> Hi,
>
> the random PARTUUID has been chosen to ensure that a given boot grub
> partition (containing grub config, kernel, sysupgrade restore tarball)
> boots the correct corresponding rootfs in case multiple openwrt
> partitions are present
Hi,
the random PARTUUID has been chosen to ensure that a given boot grub
partition (containing grub config, kernel, sysupgrade restore tarball)
boots the correct corresponding rootfs in case multiple openwrt
partitions are present on the device (e.g. different versions on
different block devices).
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 ---
Should it then be that if there is
R. Diez [2019-02-18 20:27:55]:
> Besides, like I mentioned in my first mail, this random PARTUUID is an
> obstacle for repeatable builds. In my opinion, repeatable builds is a
> desirable goal. It can help troubleshoot some problems, but it is especially
> interesting from a security point of vie
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 ---
The one thing I noticed is that t
R. Diez via openwrt-devel [2019-02-16
18:14:14]:
> The one thing I noticed is that there is a random PARTUUID for the X86_64
> target, and that it gets regenerated on every (re)build. This makes the
> image different every time, even if nothing has changed.
PARTUUID can't be the source of the r
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 ---
Hi all:
I am still an OpenWrt ne
10 matches
Mail list logo
