2.4.x series should be announced as end-of-life in Gentoo; to get
remaining consumers to migrate to the 2.5 or 2.6 series.
2.4.59-r2 does not build with GCC14, and 2.4.59-r3 builds with warnings,
some of which are downgraded from error.
atexit-fix ensures that consumers of the libraries do not segfault
during their cleanup.
Please note that 2.4.x does NOT consistently pass src_test at this time.
Closes: https://bugs.gentoo.org/show_bug.cgi?id=920380
Closes: https://bugs.gentoo.org/show_bug.cgi?id=882183
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
Currently, there doesn't seem to be a reason to block the loading of
the unconfined policy module on the mcs and mls policy types. Let's
ensure we load the unconfined policy module unconditionally in the
eclass.
The loading of the unconfined policy module was initially blocked in
82e30f21ab, however as far as I can tell,
there is no longer a reason to do this. Considering there are use flags
for sec-policy/selinux-base and sec-policy/selinux-base-policy for the
unconfined policy module, and using the unconfined policy module is
supported for the mcs and mls policy types, it makes sense to no longer
block the loading of the policy module. It is also worth mentioning
that grabbing an selinux stage3 has the unconfined policy module
already loaded.
As the strict policy is effectively the targeted policy without support
for the unconfined domain, it makes sense to not load the unconfined
module for strict policy types. Let's keep a conitional check for the
strict policy to ensure we don't load the unconfined module in that
case.
Closes: https://bugs.gentoo.org/933709
Closes: https://github.com/gentoo/gentoo/pull/37931
Signed-off-by: Rahul Sandhu <rahul@sandhuservices.dev>
Signed-off-by: Jason Zaman <perfinion@gentoo.org>
git:// is unencrypted and could be used by an attacker (mitm) to insert malicious code, see also [1].
git:// runs on port 9418 which is also less likely open behind a firewall.
[1] git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Closes: https://github.com/gentoo/gentoo/pull/38276
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
git:// is unencrypted and could be used by an attacker (mitm) to insert malicious code, see also [1].
git:// runs on port 9418 which is also less likely open behind a firewall.
[1] git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Joonas Niilola <juippis@gentoo.org>
git:// is unencrypted and could be used by an attacker (mitm) to insert malicious code, see also [1].
git:// runs on port 9418 which is also less likely open behind a firewall.
[1] git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at>
Signed-off-by: Joonas Niilola <juippis@gentoo.org>