Package Details: linux-apparmor-docs 5.1.14.arch1-1

Git Clone URL: https://aur.archlinux.org/linux-apparmor.git (read-only)
Package Base: linux-apparmor
Description: Kernel hackers manual - HTML documentation that comes with the Linux-apparmor kernel
Upstream URL: https://git.archlinux.org/linux.git/log/?h=v5.1.14-arch1
Licenses: GPL2
Submitter: alzeih
Maintainer: alzeih
Last Packager: alzeih
Votes: 8
Popularity: 0.516259
First Submitted: 2017-12-04 08:02
Last Updated: 2019-06-24 22:27

Dependencies (6)

Required by (0)

Sources (6)

Latest Comments

1 2 Next › Last »

jussihi commented on 2019-07-22 11:15

Could you please use https://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor.git/log/?h=5.2-outoftree as the kernel upstream? The linked Apparmor's kernel include needed functionality for "network" rules in kernel. Otherwise these are only available in OpenSUSE and Ubuntu.

alzeih commented on 2019-01-19 10:06

@cyrinux good news, CONFIG_PKCS8_PRIVATE_KEY_PARSER=m is set with core/linux's 4.20.arch1-1. linux-apparmor is now at 4.20.3.arch1-1, so it also has this set in the config now too.

cyrinux commented on 2019-01-18 10:47

Hi, @alzeih, Please add CONFIG_PKCS8_PRIVATE_KEY_PARSER=m in config.fragment with update to last 4.20.x

alzeih commented on 2019-01-18 04:03

It seems that no one uses this anymore, as no one has flagged this out of date for a while.

If anyone still wants an update for this kernel, then just click "Flag package out-of-date" and then I might update it.

alzeih commented on 2018-09-20 00:19

@egrupled: Thanks!

I'll keep maintaining this package for those who are using it, as linux-apparmor also sets:

CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 CONFIG_DEFAULT_SECURITY_APPARMOR=y

which core/linux currently does not (people who want selinux would probably not be happy with that).

I encourage everyone who doesn't need this to switch to core/linux and configure your boot loader appropriately, unless you still want to compile your own kernel of course.

egrupled commented on 2018-09-17 18:45

FYI: AppArmor is enabled in Archlinux kernels now: https://wiki.archlinux.org/index.php/AppArmor#Kernel

alzeih commented on 2018-07-14 09:01

@rasmusowl : See https://wiki.archlinux.org/index.php/makepkg#Signature_checking for an explanation.

You could run (as the current user):

gpg --recv-keys ABAF11C65A2970B130ABE3C479BE3E4300411886 647F28654894E3BD457199BE38DBBDC86092693E

More tips at https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key.

rasmusowl commented on 2018-07-14 08:03

Verifying source file signatures with gpg... linux-4.17.tar ... FAILED (unknown public key 79BE3E4300411886) patch-4.17.4 ... FAILED (unknown public key 38DBBDC86092693E) ==> ERROR: One or more PGP signatures could not be verified!

Can some one help me why I'm getting this error

alzeih commented on 2018-06-19 22:25

@renyuneyun A custom repo sounds like a good idea for those who want it. You don’t mention what you are using for automation, but could you parse the .SRCINFO for AUR packages instead of the PKGBUILD? I think this is how the AUR itself handles this problem.

renyuneyun commented on 2018-06-19 09:24

@alzeih Thanks for the clarification. It makes sense. I didn't really carefully read the content of core/linux/PKGBUILD previously (when I manually build kernel for apparmor on my machine).

The reason that I gave this modification is that I'm packaging this package in an automated process (of a custom arch repo), which can leverage the default split package behaviour of makepkg. The automated process doesn't support non-standard split package handling (yet?), so a "correct" PKGBUILD is needed.

Anyway, since this behaviour is inherited from official PKGBUILD and I think it's constant/static, I'll write a script to automatically change the content for the repo.