From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: i2pd: restrict /etc/i2pd permissions
Date: Thu, 25 May 2023 18:29:43 +0200 [thread overview]
Message-ID: <20230525162943.cy6fLIokrDyRii-y0N5ymuMyEF0V_3ypvFgk8Tj6uUQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42409@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
There's a merged pull request on the void-packages repository
i2pd: restrict /etc/i2pd permissions
https://github.com/void-linux/void-packages/pull/42409
Description:
It's not a good idea to have /etc/i2pd/*.conf world-readable since it may contain sensitive information
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2023-05-25 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 11:06 [PR PATCH] " steinex
2023-02-23 11:10 ` [PR PATCH] [Updated] " steinex
2023-02-23 11:11 ` steinex
2023-03-05 22:57 ` Duncaen
2023-03-05 22:58 ` Duncaen
2023-03-06 8:56 ` [PR PATCH] [Updated] " steinex
2023-03-06 9:08 ` steinex
2023-03-06 9:52 ` [PR PATCH] [Updated] " steinex
2023-05-25 16:29 ` Duncaen [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=20230525162943.cy6fLIokrDyRii-y0N5ymuMyEF0V_3ypvFgk8Tj6uUQ@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).