From owner-freebsd-current@freebsd.org Wed Mar 31 12:24:57 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6D3005C68DC for ; Wed, 31 Mar 2021 12:24:57 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9QVw1tcJz3HDZ; Wed, 31 Mar 2021 12:24:55 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Date: Wed, 31 Mar 2021 14:24:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1617193492; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7r2Q+U+1EP/scOdudhDgCwDwIE8Fk7GT0hwyWtfrvzo=; b=p8gtIHs8GDg4tI806Xa+ODxRuA5qjBvPcy1/M95II6fRgxtFUG2h8gSAYj6slwzwKAViKr +eK9SRbaDP1A4kVH658LNrZyjJI5kYO/1+cJCnkJZfk0KAaYahQNyUQ+Eo1U4Kq8GyEjeR 3Jqsoll8zvXjLBnvK/DFUHn6Kppw5z/9X8TX1H7NYrWfAI+cGp9ZHVVx2evygFXlj3C/Yb NqrV/AYEXKC8Vwfk11ZBkmonSkTaI+JN6AUkaezb9frpX3DiuXlZ/1rMtY6IfLwg0ZYx4F MQuUJViQ7GA8obXUZeBmz/QuERt4qtxViDx88TKrIiCrLNNmnPhf8LiEUQLJNQ== From: Ronald Klop To: Jochen Neumeister Cc: freebsd-current@freebsd.org, Christoph Moench-Tegeder Message-ID: <1503521615.53.1617193492486@localhost> In-Reply-To: References: Subject: Re: Blacklisted certificates MIME-Version: 1.0 X-Mailer: Realworks (553.121.96d15b53941) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4F9QVw1tcJz3HDZ X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=p8gtIHs8; dmarc=pass (policy=none) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 194.109.157.24 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-3.46 / 15.00]; ARC_NA(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[194.109.157.24:from]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,none]; HAS_X_PRIO_THREE(0.00)[3]; RCVD_IN_DNSWL_NONE(0.00)[194.109.157.24:from]; NEURAL_HAM_SHORT(-0.96)[-0.962]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2021 12:24:57 -0000 Van: Jochen Neumeister Datum: woensdag, 31 maart 2021 13:26 Aan: Christoph Moench-Tegeder , freebsd-current@freebsd.org Onderwerp: Re: Blacklisted certificates > > > Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder: > > ## Jochen Neumeister (joneum@FreeBSD.org): > > > >> Why are this certificates blacklisted? > > Various reasons: > > - Symantec (which owned Thawte and VeriSign back in the time) made > > the news in a bad way: > > https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/ > > - some certificates are simply expired > > - some certificates use SHA-1 ("sha1WithRSAEncryption") which is > > beyond deprecated > > - and basically "whatever Mozilla did", as the certificates are > > imported from NSS. > > how can I ignore the certificates now? So now everyone has this problem with an update > > > Greetings > Jochen > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > Hi, This is the proper output of installworld. So you don't have to ignore anything anymore. It is handled by installworld. Ronald. From owner-freebsd-current@freebsd.org Wed Mar 31 12:37:07 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B46875C6E95 for ; Wed, 31 Mar 2021 12:37:07 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F9Qmz4Zw7z3Hhw; Wed, 31 Mar 2021 12:37:07 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qv1-f41.google.com (mail-qv1-f41.google.com [209.85.219.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 8B75A8208; Wed, 31 Mar 2021 12:37:07 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f41.google.com with SMTP id j17so9779722qvo.13; Wed, 31 Mar 2021 05:37:07 -0700 (PDT) X-Gm-Message-State: AOAM530PqkJ/RrKjJMIw6RwwDPWPtJjpjVu4PF7T1OwFqkeyZCe6xZLN i4wOmf32dwOmHhy6sAULSQ6vAHIil1z3QRAuEcg= X-Google-Smtp-Source: ABdhPJwyS3MqeMdChNNS3Ra8lv+qV7Nl2hJc/x+uQdl0Z6WHWZXUqaJ159SF0rfrtjDw+57xt1DWEduxLx10usKwMa0= X-Received: by 2002:ad4:51c1:: with SMTP id p1mr2799459qvq.39.1617194226906; Wed, 31 Mar 2021 05:37:06 -0700 (PDT) MIME-Version: 1.0 References: <1503521615.53.1617193492486@localhost> In-Reply-To: <1503521615.53.1617193492486@localhost> From: Kyle Evans Date: Wed, 31 Mar 2021 07:36:54 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Blacklisted certificates To: Ronald Klop Cc: Jochen Neumeister , FreeBSD Current , Christoph Moench-Tegeder Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2021 12:37:07 -0000 On Wed, Mar 31, 2021 at 7:25 AM Ronald Klop wrote: > > > Van: Jochen Neumeister > Datum: woensdag, 31 maart 2021 13:26 > Aan: Christoph Moench-Tegeder , freebsd-current@freebsd.org > Onderwerp: Re: Blacklisted certificates > > > > > > Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder: > > > ## Jochen Neumeister (joneum@FreeBSD.org): > > > > > >> Why are this certificates blacklisted? > > > Various reasons: > > > - Symantec (which owned Thawte and VeriSign back in the time) made > > > the news in a bad way: > > > https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/ > > > - some certificates are simply expired > > > - some certificates use SHA-1 ("sha1WithRSAEncryption") which is > > > beyond deprecated > > > - and basically "whatever Mozilla did", as the certificates are > > > imported from NSS. > > > > how can I ignore the certificates now? So now everyone has this problem with an update > > > > > > Greetings > > Jochen > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > Hi, > > This is the proper output of installworld. So you don't have to ignore anything anymore. It is handled by installworld. > I might smack it with a -q hammer, since the output's likely not relevant to most people (certainly not there).