Thank you very much!
I now understand things that I desperately want to know about hurd internal.
On November 2, 2021 6:31:17 PM GMT+02:00, Sergey Bugaev
wrote:
>Hello!
>
>As promised [0], here are the details of the Hurd vulnerabilities I have found
>earlier this year [1] [2].
>
>[0]: https://l
Fantastic work and writeup.
Apologies for interjecting here.
On Tue, Nov 2, 2021 at 6:54 PM Samuel Thibault
wrote:
> Hello,
>
> Thanks a lot for this writing! That'll surely be an interesting read for
> whoever wants to look a bit at the details of how the Hurd works. And of
> course thanks for
I am unable to define a guix shell file with shebang to decrease the complexity
needed in the repository managing (so that i can just do ./path/to/guix.scm for
guix to invoke `guix shell -f ./path/to/guix.scm` instead of having to sanitize
the runtime) as the issue is that POSIX shebang allows o
Short description
=
A single pager port is shared between anyone who mmaps a file, allowing anyone
to modify any files they can read. This can be trivially exploited to get full
root access to the system.
Background: Mach memory objects
===
Mach has t
Short description
=
The use of authentication protocol in the proc server is vulnerable to
man-in-the-middle attacks, which can be exploited for local privilege escalation
to get full root access to the system.
Background: authentication
==
Here, the word
Short description
=
When trying to exec a setuid executable, there's a window of time when the
process already has the new privileges, but still refers to the old task and is
accessible through the old process port. This can be exploited to get full root
access to the system.
Bac
Hello,
Thanks a lot for this writing! That'll surely be an interesting read for
whoever wants to look a bit at the details of how the Hurd works. And of
course thanks for finding and fixing the vulnerabilities :)
Samuel
Hello!
As promised [0], here are the details of the Hurd vulnerabilities I have found
earlier this year [1] [2].
[0]: https://lists.gnu.org/archive/html/bug-hurd/2021-10/msg6.html
[1]: https://lists.gnu.org/archive/html/bug-hurd/2021-05/msg00079.html
[2]: https://lists.gnu.org/archive/html/bu
Short description
=
libports accepts fake notification messages from any client on any port, which
can lead to port use-after-free, which can be exploited for local privilege
escalation to get full root access to the system.
Background: Mach notifications
The guix data service also has some info on reproducibility. See
data.guix.gnu.org
(Select master, the latest processed revision, and add /package-reproducibility
to the URL). This page compares between berlin and bordeaux.
There are a lot of unknowns because the build farms haven't both built s
Hi,
On Fri, 29 Oct 2021 at 16:48, Muhammad Hassan
wrote:
> I would like to scrap reproducibility bugs data from the linked
> website to use in my research project that is being conducted at the
> University of Waterloo. I am a Master's student.
Nice! Thank for your interest to Guix.
> The
Hi Ludo,
On Fri, 29 Oct 2021 at 16:57, Ludovic Courtès wrote:
> Right now Sway’s origin refers to the “1.5.1” tag.
>
> I found the problem:
Wow! Thanks for sharing.
> The solution is to implement pagination (yuk!), or to use an endpoint to
> look up a branch by name instead of using ‘snapshot
Ludovic Courtès writes:
> Hi!
>
> Jelle Licht skribis:
>
>> What can we do to make sure we won't simply forget to apply this and
>> other such changes?
>
> I’d suggest making this change right away in ‘core-updates’.
We need to override a change that has not landed in core-updates yet; it
only
13 matches
Mail list logo
