From nobody Fri May 05 20:03:15 2023 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QChSx5YWzz49kWy for ; Fri, 5 May 2023 20:03:29 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QChSw6ZLZz3MVS for ; Fri, 5 May 2023 20:03:28 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.208.179 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com; dmarc=none Received: by mail-lj1-f179.google.com with SMTP id 38308e7fff4ca-2ac831bb762so18695581fa.3 for ; Fri, 05 May 2023 13:03:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683317007; x=1685909007; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2dMuLP5qZ44ipzJ0V3iJIPCO7bn0U7XH6Rm7zwr0WTE=; b=bVHeYAM+eGCR0ooMTfsqmmtqEpBi93+yxO6yT4h62mnMJ+jZcshnRDOyukHjnDZmYu CZ3jK18/UnQjx5Aw3zkLR59tOzOCyZGiwFEgqcGare7zZIMILj4ECzMMx1gce9FHZ0nU qLWQQwKfTl1MDk1+B1ZZXXez03JKEyK1p9fU8Bq+evmcxE9HC81Bj125WVyrdONkH5c7 j0RqDLL416rVsboSTXccTEdWlURNFvSDitA1L+kPoqE1riOQAbDhcB21nBeZUwCKumKL O3oieR6JKjEY/FJ25n2vDnYpeSNkFhIbI1Pe21B3El2gv+Bh95AWaQcWLazDT9ZiDbLD VL/A== X-Gm-Message-State: AC+VfDwn64iboCC3JideT8QEjkhTinf9EpVVsViQ9gAs/IP/78ag3slC bAM9ClYHaa+etbTme0PtEUilQOwMC9nwdFzFqhI= X-Google-Smtp-Source: ACHHUZ5HP9LORasfvDBhrVcU1L63dJfCX2XeCQSNrJ4BsDZE/wTNAo9GhRfyqbLQM5ZppJ+FIDZahs1Q6eUKgHGii20= X-Received: by 2002:a05:6512:1031:b0:4dd:98c6:ee2 with SMTP id r17-20020a056512103100b004dd98c60ee2mr712071lfr.15.1683317006704; Fri, 05 May 2023 13:03:26 -0700 (PDT) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 References: <12f8559c-d696-5344-98d5-1751d04088af@FreeBSD.org> In-Reply-To: From: Ed Maste Date: Fri, 5 May 2023 16:03:15 -0400 Message-ID: Subject: Re: OpenSSL 3.0 for 14.0-RELEASE: issues with 1.x/3.x symbol clashing, ports linking against base OpenSSL, ports that don't compile/link against OpenSSL 3, etc To: Pierre Pronchery Cc: freebsd-arch@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-0.59 / 15.00]; NEURAL_HAM_SHORT(-0.64)[-0.642]; NEURAL_SPAM_LONG(0.37)[0.369]; NEURAL_HAM_MEDIUM(-0.32)[-0.318]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-arch@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.179:from]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.179:from]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arch@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4QChSw6ZLZz3MVS X-Spamd-Bar: / X-ThisMailContainsUnwantedMimeParts: N On Wed, 3 May 2023 at 19:10, Pierre Pronchery wrote: > > I have started to look at updating OpenSSL to version 3.0.8 in base, > using the existing vendor/openssl-3.0 branch. > > My progress can be found at > https://github.com/khorben/freebsd-src/tree/khorben/openssl-3.0. I > regularly force-push to keep a consistent and nice commit history, > before possibly applying for a merge. > > So far the status is: > > - libssl, libcrypto build on amd64, i386, less sure about aarch64, other > architectures not tested aarch64 is also Tier-1 and we'll need to make sure it's working well, but that can happen after we have at least one arch fully functional. > - libfetch builds, uses libmd in addition to OpenSSL > - libradius builds, same thing > - libarchive builds > - libunbound builds, but not unbound > - libmp builds I had a look at the remaining build failures with your changes merged in, and I see errors due to deprecation notices in: auditdistd bhyve decryptcore dma dumpon factor ktls_test ldns libfido2 ppp telnet tcpdump I started working on updating libfido2 some time ago, and will pick that back up.