Linux Security Modules development
 help / color / mirror / Atom feed
From: John Johansen <john@jjmx.net>
To: Baruch Siach <baruch@tkos.co.il>,
	John Johansen <john.johansen@canonical.com>
Cc: Serge Hallyn <serge@hallyn.com>,
	Ryan Lee <ryan.lee@canonical.com>,
	John Johansen <john@apparmor.net>,
	Georgia Garcia <georgia.garcia@canonical.com>,
	apparmor@lists.ubuntu.com, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] apparmor: update website link
Date: Thu, 23 Jul 2026 10:12:18 -0700	[thread overview]
Message-ID: <bf88cee2-c398-45d7-88e8-c5740e0aeddf@jjmx.net> (raw)
In-Reply-To: <87bjbxodw7.fsf@tarshish>

On 7/23/26 09:43, Baruch Siach wrote:
> Hi John, Serge,
>
> On Wed, Jul 22 2026, John Johansen wrote:
>> On 7/22/26 15:36, Serge Hallyn wrote:
>>> Jul 22, 2026 11:41:27 Ryan Lee <ryan.lee@canonical.com>:
>>>
>>>> On Tue, Jul 21, 2026 at 4:40 AM Baruch Siach <baruch@tkos.co.il> wrote:
>>>>> apparmor.wiki.kernel.org redirects to the current website.
>>> Sure, but kernel.org seems less likely to go away, and the redirect can
>>> easily be updated if needed.  Up to John of course, but i would leave it
>>> as is.
>> I am unsure of the best course, but atm I am inclined to leave it with
>> kernel.org, Like you said the redirect can easily be updated.
> Another problem this patch fixes is the use of unauthenticated
> HTTP. This is less than ideal for a security feature. A MITM attacker
> can easily redirect to somewhere else.
>
> So a patch only switching to HTTPS should be fine, right?
>
switching to HTTP is fine, if you want to submit a patch that does that.


>>>>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>>>>> ---
>>>>> security/apparmor/Kconfig | 2 +-
>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/security/apparmor/Kconfig b/security/apparmor/Kconfig
>>>>> index 1e3bd44643da..472aa38254be 100644
>>>>> --- a/security/apparmor/Kconfig
>>>>> +++ b/security/apparmor/Kconfig
>>>>> @@ -11,7 +11,7 @@ config SECURITY_APPARMOR
>>>>>             This enables the AppArmor security module.
>>>>>             Required userspace tools (if they are not included in your
>>>>>             distribution) and further information may be found at
>>>>> -         http://apparmor.wiki.kernel.org
>>>>> +         https://wiki.apparmor.net
>>>>>
>>>>>             If you are unsure how to answer this question, answer N.
>>>> Reviewed-by: Ryan Lee <ryan.lee@canonical.com>



      reply	other threads:[~2026-07-23 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 11:19 [PATCH] apparmor: update website link Baruch Siach
2026-07-22 16:35 ` Ryan Lee
2026-07-22 22:36   ` Serge Hallyn
2026-07-22 23:53     ` John Johansen
2026-07-23 16:43       ` Baruch Siach
2026-07-23 17:12         ` John Johansen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf88cee2-c398-45d7-88e8-c5740e0aeddf@jjmx.net \
    --to=john@jjmx.net \
    --cc=apparmor@lists.ubuntu.com \
    --cc=baruch@tkos.co.il \
    --cc=georgia.garcia@canonical.com \
    --cc=john.johansen@canonical.com \
    --cc=john@apparmor.net \
    --cc=linux-security-module@vger.kernel.org \
    --cc=ryan.lee@canonical.com \
    --cc=serge@hallyn.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox