Github messages for voidlinux
 help / color / mirror / Atom feed
From: Dieken <Dieken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: update-check: no partial response and not trust insecure certificate
Date: Mon, 03 Apr 2023 02:17:07 +0200	[thread overview]
Message-ID: <20230403001707.KMzhq-2RKW-yAGOKInzTcPH1a_aVo4DkdtDmKSLX0W8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43192@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

New comment by Dieken on void-packages repository

https://github.com/void-linux/void-packages/pull/43192#issuecomment-1493482399

Comment:
> Some packages' homepages have invalid or self-signed certificates, I've seen it before

Get it, thanks for the explanation, I’m new to Void Linux.

IMHO, the public official package repository should forbid insecure certificate, at least by default, I always feel nervous about skipping certificate validation when I review peer’s code.

  parent reply	other threads:[~2023-04-03  0:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 10:50 [PR PATCH] " Dieken
2023-04-02 20:27 ` classabbyamp
2023-04-02 23:07 ` Dieken
2023-04-02 23:15 ` classabbyamp
2023-04-02 23:16 ` classabbyamp
2023-04-02 23:28 ` Dieken
2023-04-02 23:43 ` Duncaen
2023-04-02 23:43 ` classabbyamp
2023-04-02 23:56 ` Duncaen
2023-04-03  0:02 ` Duncaen
2023-04-03  0:13 ` Dieken
2023-04-03  0:17 ` Dieken [this message]
2023-07-02  2:10 ` github-actions
2023-07-16  2:13 ` [PR PATCH] [Closed]: " github-actions

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=20230403001707.KMzhq-2RKW-yAGOKInzTcPH1a_aVo4DkdtDmKSLX0W8@z \
    --to=dieken@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).