From nobody Mon Oct 7 10:59:01 2024 X-Original-To: freebsd-questions@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 4XMbkX3YdJz5Xjqk for ; Mon, 07 Oct 2024 10:59:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.135]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mout.kundenserver.de", Issuer "Telekom Security ServerID OV Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XMbkW31V0z4FCB for ; Mon, 7 Oct 2024 10:59:15 +0000 (UTC) (envelope-from freebsd@edvax.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=edvax.de header.s=s1-ionos header.b=nxXpkHey; spf=pass (mx1.freebsd.org: domain of freebsd@edvax.de designates 212.227.126.135 as permitted sender) smtp.mailfrom=freebsd@edvax.de; dmarc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=edvax.de; s=s1-ionos; t=1728298748; x=1728903548; i=freebsd@edvax.de; bh=PD7Eq6kGPNeD4FExP/xVpwESSjAvXPG6BQw12NSqFx4=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:Message-Id:In-Reply-To: References:Reply-To:Mime-Version:Content-Type: Content-Transfer-Encoding:cc:content-transfer-encoding: content-type:date:from:message-id:mime-version:reply-to:subject: to; b=nxXpkHeyHiUX7EQG+yIxLqNsEHypISmLXGoLkcTAGhLR9Sp4IbdeY9pCFjGM+aPR SASAC3E56zfIbigGP25lt1cvQhi96QyfFvaaNaxh+ZcCc+S2Fs5fmlAeEPMnJd8Mj jKdNeZj8fdS6pxJet4gfQpON/4NwUck5xvVWhJnaMMkC4VjjalLSuYzCjfmmyIdwW UWmVUzwgvmVC/FcPVtVuw+uZqndhycYFnFL82VzAkdrwvLhWVlBvAdlRw/jaxnK+B pr9jZnBFC0kDV886VmC4ryntD6x+V+puasa8fInKsSw82hNuyqrwlXlq90XSIlskL I9T2LDwT3wJJ/lJQvA== X-UI-Sender-Class: 55c96926-9e95-11ee-ae09-1f7a4046a0f6 Received: from terra.edvax.de ([79.197.147.220]) by mrelayeu.kundenserver.de (mreue011 [213.165.67.97]) with ESMTPSA (Nemesis) id 1MD9jV-1t6Ftl0fth-00G9BS; Mon, 07 Oct 2024 12:59:08 +0200 Received: from r56.edvax.de (r56 [10.200.1.11]) (authenticated bits=0) by terra.edvax.de (8.18.1/8.18.1) with ESMTPA id 497Ax6kv056931; Mon, 7 Oct 2024 10:59:06 GMT (envelope-from freebsd@edvax.de) Date: Mon, 7 Oct 2024 12:59:01 +0200 From: Polytropon To: Andrea Venturoli Cc: freebsd-questions@freebsd.org Subject: Re: USB storage key error Message-Id: <20241007125901.8810b1bd.freebsd@edvax.de> In-Reply-To: References: Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:fo0vnRsxdAFpj771gEpvVv7EnhBzTD6KJUmUOWTlQSEJD4yXZO5 D3ApvEv14hjP4TvHesFUueT93rIhnXIsSLYEK8FgamKB7vdQPUMTKPMdNL0dRJcPuURTp1H iBnzPJuf8+WjmXbBiCA3YitGrbRoh0ncoXtHZW6on01md/ayz2StjhyKd76LRjJgCKWy9I4 38CTeecQKMhwz0SZODFew== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:EoKnQ4zC6CA=;yCkEszFYb87f0882lgIgv28xO6w 9IDsxcdVnBA24yc7WKsytFjZO2R90C8zY14EbveKjH34rLks4rEiMYDTA+AutXFfNys6JyQhO Iik3cPwmo7sZB0C9ESJBRNVQ5ELf4oRL2j/cH/4EOL0mbK7rRL+DUZQWF73UJIrP8DGv/WFrg gWFsoZeLyoyDPg52kIfn9B9l6JDEJaN5wl18xK6E9WbxVN1wkdr5VDDSJDhFdM8pmA2/S/cQF McW5MkeWPSAlR+CmXFAAp3X24VMesz/m09osn5ZOXqweBMt/FfKHOSuHpphXxMjbpjcE60Mlg DcvVFoJcCtUF9WFGQQGQGVvz2dEE2LC8WVIvBhgYyu4O7ndJ6mu0cYY2SqDgw/X/56y2h7bQM XhgMKr74ltn2w9W0QXVVnPKbQiZrLWl82ZFgv9CUb/iVO/q39S+D7zJZxtciJhvoPzsNbW5Vj Do2hO20ORxQ32uFy/rl/Eyoiv03tgSUJxr3/Yoig46qVQM+lv0pt4NIxeErpgMBh27xjIheEN 31wMcZUTRtGyXDfMgm5D2at2hpXjW4+Pkur7OioJFSzUhZajHzHnnpRJUxa+NToiTSx7/vE6P QnXQrUGSj5NQX29w5IEOX37kGp77iqSGvSwQ3W3gwAxp8YK6ZInhVpCOY5s6fTjedZq8VGdUC suyaVAx0jRy7ih6Z+5T3QUcCSy8JIjCcR8XGuENvE6iNQsemVvJA/AVtMkNKlY1pI8mMEnV+a IcQ+tL98r2wmvt1n6ZxpYTjachewUotkw== X-Spamd-Result: default: False [-2.18 / 15.00]; MID_CONTAINS_FROM(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.985]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[edvax.de:s=s1-ionos]; R_SPF_ALLOW(-0.20)[+ip4:212.227.126.128/25]; RWL_MAILSPIKE_VERYGOOD(-0.20)[212.227.126.135:from]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[edvax.de]; RCVD_IN_DNSWL_NONE(0.00)[212.227.126.135:from]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_REPLYTO(0.00)[freebsd@edvax.de]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[edvax.de:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; REPLYTO_EQ_FROM(0.00)[] X-Rspamd-Queue-Id: 4XMbkW31V0z4FCB X-Spamd-Bar: -- On Sat, 5 Oct 2024 13:17:58 +0200, Andrea Venturoli wrote: > I'm getting this: > > kernel: UFS /dev/da0 (/mnt/HD) cylinder checkhash failed: cg 18, cgp: = 0x5b68e98 !=3D bp: 0x352516c > > Does it mean the USB key is broken and I can throw it away? Quite possible. I recently had a similar problem - stick went to "no write" mode after having multiple fsck errors and system crashes, including damaged binaries... > I can write to it, unmount it, but when I try to mount it again it gives= : > > mount: /dev/da0: R/W mount on /mnt/HD denied. Filesystem is not clean = - run fsck.: Operation not permitted Run fsck manually, two or three times. Also try to re-initalize the file system. Also perform a dd or tar test with the stick. If any test fails, it's designed to be thrown away. Any mount operation (except "mount -r") will intendedly (!) fail if the file system is not in a clean state. So performing # fsck -yf /dev/da0 is needed, as mentioned maybe multiple times. =2D- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From nobody Mon Oct 7 12:26:51 2024 X-Original-To: freebsd-questions@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 4XMdgl2P56z5Y4t3 for ; Mon, 07 Oct 2024 12:26:59 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (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 (2048 bits) client-digest SHA256) (Client CN "mailserver.netfence.it", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XMdgk4QDLz4QCF for ; Mon, 7 Oct 2024 12:26:58 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; none Received: from [192.168.1.76] (host-80-21-94-33.business.telecomitalia.it [80.21.94.33]) (authenticated bits=0) by soth.netfence.it (8.18.1/8.17.2) with ESMTPSA id 497CQpSN044012 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 7 Oct 2024 14:26:51 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.netfence.it: Host host-80-21-94-33.business.telecomitalia.it [80.21.94.33] claimed to be [192.168.1.76] Message-ID: Date: Mon, 7 Oct 2024 14:26:51 +0200 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: USB storage key error Content-Language: en-US To: Polytropon Cc: freebsd-questions@freebsd.org References: <20241007125901.8810b1bd.freebsd@edvax.de> From: Andrea Venturoli In-Reply-To: <20241007125901.8810b1bd.freebsd@edvax.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.86 X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT] X-Rspamd-Queue-Id: 4XMdgk4QDLz4QCF X-Spamd-Bar: ---- On 10/7/24 12:59, Polytropon wrote: > Quite possible. I recently had a similar problem - stick went > to "no write" mode after having multiple fsck errors and system > crashes, including damaged binaries... In my case I think it's even worse: it gives no error when you write it, but if you read it back, data won't match with the original! > If any test fails, it's designed to be thrown away. That's the problem: all the write test succeed :-O But you won't be able to read data back. Again, no error!!! Just wrong data!!! It's already in the trashbin. bye & Thanks av. From nobody Tue Oct 8 01:13:51 2024 X-Original-To: questions@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 4XMyhm4KLJz5YjjX for ; Tue, 08 Oct 2024 01:14:00 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Received: from beesty.loosely.org (beesty.loosely.org [IPv6:2600:3c01:e000:4c0::2]) (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 4XMyhl0gBdz4D8k for ; Tue, 8 Oct 2024 01:13:59 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of fatty.merchandise677@aceecat.org designates 2600:3c01:e000:4c0::2 as permitted sender) smtp.mailfrom=fatty.merchandise677@aceecat.org; dmarc=none Received: from [::1] (helo=beesty ident=itz) by beesty.loosely.org with esmtp (Exim 4.98-4-9cb179d48) (envelope-from ) id 1sxynP-000000001YU-0lTY for questions@freebsd.org; Mon, 07 Oct 2024 18:13:51 -0700 Date: Mon, 7 Oct 2024 18:13:51 -0700 From: fatty.merchandise677@aceecat.org To: questions@freebsd.org Subject: wireguard confusion Message-ID: Mail-Followup-To: questions@freebsd.org List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spamd-Result: default: False [-3.16 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.99)[-0.995]; NEURAL_HAM_SHORT(-0.97)[-0.970]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:63949, ipnet:2600:3c01::/32, country:SG]; MISSING_XM_UA(0.00)[]; FROM_NO_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[aceecat.org]; RCVD_TLS_LAST(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-Rspamd-Queue-Id: 4XMyhl0gBdz4D8k X-Spamd-Bar: --- There is a wireguard package which contains the wg tool and a helpful rc.conf bit. But there is *also* a /usr/bin/wg in base (as of 14.1) and as far as I can tell it is the same version (though not identical bit by bit). What is going on here? -- Ian From nobody Tue Oct 8 01:33:40 2024 X-Original-To: questions@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 4XMz7W169Rz5Yl32 for ; Tue, 08 Oct 2024 01:33:43 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XMz7W0YsDz4GFL for ; Tue, 8 Oct 2024 01:33:43 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728351223; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sIM9RRFbVSs4dhS5XyjGOjZQVyT9gDMsMkc6BHfShKA=; b=GYCUmlCrHHBafKCKV7qga1Pynh5OhxkAwwN6hmIwnFUDGbr5jjVEoEft4VYgSv6hbEDTve GX9SZzNwHUKU8LSaG53YNCi79capHwft1EKAom9FP+xa3uTcqU3V3OcwY3cpN6d56BNOGq kNXT/HjYpEpw/emuVfKw0+QxWZDuJjsnDnV2ZQNHbA37G1CrD7XO5m8043e8KEFa72AxKl R28GzF4M8qsnOvVCCYeFTmywGYb/e73Xxh4UzIa/cgyeWjl6dpUewFcI0Vzw+dZ+qifbrp J9kynA43gX6ObqXrG4sKfe0pQYT2ZN6Jv+GtoOVqNBHxaxUoiX1Mep/tJimNqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728351223; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sIM9RRFbVSs4dhS5XyjGOjZQVyT9gDMsMkc6BHfShKA=; b=Y8TVA1rVzSLzoswoDuZxoh7K9ArshMhlsHoNzpiUFoeAo8Q5yAYRu/dWGngsjl1ehdgDbH R7g5lcrXmN0Lo14fbHqWzRpZv7FNLnw4u0eeaaxtUVpUF6lB/jiCw1iWUXQH2SKbmQcvuh rJxk8mBmF8HJeG2jGI2W0o1IePz9Ykk92hwhrPdUsdjhVS3xuYTqoYL2ZP3AWrhkx+/EMj rCohymXBEYx6twaErWREnhH2oykEipuRTURMuLKIrIlhWItbHEZbwnsgeCWIu6kb52s7IZ S7EwNkhQ+8NiF/NShbMCxJmyDiuw9GkXqB4/2hD9Ek4kKyjcLWSyqFyNUt5+0Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1728351223; a=rsa-sha256; cv=none; b=wvXTfwdiUSCcsULEOqtK/AztVcxpJNBAHuEqCNBXKNsEH4P8X3eunf6eYvMRJOi1JzVYdu nYubI2wO1wxAX3/v207A5JIgtiTHHA8fXYuyAUEbpkdkUMpF3/biPNyOJgXORxMEmeMMPh NsBQOZyLgg48G1CmmvvkPABZ7DHvbCQh45CuQK21J3SXKAHq3hIV/Zyv8hsFtfIDHOAmWy IemWmkf0+hWK5fFTxweQzllQW3HcG1VBl/F8CniyAS+MW+gS5JhBsc0AsIPMr0a8rohFmD eeaQNejE2XD4d0rLQ2fHF1xi8GmoV1TsI33Avloync8A9VyL2ReShhSmS+NGyA== Received: from [10.9.4.95] (unknown [209.182.120.176]) (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 did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XMz7V60Xxz1MZK for ; Tue, 8 Oct 2024 01:33:42 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> Date: Mon, 7 Oct 2024 20:33:40 -0500 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wireguard confusion To: questions@freebsd.org References: Content-Language: en-US From: Kyle Evans In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/7/24 20:13, fatty.merchandise677@aceecat.org wrote: > There is a wireguard package which contains the wg tool and a helpful > rc.conf bit. But there is *also* a /usr/bin/wg in base (as of 14.1) > and as far as I can tell it is the same version (though not identical > bit by bit). What is going on here? > We imported wg(8), but left wireguard-tools intact in ports because we don't have a good replacement for wg-quick(8) and the rc script at the moment -- the former has a bash requirement. I'd love to have more direct equivalents in base, but it seems that nobody's interested in a wg-quick analog. Thanks, Kyle Evans From nobody Tue Oct 8 01:38:39 2024 X-Original-To: questions@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 4XMzFV0Xskz5Yl7T for ; Tue, 08 Oct 2024 01:38:54 +0000 (UTC) (envelope-from polarian@polarian.dev) Received: from mail.polarian.dev (mail.polarian.dev [IPv6:2001:8b0:57a:2385::8]) (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 4XMzFT162Cz4H7K for ; Tue, 8 Oct 2024 01:38:53 +0000 (UTC) (envelope-from polarian@polarian.dev) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=polarian.dev header.s=polarian header.b=Lgyfv1Yu; spf=pass (mx1.freebsd.org: domain of polarian@polarian.dev designates 2001:8b0:57a:2385::8 as permitted sender) smtp.mailfrom=polarian@polarian.dev; dmarc=pass (policy=reject) header.from=polarian.dev Received: from Hydrogen (_gateway [192.168.2.1]) by mail.polarian.dev (Postfix) with ESMTPSA id 504F410A0772 for ; Tue, 08 Oct 2024 01:38:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/relaxed; d=polarian.dev; s=polarian; t=1728351522; bh=3l5Rt+PFEXEsY57FXXy79txpY1Fp02qt/7yveMOB8cA=; h=Date:From:To:Subject:In-Reply-To:References; b=Lgyfv1YuL0u+Pgl7ExkgrsKsseR6EIc+pJABER92/lRVsciG0EDfzCRDfWNlAcxyl ImR0iKoqugVkhkE2TR+84tyYyXqwl4C4u96/HgHMFxRB+ofrTl6ZTUoLLBU+oIYwM/ +StkSJbm1PHveVUI8S2n4yMA3gIc5UI16TIqS0pk= Date: Tue, 8 Oct 2024 02:38:39 +0100 From: Polarian To: questions@freebsd.org Subject: Re: wireguard confusion Message-ID: <20241008023839.01b159e0@Hydrogen> In-Reply-To: References: X-Mailer: Claws Mail 3.20.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.40 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.995]; NEURAL_HAM_MEDIUM(-0.99)[-0.986]; NEURAL_HAM_LONG(-0.92)[-0.916]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[polarian.dev,reject]; R_DKIM_ALLOW(-0.20)[polarian.dev:s=polarian]; R_SPF_ALLOW(-0.20)[+ip6:2001:8b0:57a:2385::8]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20712, ipnet:2001:8b0::/32, country:GB]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[polarian.dev:+] X-Rspamd-Queue-Id: 4XMzFT162Cz4H7K X-Spamd-Bar: --- Hello, I am not sure about wg being in both base and the port. However, I have a feeling it is because wireguard has two implementations. You have the generic go implementation which runs in the userspace which is developed and maintained by zx2c4 and other contributors, this is within the port tree. However, there is also a kernel module for in-kernel support for wireguard (see WG(4)) which used to be in the port tree, but was moved into the base system at some point (not sure when). This is an educated guess, I assume it is because older FreeBSD installs will not have the wireguard kernel module, and thus won't ship wg in base, therefore wireguard-go would be used with wireguard-tools which would provide wg. As /usr/bin is higher priority, the wg within base is always used unless you explicitly invoke /usr/local/bin/wg so no conflict should occur here, therefore works for all FreeBSD versions, thats my best guess. Take care, -- Polarian GPG signature: 0770E5312238C760 Jabber/XMPP: polarian@icebound.dev From nobody Tue Oct 8 01:43:04 2024 X-Original-To: questions@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 4XMzLM5gjNz5YlWV for ; Tue, 08 Oct 2024 01:43:07 +0000 (UTC) (envelope-from polarian@polarian.dev) Received: from mail.polarian.dev (mail.polarian.dev [IPv6:2001:8b0:57a:2385::8]) (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 4XMzLM0by9z4J3F for ; Tue, 8 Oct 2024 01:43:07 +0000 (UTC) (envelope-from polarian@polarian.dev) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=polarian.dev header.s=polarian header.b=oF3HG2Xy; spf=pass (mx1.freebsd.org: domain of polarian@polarian.dev designates 2001:8b0:57a:2385::8 as permitted sender) smtp.mailfrom=polarian@polarian.dev; dmarc=pass (policy=reject) header.from=polarian.dev Received: from Hydrogen (_gateway [192.168.2.1]) by mail.polarian.dev (Postfix) with ESMTPSA id CAE9710A0772 for ; Tue, 08 Oct 2024 01:43:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/relaxed; d=polarian.dev; s=polarian; t=1728351785; bh=tXanLRwEChTEB8GRVoTXM255wGZnrmbcjgq9kdp8TO8=; h=Date:From:To:Subject:In-Reply-To:References; b=oF3HG2XyShtB5Ip2Ef8ZbDFthwv7oTaisipDL/ok0GgJbuT6zAm2PZSZWKpwezdmU rIm6pbkawd0je4Rp+V5LtbaDCs8eiFRaXEygliVhm94qhQc+nBvw6aHBgDQ0Rg3txk TY/o/yWVWBEsOOmvkBy1WhCEeLqzOAkVCvLAPxK4= Date: Tue, 8 Oct 2024 02:43:04 +0100 From: Polarian To: questions@freebsd.org Subject: Re: wireguard confusion Message-ID: <20241008024304.5ff138a9@Hydrogen> In-Reply-To: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> X-Mailer: Claws Mail 3.20.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.41 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.995]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; NEURAL_HAM_LONG(-0.93)[-0.929]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[polarian.dev,reject]; R_DKIM_ALLOW(-0.20)[polarian.dev:s=polarian]; R_SPF_ALLOW(-0.20)[+ip6:2001:8b0:57a:2385::8:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20712, ipnet:2001:8b0::/32, country:GB]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[polarian.dev:+] X-Rspamd-Queue-Id: 4XMzLM0by9z4J3F X-Spamd-Bar: --- Ah, Seems I overthought it, it was simply because of the scripts requiring bash and therefore can't be imported into base. Little nitpick at this, can't you exclude wg from the port then? It has almost no benefit other than 61K of storage space, but it would save confusion :P Take care, -- Polarian GPG signature: 0770E5312238C760 Jabber/XMPP: polarian@icebound.dev From nobody Tue Oct 8 01:45:33 2024 X-Original-To: questions@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 4XMzPD62Drz5Ylk6 for ; Tue, 08 Oct 2024 01:45:36 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XMzPD4jWrz4K7g; Tue, 8 Oct 2024 01:45:36 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728351936; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=msyb4UN6FiYEVoSOuLha+mSt9HTRmKIdepBey4ccUes=; b=i7ssQLFCXq9XM2bQ0vEJgBBb8/12znQ9qM/R19HVLcNSRA39ibtMnZkYPOnw1Jp4hjl6jp xeBNeSZTAskm47AH/SWNuXl/ca6u7UcILC7VFkwZ4UGC1YX0PSLM8ILjfDbfMHdTYrzfka uhkZY9ZODOM8yrJ0lCQGHopA9WLwtKiwnsSZ17IAxE4XvZrNVk4HO86j/ohf/qEvX6B3Rw h0XvF+eKf3UEzipwufS6B2NzGvHRr2XgxXXsBulT6pNI4jUypxSPvIDSEv47Lwqg0aeVF1 qmztxoB3bh/ml/cGPylOR+ix36vT9PbEp9l1o/q6yznXY1WtQIrjVecwyipV3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728351936; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=msyb4UN6FiYEVoSOuLha+mSt9HTRmKIdepBey4ccUes=; b=cD4Db6lSdWAg3+udPtyKF1bstvXpHP8gWAlqHaNr/LQ9+0GgX1Af2Lp8fpnTVFThV1LaTm 31tiQoWFhex48THDFAB0fw7D1UG7M7BY/nrkvdxvYrxKWURaGPTIPDC22k+0ZIVN/WSTIY ogahRbgMw3vNazjLSi0PtDU66MqJIKkyc3L6Zzp0Csu4zSgVEFK03pBBj0byRp7cxmtJyT O1/SEiFVMbNFPzZgCa2vlA2xxRADmV17QggIBht1TngzwqTCyCb0rpzjWTpFufbdN5OFaz n1iDmDvVUqkiQEjDcputP57eTUxocJthanbHihclYbfq6eZ5Hnm6kgSjszul7g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1728351936; a=rsa-sha256; cv=none; b=BNUtjidP7ZzhHVKsbt9jsXeqeP08rFpQvQ0qI86RzN41zhVYiLUnOitbK//0Cnky43JoYz myud8K9oS/gcs1KQJslYSqCLOlxf87Xmtfax2XPxEfVEAAdwcQEhEbZJvKZDNVsvZgtlYG Sg1RvwnmP52HzWWhcKpyAk8jXLYx18U5b+g8VY99wnwWtSa0GzuZ5kme6Pu3UwxWYz051s KE8zsNkES2ehm1JZmO1x52FAfpSN8Qqn7c46p25xN/1DFGz0DIJQSIgmiKFOAZTNyy9snu A41mSjNo41jX0ah9HX8ify6+Ghr4KFXuFUV9ZzoRn69vVihVWjXp3zffMUXFwQ== Received: from [10.9.4.95] (unknown [209.182.120.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XMzPC51Tsz1NZ4; Tue, 8 Oct 2024 01:45:35 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> Date: Mon, 7 Oct 2024 20:45:33 -0500 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wireguard confusion To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> Content-Language: en-US Cc: decke@FreeBSD.org From: Kyle Evans In-Reply-To: <20241008024304.5ff138a9@Hydrogen> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/7/24 20:43, Polarian wrote: > Ah, > > Seems I overthought it, it was simply because of the scripts requiring > bash and therefore can't be imported into base. > > Little nitpick at this, can't you exclude wg from the port then? > > It has almost no benefit other than 61K of storage space, but it would > save confusion :P > > Take care, At this point we probably could- all supported versions should have it- but I have no opinion. CC decke@ Thanks, Kyle Evans From nobody Tue Oct 8 15:46:24 2024 X-Original-To: questions@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 4XNL3S0H7Gz5ZXVX for ; Tue, 08 Oct 2024 15:46:28 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Received: from beesty.loosely.org (beesty.loosely.org [IPv6:2600:3c01:e000:4c0::2]) (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 4XNL3Q5GD8z3wmH for ; Tue, 8 Oct 2024 15:46:26 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of fatty.merchandise677@aceecat.org designates 2600:3c01:e000:4c0::2 as permitted sender) smtp.mailfrom=fatty.merchandise677@aceecat.org; dmarc=none Received: from [::1] (helo=beesty ident=itz) by beesty.loosely.org with esmtp (Exim 4.98-4-9cb179d48) (envelope-from ) id 1syCPo-000000001sN-2zA0 for questions@freebsd.org; Tue, 08 Oct 2024 08:46:24 -0700 Date: Tue, 8 Oct 2024 08:46:24 -0700 From: fatty.merchandise677@aceecat.org To: questions@freebsd.org Subject: Re: wireguard confusion Message-ID: Mail-Followup-To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> X-Spamd-Result: default: False [-3.18 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.98)[-0.981]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:63949, ipnet:2600:3c01::/32, country:SG]; MISSING_XM_UA(0.00)[]; FROM_NO_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[aceecat.org]; RCVD_TLS_LAST(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-Rspamd-Queue-Id: 4XNL3Q5GD8z3wmH X-Spamd-Bar: --- On Mon, Oct 07, 2024 at 08:45:33PM GMT, Kyle Evans wrote: > > Little nitpick at this, can't you exclude wg from the port then? > At this point we probably could- all supported versions should have > it- but I have no opinion. CC decke@ Note that the rc bit would have to be modified in that case, as it hardcodes the pathname to /usr/local/bin/wg. If anything, I'd do something to the base copy -- if not delete it, maybe rename it, how about wgtool ? -- Ian From nobody Tue Oct 8 15:47:53 2024 X-Original-To: questions@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 4XNL564M4Dz5XZ75 for ; Tue, 08 Oct 2024 15:47:54 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XNL563pHWz3xkW for ; Tue, 8 Oct 2024 15:47:54 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728402474; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=u6Oe9aiArBAJmFNnR9s0plsQC4EHveTg3JaMCDzWU0Q=; b=n21HSjGIaPH/0t8moMGa/qJLpI3qbVG9yAgdWQ+M4ae6c/Wsg2H7UnyQ/GSHs/rYbhNw3C BRfXA024/i/6jifBleehCcImC2/W0UbyFy2/I/m7QfBCNNChEDQYkgb8tjz8DOAgQlIPg2 p/2/tqJvvNIm2seuZHaGMjCqJ95SG+O210dnYuYZnhudJ+BcQSnrYaSQ5x1xAocO3dwwJQ RUavXv1+FPRQAuMZAHz19t4dzUkqSwVWxCQjv1Bsdyix1n+RLXD14PnQS/3ZiPoyCdXb3u tsDuAEXuQmFKXy64l6ZxI8cVjl60GLy5g7UXulnqDPQUoY69u7czmoHLyd/MtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728402474; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=u6Oe9aiArBAJmFNnR9s0plsQC4EHveTg3JaMCDzWU0Q=; b=a/wFzhAQMiMA4VxheIzEQCfTKQm115Zu2Ope5RokcvWoPqT7S0T7oxPnA2gUN3Qpr1z7QN VPR9ZkkNIstjK0SpJdJ4oGUqwTAGo7eEoXABPGXhpB4VK2OUqt3F7HdNcVRu0ESSq+yVM7 EdSXC2FcP0tMu4Fl+5gcfPOmokDv8QURlsrmv6x3SFFJGy7WbJmR8Ci9v/IzqTgMPHrzaA iVeNY0AhFZ4LKsLOJwaNI1gPh/UF2mMnI9kbiJndOsJ80opHN69tTXAMdphgrF4tLSuDA7 cJkCv/UP9WX6ZbJeauBZQV+/vC6Q9H21tJYOWocPdcnSTD/OU8XtvR9z0cDbMQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1728402474; a=rsa-sha256; cv=none; b=v1fb2rmKKDeZ4/5hvqtoZECEXbaLyLHSHXRePGIpp1cNgjs7/mNWbqZbouCKMlFQALZt1t S7+zffCcg+HJW3zXPXyJAdNFsrYuGdxhGXxaPVA7L8nM9knAxdsRH18mpHnsf/Fy+kOLu6 O3KtFj34RWP+ANOu9RUm77A673VX9P3L0Jk3HlUv+GbBmxWPgbZSK7F2exRZCIi3OpNm0v g+V1b5vd6L6TViOf0GrzFzyXQzLI+RffVL46EKX1FzajBL2BXzO/023BBcX0WYN6MQ8pBV 8RWaPQ0v8fzwcOFICbzMj9F8jstzKMYslE7XmQZz7+WWbusOPPDSsy40TZYH7g== Received: from [10.9.4.95] (unknown [209.182.120.176]) (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 did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XNL562Cp1zQr0 for ; Tue, 8 Oct 2024 15:47:54 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: Date: Tue, 8 Oct 2024 10:47:53 -0500 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wireguard confusion To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> Content-Language: en-US From: Kyle Evans In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/8/24 10:46, fatty.merchandise677@aceecat.org wrote: > On Mon, Oct 07, 2024 at 08:45:33PM GMT, Kyle Evans wrote: > >>> Little nitpick at this, can't you exclude wg from the port then? > >> At this point we probably could- all supported versions should have >> it- but I have no opinion. CC decke@ > > Note that the rc bit would have to be modified in that case, as it > hardcodes the pathname to /usr/local/bin/wg. > That can be fixed. > If anything, I'd do something to the base copy -- if not delete it, > maybe rename it, how about wgtool ? > I can't think of a good reason to do this, no. You should be using the version in base, not the version in ports. Thanks, Kyle Evans From nobody Wed Oct 9 00:48:01 2024 X-Original-To: questions@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 4XNZ4Z47bQz5YbZ0 for ; Wed, 09 Oct 2024 00:48:14 +0000 (UTC) (envelope-from polarian@polarian.dev) Received: from mail.polarian.dev (mail.polarian.dev [IPv6:2001:8b0:57a:2385::8]) (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 4XNZ4X6VNSz4m3w for ; Wed, 9 Oct 2024 00:48:12 +0000 (UTC) (envelope-from polarian@polarian.dev) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=polarian.dev header.s=polarian header.b=IGxg91qi; spf=pass (mx1.freebsd.org: domain of polarian@polarian.dev designates 2001:8b0:57a:2385::8 as permitted sender) smtp.mailfrom=polarian@polarian.dev; dmarc=pass (policy=reject) header.from=polarian.dev Received: from Hydrogen (_gateway [192.168.2.1]) by mail.polarian.dev (Postfix) with ESMTPSA id 480E110A0772 for ; Wed, 09 Oct 2024 00:48:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/relaxed; d=polarian.dev; s=polarian; t=1728434883; bh=8IsZID5vX4KkDivsUBD3zBxUP1sFqY0wrwIDI9mONII=; h=Date:From:To:Subject:In-Reply-To:References; b=IGxg91qi0qs6H3JzcLfy0JVmHUJQo/4kwbuGg9FWd8A8x6DHuMTWu8bz2gIhH9lHx ETgIAE1CaHWphQ1VEVP/P+b6+/LFK82L52u97Rv4uE51w1ItD5CQsTj1sBQxfF3L3R TBj/541t5EFgwkYd4X5iZA4wzRxNSi/SyubxmEBs= Date: Wed, 9 Oct 2024 01:48:01 +0100 From: Polarian To: questions@freebsd.org Subject: Re: wireguard confusion Message-ID: <20241009014801.60e084f9@Hydrogen> In-Reply-To: References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> X-Mailer: Claws Mail 3.20.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.41 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.91)[-0.909]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[polarian.dev,reject]; R_DKIM_ALLOW(-0.20)[polarian.dev:s=polarian]; R_SPF_ALLOW(-0.20)[+ip6:2001:8b0:57a:2385::8]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20712, ipnet:2001:8b0::/32, country:GB]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[polarian.dev:+] X-Rspamd-Queue-Id: 4XNZ4X6VNSz4m3w X-Spamd-Bar: --- Hello, As for the scripts not being ported, wg-quick can be omitted and you could use ifconfig directly within rc.conf. However, this is not clean, nor secure in the slightest, as you would need to stick your private key in the rc.conf which by default can be read by any user. It would be nice if WG(4) could load configs natively without needing a script to do so, in the same format as wg-quick does (look for /etc/wireguard/.conf), therefore no bash needed, and it can be baked into the base system easily without relying on third party scripts. I assume the problem with this is someone has to code it. > > If anything, I'd do something to the base copy -- if not delete it, > > maybe rename it, how about wgtool ? > > > > I can't think of a good reason to do this, no. You should be using > the version in base, not the version in ports. I would like to point out that this entire thread is about wireguard confusion, and you want to rename the standard name (wg) to a non-standard name, even if this was a good idea, this would cause even more confusion. > >>> Little nitpick at this, can't you exclude wg from the port then? > > > >> At this point we probably could- all supported versions should have > >> it- but I have no opinion. CC decke@ > > > > Note that the rc bit would have to be modified in that case, as it > > hardcodes the pathname to /usr/local/bin/wg. > > > > That can be fixed. I am a little confused why you would hardcode the path to wg in the script and not use whats in $PATH (which, as I explained in my first email in this thread, defaults to /usr/bin/wg), maybe someone knows the reason for this? (I am curious) Take care, -- Polarian GPG signature: 0770E5312238C760 Jabber/XMPP: polarian@icebound.dev From nobody Wed Oct 9 00:54:40 2024 X-Original-To: questions@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 4XNZD850Sdz5Ybd1 for ; Wed, 09 Oct 2024 00:54:48 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XNZD847CCz4nBc for ; Wed, 9 Oct 2024 00:54:48 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728435288; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tiWYsUl2LJIU4pObjZ7e3NkvsflihDaMqMHwBwwcXe8=; b=VcLNT5+tieEKK16vNrslbSVE9rPIjFL/YLkCs7pVmbIN1IXaQXR6AKbZ6xocHviYccP1B0 OvS+xNUzE1gDiolxNWfK7d+KEtRAw5ipyEZQCVIn5LHIbVbZpoULl4BVEdB9RjU/yfMn4O jIEyeZAb6Vq5fW336xF7rAHWnc4pLbtaH5bEt8gXoN7+6XXo3KcFPM/6/PJmc1sSmUaz71 uG1b9zGBD5tyRa7/2KWZxc+iezFhIm/WEYb6ZV/ScX844BENpLtnygXQYK0AXv8J/8wvhM a1YMewAiAhG8hp48020yeJBdhg5vHoLz4mct6sqkGm8WoSkbqcyqkYXylb2aaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728435288; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tiWYsUl2LJIU4pObjZ7e3NkvsflihDaMqMHwBwwcXe8=; b=LjwRX9PefWRN6BEoxHTm9qsU1c/lo9ZCCMiNMmX25MgZTMJFPSfzuKoSbBt39RLUXGr6do 0ln6xlZMVDfA2jawNxgBhRIVKK/7b9WaGtxjdq1XURQpL0DjxkrqXHC6GSpCP2LhSXQDWm 7tNnT9YtFECkZAODud1sYPxUTEtqysNJ7W14jPr4U2rZNzFsM3OH6DKkxY9iG7yYW297lV 1WvUkLx7oBqIay/gbOugyGOcNM88jIfNFCMTJywylRXYaTnG0scXkb7n7HDU+tr1AjW6QJ YQxJAd9uEavmdGgIm7s5gQ0rBCK8gnJetW8CAeZoMwdg4BPYNN48x9FFkyKcTA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1728435288; a=rsa-sha256; cv=none; b=qId0KAEXt8uWJxxAA07y+RNQEqkITYxpo+Axjb3DclVxvIUnG42qTLnirSQFvG5qbuk/5f 6qm8EW5KdX7vL6A8BMVJyB8HYQF+0o5KOysvb29tO7vrvwaP4Eo+T+ElTatWmm9y6AnrIZ m0tfeqDnDaji4qMqj3vjxK+XHJdRmvo+u3uBF92CrZpP/cG8rgeH/PMZNNiC1Jq4laEnoH uC4mSWpRCaLabr3Z7uA3XaQDQajZFBNaYu9XQlgjOdYwKUR8a/9DhfBWpYh7pylxloOEfs dQWRlMXfIEx80bgABnA0Dqgt3bGJ5bP1ZgyaN/k+y8gS9lYDQE+RcjgWY/o7iw== Received: from [10.9.4.95] (unknown [209.182.120.176]) (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 did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XNZD73Qpdzbv4 for ; Wed, 9 Oct 2024 00:54:46 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> Date: Tue, 8 Oct 2024 19:54:40 -0500 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wireguard confusion To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> <20241009014801.60e084f9@Hydrogen> Content-Language: en-US From: Kyle Evans In-Reply-To: <20241009014801.60e084f9@Hydrogen> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/8/24 19:48, Polarian wrote: > Hello, > > As for the scripts not being ported, wg-quick can be omitted and you > could use ifconfig directly within rc.conf. > > However, this is not clean, nor secure in the slightest, as you would > need to stick your private key in the rc.conf which by default can be > read by any user. > > It would be nice if WG(4) could load configs natively without needing a > script to do so, in the same format as wg-quick does (look for > /etc/wireguard/.conf), therefore no bash needed, and it can > be baked into the base system easily without relying on third party > scripts. I assume the problem with this is someone has to code it. > wg(8) can read that style of configuration, but wg-quick(8) adds some niceties on top of that that it won't understand. I think DNS is the main one, which I wouldn't think would be too hard to parse out. >>>>> Little nitpick at this, can't you exclude wg from the port then? >>> >>>> At this point we probably could- all supported versions should have >>>> it- but I have no opinion. CC decke@ >>> >>> Note that the rc bit would have to be modified in that case, as it >>> hardcodes the pathname to /usr/local/bin/wg. >>> >> >> That can be fixed. > > I am a little confused why you would hardcode the path to wg in the > script and not use whats in $PATH (which, as I explained in my first > email in this thread, defaults to /usr/bin/wg), maybe someone knows the > reason for this? (I am curious) > You can't count on /usr/local/bin being in $PATH in rc scripts, so for things that come from ports you have to hardcode it. For wg in particular, the version in base comes along quite far after the version in ports and the ports script just hasn't been adopted to use it. The version in base is technically safer, though, as we could theoretically change the configuration interface for wg interfaces and the version in base is generally guaranteed to work with the kmod that it ships with. Thanks, Kyle Evans From nobody Wed Oct 9 10:37:10 2024 X-Original-To: freebsd-questions@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 4XNq8K0vTpz5YMjQ for ; Wed, 09 Oct 2024 10:37:21 +0000 (UTC) (envelope-from lumiwa@dismail.de) Received: from mx1.dismail.de (mx1.dismail.de [78.46.223.134]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XNq8H54xQz4MMg for ; Wed, 9 Oct 2024 10:37:19 +0000 (UTC) (envelope-from lumiwa@dismail.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=dismail.de header.s=20190914 header.b=aqXbYp5H; spf=pass (mx1.freebsd.org: domain of lumiwa@dismail.de designates 78.46.223.134 as permitted sender) smtp.mailfrom=lumiwa@dismail.de; dmarc=pass (policy=reject) header.from=dismail.de Received: from mx1.dismail.de (localhost [127.0.0.1]) by mx1.dismail.de (OpenSMTPD) with ESMTP id ac0cf28b for ; Wed, 9 Oct 2024 12:37:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=dismail.de; h=date:from :to:subject:message-id:mime-version:content-type :content-transfer-encoding; s=20190914; bh=UVMiNgjQt48Qj02Qe0UfK FwYQrI6kqqn/+EGW326yQ4=; b=aqXbYp5H+6fwIHBOfUkDLoN3+SD9jhvbBMSSn 3vETMoIcratftaa5NCwA1AceV8kby+ZDXmoaXOWFZzrOswBD3VgC1T8AHxmBM4PU yvbpWWA5Jzcx0gNexB5DAvPCY/OSjD8Ls6rPfvx4jl3ETzrAni6S8T9iD/K1gy+Q 6SPWWvwSyjJP6Vvhg33LpfovYe/HeZGqKJbPSxo9L7IncSO4bNPjSZaEa21imY/2 fxXdA9Ci31laJOKeUjWEGe8//sM1Yah6ychsUS0xQ4C39Pi6gd8oHPZAenyl2etV kx4jRHynIKOCC+iyKYf6HEkesy6APyeHdga/iUIIaRE+7QhBQ== Received: from smtp2.dismail.de ( [10.240.26.12]) by mx1.dismail.de (OpenSMTPD) with ESMTP id 4cb07f49 for ; Wed, 9 Oct 2024 12:37:16 +0200 (CEST) Received: from smtp2.dismail.de (localhost [127.0.0.1]) by smtp2.dismail.de (OpenSMTPD) with ESMTP id 39f66ea0 for ; Wed, 9 Oct 2024 12:37:16 +0200 (CEST) Received: by dismail.de (OpenSMTPD) with ESMTPSA id 446d9bfd (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Wed, 9 Oct 2024 12:37:15 +0200 (CEST) Date: Wed, 9 Oct 2024 06:37:10 -0400 From: LuMiWa To: FreeBSD Questions Subject: FreeBSD releases Message-ID: <20241009063710.09572e05@dismail.de> X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-5.10 / 15.00]; DWL_DNSWL_LOW(-1.00)[dismail.de:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[dismail.de,reject]; R_DKIM_ALLOW(-0.20)[dismail.de:s=20190914]; R_SPF_ALLOW(-0.20)[+ip4:78.46.223.134]; RCVD_IN_DNSWL_LOW(-0.10)[78.46.223.134:from]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:78.46.0.0/15, country:DE]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; DKIM_TRACE(0.00)[dismail.de:+] X-Rspamd-Queue-Id: 4XNq8H54xQz4MMg X-Spamd-Bar: ----- Hi! As a binary packages user I have one question, please. For example: releng/14.1 14.1-RELEASE June 4, 2024 expected eol March 31, 2025 This mean that are all packages built on version 14.0 for six months. This mean if we want applications built for 14.1 we need to use ports, special for apps like drm-kmod and more and build by ourselves. Am I wright? Thank you. --=20 =E2=80=9CI hate books; they only teach us to talk about things we know noth= ing about.=E2=80=9D =E2=80=95 Jean-Jacques Rousseau=20 From nobody Wed Oct 9 18:25:58 2024 X-Original-To: questions@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 4XP1YD3gPkz5YrMV for ; Wed, 09 Oct 2024 18:26:08 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Received: from beesty.loosely.org (beesty.loosely.org [IPv6:2600:3c01:e000:4c0::2]) (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 4XP1YB554xz4G49 for ; Wed, 9 Oct 2024 18:26:06 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of fatty.merchandise677@aceecat.org designates 2600:3c01:e000:4c0::2 as permitted sender) smtp.mailfrom=fatty.merchandise677@aceecat.org; dmarc=none Received: from [::1] (helo=beesty ident=itz) by beesty.loosely.org with esmtp (Exim 4.98-4-9cb179d48) (envelope-from ) id 1sybNm-000000002XU-1VsQ for questions@freebsd.org; Wed, 09 Oct 2024 11:25:58 -0700 Date: Wed, 9 Oct 2024 11:25:58 -0700 From: fatty.merchandise677@aceecat.org To: questions@freebsd.org Subject: Re: wireguard confusion Message-ID: Mail-Followup-To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> <20241009014801.60e084f9@Hydrogen> <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> X-Spamd-Result: default: False [-3.08 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.997]; NEURAL_HAM_SHORT(-0.88)[-0.879]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:63949, ipnet:2600:3c01::/32, country:SG]; MISSING_XM_UA(0.00)[]; FROM_NO_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[aceecat.org]; RCVD_TLS_LAST(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-Rspamd-Queue-Id: 4XP1YB554xz4G49 X-Spamd-Bar: --- On Tue, Oct 08, 2024 at 07:54:40PM GMT, Kyle Evans wrote: > the version in base comes along quite far after the version in ports > and the ports script just hasn't been adopted to use it. I am still confused by this bit. The --version output is the same for both. If there are freebsd specific patches maybe the --version should be tweaked to make that obvious. > The version in base is technically safer, though, as we could > theoretically change the configuration interface for wg interfaces > and the version in base is generally guaranteed to work with the > kmod that it ships with. I can understand this part. But why can't we just adopt the rc.script into base, too, and get rid of the port entirely? -- Ian From nobody Wed Oct 9 18:36:09 2024 X-Original-To: questions@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 4XP1mq2ML7z5Yrj8 for ; Wed, 09 Oct 2024 18:36:11 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XP1mq1jVgz4HZS for ; Wed, 9 Oct 2024 18:36:11 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728498971; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=m//nUCa7yDWq1+sUSiA63L9lf3YtXHubW1IAfvl6yFA=; b=tiZKlAB/obtnNtN5U5JBCj8VT68N63Y25V/syKJkdN62PoMh7ctnPSlMYaW4ddFkgXdpzV f6FnOFdWtH+F3YpnNCqXxKYoCQi87vLt78GTDU12nnAhuRPaG6KBHH9biWaB4FDQTww9d4 sRNx12sFitBzHvKCAJF3Mv654YQaQ3nUYQF8+iUImwm7XkwGDoX3CegOlCgghVVpQ+jUJl 2ehj3//8G/Lbrg8RtmrTmoa3Ry2o0T4XG4qnBhAvodA9+OoiXKCm7LsTECc4FNmOD2elrf HiF/22fX+1+zSCFKOzSzCWhUelcLedkY7b0+Vd5a8HEjZT+XlhuDJuyej5EwaQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728498971; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=m//nUCa7yDWq1+sUSiA63L9lf3YtXHubW1IAfvl6yFA=; b=NI0hGDZlDlVjrAOsvKNfb1aqOx/ThFLMGOYoAtO5iA5KCQ7oT+bA36mxkAas56O+JiD7f3 axVUi7VoHd7g3eC1dmvPyCKKwgqfHrANJEIccdQw1UyT++oXuM9MSVllJp4Y5UPqIuqtnM 1krgDYA0xExY4OPbDELvvNWewTFUEhv/iYcjjP6XPDXyompaEL9rsGU3EEtFXzRI06DT7g PwkzDFTFELgjwzwaPDoKnHTNUPZWh4LCmNKMB2wi3KIE5tfOBqe+z3pFMR8Gu1KD/R8bWh sXpnoLudF8hli9UX22oXWBCxrfTu3FbvOF0ebMNbYTgsIDLtb3VPpEySJxlMTA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1728498971; a=rsa-sha256; cv=none; b=lSj9RPGNBuRSWwEi3ypdAfo4LG1hUUm7wHNCqbfkgK13d8uQ2NVpvMrtQwtCrBLG3QlMRY A03k6ZMVXvk6+0H9K3+FZ639hAFRpk7Dh6RL9llWeYquCAgqe4TNt1EsbKYNgFwIHxr6va iow+oqnH7E74pbIbQknagevVm3QMalLHz3PfqUkRWyP3lQqMPCtaWsZqXoHC4428QDxrpQ suy+CiovPsOy8Cx269BfihZ7W0oK83hlr2zH4cRjkuqDyLyokeYlaNwt3z259b/enlJuoO cjZdHmHF07LNkR3v85rBxXVwdIUWyp0LCElpnTFeDK83qUdNJLDwOhRu/KyAbg== Received: from [10.9.4.95] (unknown [209.182.120.176]) (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 did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XP1mq02N3z1F2V for ; Wed, 9 Oct 2024 18:36:10 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: Date: Wed, 9 Oct 2024 13:36:09 -0500 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wireguard confusion To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> <20241009014801.60e084f9@Hydrogen> <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> Content-Language: en-US From: Kyle Evans In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/9/24 13:25, fatty.merchandise677@aceecat.org wrote: > On Tue, Oct 08, 2024 at 07:54:40PM GMT, Kyle Evans wrote: > >> the version in base comes along quite far after the version in ports >> and the ports script just hasn't been adopted to use it. > > I am still confused by this bit. The --version output is the same for > both. If there are freebsd specific patches maybe the --version should > be tweaked to make that obvious. > There are no FreeBSD specific patches today. >> The version in base is technically safer, though, as we could >> theoretically change the configuration interface for wg interfaces >> and the version in base is generally guaranteed to work with the >> kmod that it ships with. > > I can understand this part. But why can't we just adopt the rc.script > into base, too, and get rid of the port entirely? > The rc script requires wg-quick(8), which relies on bash. We could do it, but I don't personally have time. Thanks, Kyle Evans From nobody Wed Oct 9 19:08:53 2024 X-Original-To: questions@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 4XP2Vf2pGxz5Ysq5 for ; Wed, 09 Oct 2024 19:08:58 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Received: from beesty.loosely.org (beesty.loosely.org [IPv6:2600:3c01:e000:4c0::2]) (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 4XP2Vc2KL6z4LPY for ; Wed, 9 Oct 2024 19:08:55 +0000 (UTC) (envelope-from fatty.merchandise677@aceecat.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of fatty.merchandise677@aceecat.org designates 2600:3c01:e000:4c0::2 as permitted sender) smtp.mailfrom=fatty.merchandise677@aceecat.org; dmarc=none Received: from [::1] (helo=beesty ident=itz) by beesty.loosely.org with esmtp (Exim 4.98-4-9cb179d48) (envelope-from ) id 1syc3J-0000000037K-1Yxw for questions@freebsd.org; Wed, 09 Oct 2024 12:08:53 -0700 Date: Wed, 9 Oct 2024 12:08:53 -0700 From: fatty.merchandise677@aceecat.org To: questions@freebsd.org Subject: Re: wireguard confusion Message-ID: Mail-Followup-To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> <20241009014801.60e084f9@Hydrogen> <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-3.19 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.997]; NEURAL_HAM_SHORT(-0.99)[-0.992]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:63949, ipnet:2600:3c01::/32, country:SG]; MISSING_XM_UA(0.00)[]; FROM_NO_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[aceecat.org]; RCVD_TLS_LAST(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-Rspamd-Queue-Id: 4XP2Vc2KL6z4LPY X-Spamd-Bar: --- On Wed, Oct 09, 2024 at 01:36:09PM GMT, Kyle Evans wrote: > The rc script requires wg-quick(8), which relies on bash. Not the one I see in wireguard-tools-lite. Maybe I should have been specific that's the package I installed. Meanwhile, I just removed the package and copied the script manually into /usr/local/etc/rc.d, then edited the pathname. Works without a problem for now. But not sure what happens if base puts an equally named script into /etc/rc.d. -- Ian From nobody Wed Oct 9 19:38:18 2024 X-Original-To: questions@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 4XP38X3F4Mz5YvTZ for ; Wed, 09 Oct 2024 19:38:20 +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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XP38X2jW9z4Qbt for ; Wed, 9 Oct 2024 19:38:20 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728502700; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3DRF+B1dls9euvnWYo9ZqwtmwoZKjzGWP1LjHNJn1LI=; b=etHYwLE3tyCu0WTvv5g2wP3TxnUCZ+2QYsT402WhJi3w0Gi6fYZMFcbKlut2WbRlpZ47yW N4n+d+kveHqlyGtE9LgkYq2uFK0SiyKb1La/TYDFwqi6IsZDj8pQZma8Fc/hdio5vTphYB 9t9lZ9JRFIpfZWvKX3TkUw0P08l0X/wC8UIZ8V52rkk/xKdtRfWDoIL+n4u1nwMAGFWnKb GhQJ9NOjqY/Af040iQ2yueT33GC712xvk2y75KM2WTkdEaDYXFfaEISXtobYLfLcZhsKYY 2OiNM+EVrcbNF0/QsjCkxtCAMqdg0OSrKs2LZ0/+ptCpRAhezxsuzJAg3KPR4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728502700; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3DRF+B1dls9euvnWYo9ZqwtmwoZKjzGWP1LjHNJn1LI=; b=upHUnnJ0leN0mLG9X/T3af2f5PSfmquSc+N9VNRGINtVTmkb3XTlaKl0JrGIION0KfGaBz 5ZfDKvF9+azIqYHdx4dlus9NnDicLntSfyV0XwNQhRig2YoWbnH1CkQ5OIoWpZpPjEBezn EBLPuP0BD1y6mRAqy4rJkW/e2JqKyySelS4CMwkh4Xkqecq4AuagHUrBhaL2Fst/euw/cD Wg71mmT1snqqXwJbVpah2PwXr+QFz7zzQAI0V95R97PmQL9BtWWYVVnlp6iVub12oOhIm6 1+jaOTFIndsxyrDmAj5NEXVkpczjd+ictXcZ36TRqb+Kq/sMoHZlhsdcynCFfA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1728502700; a=rsa-sha256; cv=none; b=aNDzEj5Vabpg/hS13rQc0JMlG4nSTFLZ+GbHHGEvKxrx1tjIsWDZm8HEsDmnWwcysCSltB tpkucwrQyhz1WeRf5Um/jlKHwO3JArBT+skl9GBUZqLzq1xChuFpXbHj0s2OEYaYQpc/Wj qEMieqFijlwE6xMrBv1ZRzejutLGJ8IYb+dGofbfXGecv71LkBmwnNdglBI/e9jVvWMrr/ 6/7PGp3M+tczTAQkQc/kpHk30unw7sdbu7z4EGfKJd/a+GhvDpEUOtHzVdUPsUbf44TH9t oFZS6DxJ4plVHt6lcxky9KDLonU49U5mZIyrdhofQEE3KFY3RlqtXllrgCFLzA== Received: from [10.9.4.95] (unknown [209.182.120.176]) (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 did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XP38X12DCz1GlQ for ; Wed, 9 Oct 2024 19:38:20 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: <3672cc7b-2c9a-41c3-8767-669427d0a59c@FreeBSD.org> Date: Wed, 9 Oct 2024 14:38:18 -0500 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wireguard confusion To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> <20241009014801.60e084f9@Hydrogen> <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> Content-Language: en-US From: Kyle Evans In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 10/9/24 14:08, fatty.merchandise677@aceecat.org wrote: > On Wed, Oct 09, 2024 at 01:36:09PM GMT, Kyle Evans wrote: > >> The rc script requires wg-quick(8), which relies on bash. > > Not the one I see in wireguard-tools-lite. Maybe I should have > been specific that's the package I installed. > Oh, neat. TIL there's a lite flavor- that script seems to do effectively the same as the wg-quick version, just without some extra flavor like the DNS capability that you'd get from wg-quick. I like that one, sure. > Meanwhile, I just removed the package and copied the script > manually into /usr/local/etc/rc.d, then edited the pathname. > Works without a problem for now. But not sure what happens if > base puts an equally named script into /etc/rc.d. > IIRC rcorder will see both and, sharing a common rcvar, run both. From nobody Wed Oct 9 23:15:06 2024 X-Original-To: questions@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 4XP7yp6Wffz5Z6l5 for ; Wed, 09 Oct 2024 23:15:14 +0000 (UTC) (envelope-from lexi@le-fay.org) Received: from fuchsia.eden.le-Fay.ORG (fuchsia.eden.le-fay.org [81.187.47.195]) by mx1.freebsd.org (Postfix) with ESMTP id 4XP7yn6rwpz4lS6 for ; Wed, 9 Oct 2024 23:15:13 +0000 (UTC) (envelope-from lexi@le-fay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=le-fay.org header.s=fuchsia header.b=BXj7uuXh; spf=pass (mx1.freebsd.org: domain of lexi@le-fay.org designates 81.187.47.195 as permitted sender) smtp.mailfrom=lexi@le-fay.org; dmarc=none Received: from iris.eden.le-Fay.ORG (iris.eden.le-fay.org [IPv6:fd12:8247:3:1::7]) by fuchsia.eden.le-Fay.ORG (Postfix) with ESMTP id B5676302A2 for ; Wed, 09 Oct 2024 23:15:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=le-fay.org; s=fuchsia; t=1728515706; bh=HsRtKxiaS3G4jiwZX81KgZLdSsOY40DvJkS/OwVctTA=; h=Date:Subject:To:References:From:In-Reply-To; b=BXj7uuXhhzGT82u9osByGYPcRm4Kk2+izd9MZckzKxsmN9ILuAk6v9fUoJ461buhX NRM8FXMLCmOwSrjKxSVaVw6id9jULWuIuVTQ0iuQaj362imAv89HjiEdrkCUgNByVG AhN25LoshM8r7PWfMHek/xZBpoeR4NIljlY66T5s= Received: from [IPV6:2001:8b0:aab5:c110:299c:a8e3:9bad:a32d] (unknown [IPv6:2001:8b0:aab5:c110:299c:a8e3:9bad:a32d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by iris.eden.le-Fay.ORG (Postfix) with ESMTPSA id D048F2C0489 for ; Thu, 10 Oct 2024 00:15:04 +0100 (BST) Message-ID: <05b34bb9-527e-4e4e-b2cf-77a2ca0903fc@le-fay.org> Date: Thu, 10 Oct 2024 00:15:06 +0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: wireguard confusion Content-Language: en-GB To: questions@freebsd.org References: <29044f1d-f835-459d-8e1c-17832580b5d9@FreeBSD.org> <20241008024304.5ff138a9@Hydrogen> <4e50caf7-dd15-4c8c-9a69-b2f7dbee8b46@FreeBSD.org> <20241009014801.60e084f9@Hydrogen> <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> From: Lexi Winter In-Reply-To: <9f0e1fff-daf5-4dd5-a972-1ed73618533a@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.37 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.982]; R_DKIM_ALLOW(-0.20)[le-fay.org:s=fuchsia]; R_SPF_ALLOW(-0.20)[+ip4:81.187.47.195]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20712, ipnet:81.187.0.0/16, country:GB]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[le-fay.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DKIM_TRACE(0.00)[le-fay.org:+] X-Rspamd-Queue-Id: 4XP7yn6rwpz4lS6 X-Spamd-Bar: --- On 09/10/2024 01:54, Kyle Evans wrote: > On 10/8/24 19:48, Polarian wrote: >> It would be nice if WG(4) could load configs natively without needing a >> script to do so, in the same format as wg-quick does (look for >> /etc/wireguard/.conf) [...] > wg(8) can read that style of configuration, but wg-quick(8) adds some > niceties on top of that that it won't understand.  I think DNS is the > main one, which I wouldn't think would be too hard to parse out. a handy way to do this is using /etc/start_if.$interface: # cat /etc/start_if.wg0 #! /bin/sh /usr/bin/wg setconf wg0 /etc/wg/wg0.conf i've been using this a while now and have not run into any problems with it. presumably it would not be too difficult to add an rc.conf knob for this, if anyone cared to do it. From nobody Thu Oct 10 11:57:49 2024 X-Original-To: questions@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 4XPSts31Mvz5YwDd for ; Thu, 10 Oct 2024 11:57:57 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPStq6lC7z47nw for ; Thu, 10 Oct 2024 11:57:55 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id 1A29C4E690; Thu, 10 Oct 2024 04:57:49 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: How to zero a failing disk drive before disposal? List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5116.1728561468.1@segfault.tristatelogic.com> Content-Transfer-Encoding: quoted-printable Date: Thu, 10 Oct 2024 04:57:49 -0700 Message-ID: <5117.1728561469@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.10 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.995]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XPStq6lC7z47nw X-Spamd-Bar: -- I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that is unamb= iguously at death's door: 1 Raw_Read_Error_Rate 0x002f 200 173 051 Pre-fail Always = - 0 3 Spin_Up_Time 0x0027 167 161 021 Pre-fail Always = - 10641 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always = - 155 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always = - 1 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always = - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always = - 829 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always = - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always = - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always = - 80 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always = - 24 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always = - 130 194 Temperature_Celsius 0x0022 126 098 000 Old_age Always = - 26 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always = - 1 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always = - 36 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline = - 32 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always = - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline = - 40 In addition to the above clear indications of failure, "smartctl -t long" = dies almost immediately with a fatal error. Now I plan to dispose of the drive (appropriately, at a proper e-waste rec= ycling place) however there may be some confidential data on the thing that should be wi= ped first... because I'm paranoid. I used to own an old RadioShack bulk tape eraser (basically just a big ele= ctromagnet) that I would use on drives before disposing of them but I don't have that = any more. I could try using smartctl to initiate a secure erase, but for various rea= sons it would just be more convenient if I could just dd /dev/zero to the thing. But th= ere's a catch. According to what I have read, dd will halt if it encounters a write error= . That's a clear problem in this context. Also, according to the dd man page, the co= nv=3Dnoerror option for dd won't really be helpful in this case since that just prevent= s dd from stopping on _input_ errors. Any suggestions? If worse comes to worse I guess I will end up writing my= own tiny little C program to just write 4KB blocks to a designated output file whil= e ignoring all output errors, but I don't want to reinvent the wheel if somebody else= already created something I can use in this context. Suggestions welcome. From nobody Thu Oct 10 12:21:41 2024 X-Original-To: questions@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 4XPTQL1ffwz5Yxpt for ; Thu, 10 Oct 2024 12:21:46 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPTQK2RrFz4DH7 for ; Thu, 10 Oct 2024 12:21:45 +0000 (UTC) (envelope-from guru@unixarea.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of guru@unixarea.de designates 178.254.4.101 as permitted sender) smtp.mailfrom=guru@unixarea.de; dmarc=none Received: from [212.222.85.114] (helo=pureos) by ms-10.1blu.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1sysAo-00C4sF-Vh for questions@freebsd.org; Thu, 10 Oct 2024 14:21:43 +0200 Date: Thu, 10 Oct 2024 14:21:41 +0200 From: Matthias Apitz To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? Message-ID: Reply-To: Matthias Apitz References: <5117.1728561469@segfault.tristatelogic.com> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5117.1728561469@segfault.tristatelogic.com> X-Operating-System: FreeBSD 14.0-CURRENT 1400094 (amd64) X-message-flag: Mails in HTML will not be read! Send only plain text. X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 212.222.85.114 X-Spamd-Result: default: False [-1.80 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:178.254.4.101]; RWL_MAILSPIKE_GOOD(-0.10)[178.254.4.101:from]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[unixarea.de]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:42730, ipnet:178.254.0.0/19, country:DE]; HAS_REPLYTO(0.00)[guru@unixarea.de]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; HAS_XOIP(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; REPLYTO_EQ_FROM(0.00)[] X-Rspamd-Queue-Id: 4XPTQK2RrFz4DH7 X-Spamd-Bar: - El día jueves, octubre 10, 2024 a las 04:57:49 -0700, Ronald F. Guilmette escribió: > I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that is unambiguously at > death's door: > > ... I used once an axe to destroy the (metal) case and slices and then I throw it into the wastebin of my house which is emtied once a week into a big truck and perhaps it content is put on fire. > Any suggestions? If worse comes to worse I guess I will end up writing my own tiny > little C program to just write 4KB blocks to a designated output file while ignoring > all output errors, but I don't want to reinvent the wheel if somebody else already > created something I can use in this context. Overwriting the data will not help. The reading head(s) could be adjusted and read the data on the side of the old track. matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub Annalena Baerbock: "We are fighting a war against Russia ..." (25.1.2023) I, Matthias, I am not at war with Russia. Я не воюю с Россией. Ich bin nicht im Krieg mit Russland. From nobody Thu Oct 10 12:36:00 2024 X-Original-To: questions@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 4XPTlV1yCtz5YynZ for ; Thu, 10 Oct 2024 12:36:38 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-oa1-x2f.google.com (mail-oa1-x2f.google.com [IPv6:2001:4860:4864:20::2f]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPTlV1Tc2z4G7x for ; Thu, 10 Oct 2024 12:36:38 +0000 (UTC) (envelope-from odhiambo@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x2f.google.com with SMTP id 586e51a60fabf-2884e7fad77so512588fac.2 for ; Thu, 10 Oct 2024 05:36:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728563797; x=1729168597; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=R6x7ijRevG0PArY8JLW33/RD4dVqQbOnrim4wUekVbo=; b=P8BNwWcd21zMhimwcWu6+Yy55dRypooV6CJELTX2LPT4o0d4cLQjY80nfe9d1g0TLy WaERisxqbiXMv65VCqB9pb3556QU/dSOkEQSPisLulrPVpRWWUXNSGBmLQkPOn0EMtGy xTb+R55Zc1KLcxddijWGyRYc9ocwjwRiM3l9+TD+x3m8NdltyPsdf/xccjIbriiLzEXb NWIffVlhhUZ75zL3XmSS6DI8XDhuKOYkp5U2ppyDdiodXmMwbdneuvLqxyCR3IL75Bm3 94w9/JKj3D+49etY7fFECztpMLlGG8zYaXA4WT3P5DcWAWL3PXVmTuA3VAXnEhKcut3P 6QjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728563797; x=1729168597; 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=R6x7ijRevG0PArY8JLW33/RD4dVqQbOnrim4wUekVbo=; b=XkdhmnQGA8/ukar+6n+QQCEIZ5L2UKaVhB1jwJDEDp+/WY1Yw10zVdZNroKlIDT2CJ VUKuf8poekVhhFm+ehe9vhjCjWHQJcYqF4No1XRW8XhuI89tW6TLeSrjmtA7JEl2NsrE K1xY7rz6K4dFeN9w0oYcvkPykAn/ekTsoJ3F2LxGSdL0s6XM1RzkI+DtHwa90+hUrA5A uVMJTj/6owXfOT5w+fMdueSCVD8NACwKzeXCRQ9iVXr4s31IyGKDCJwag9r6269dgRh0 hx2U+E1hk993OQ51CqZkwF552yDVH1t8IyWx+M6c+4Hh/7NyHXvXUx/dM/0FdJeWjKju ZItw== X-Gm-Message-State: AOJu0YxMO1GrrxIeiHNjIEdYRXTApzFz6ULzOOzDkvAg0RkW/6FCLF0+ aXczGlznJjOxiVHt0DnPOEJMIGRs//tsxg2pQLkK4uEds6WUJj8CR6G/bjPEGVvT0BL/qdsuqzI 8EL5LbtToSgAGhYNuQE4ymAxSr0eGOdwBDh0= X-Google-Smtp-Source: AGHT+IG9nbPxGHB2s2rgdy/9xEg6HZo7GNClo9092dEJUkK15FE5dzsrkL0TNoaTwkT2kbAonEmV299dMw8quUpJF+g= X-Received: by 2002:a05:6871:e413:b0:260:e713:ae8b with SMTP id 586e51a60fabf-288342e4acfmr4097198fac.20.1728563797101; Thu, 10 Oct 2024 05:36:37 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: <5117.1728561469@segfault.tristatelogic.com> In-Reply-To: From: Odhiambo Washington Date: Thu, 10 Oct 2024 15:36:00 +0300 Message-ID: Subject: Re: How to zero a failing disk drive before disposal? To: Matthias Apitz Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="0000000000001915a206241e9fcc" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Queue-Id: 4XPTlV1Tc2z4G7x X-Spamd-Bar: ---- --0000000000001915a206241e9fcc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Oct 10, 2024 at 3:21=E2=80=AFPM Matthias Apitz w= rote: > El d=C3=ADa jueves, octubre 10, 2024 a las 04:57:49 -0700, Ronald F. Guil= mette > escribi=C3=B3: > > > I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that is > unambiguously at > > death's door: > > > > ... > > I used once an axe to destroy the (metal) case and slices and > then I throw it into the wastebin of my house which is emtied once a > week into a big truck and perhaps it content is put on fire. > > > Any suggestions? If worse comes to worse I guess I will end up writing > my own tiny > > little C program to just write 4KB blocks to a designated output file > while ignoring > > all output errors, but I don't want to reinvent the wheel if somebody > else already > > created something I can use in this context. > > Overwriting the data will not help. The reading head(s) could be > adjusted and read the data on the side of the old track. > > matthias > I open the case, remove the platters and the magnets (for use elsewhere), and repurpose the casing! --=20 Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2=AF :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] --0000000000001915a206241e9fcc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Oct 10, 2024 at 3:21=E2=80=AF= PM Matthias Apitz <guru@unixarea.de<= /a>> wrote:
E= l d=C3=ADa jueves, octubre 10, 2024 a las 04:57:49 -0700, Ronald F. Guilmet= te escribi=C3=B3:

> I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that is u= nambiguously at
> death's door:
>
> ...

I used once an axe to destroy the (metal) case and slices and
then I throw it into the wastebin of my house which is emtied once a
week into a big truck and perhaps it content is put on fire.

> Any suggestions?=C2=A0 If worse comes to worse I guess I will end up w= riting my own tiny
> little C program to just write 4KB blocks to a designated output file = while ignoring
> all output errors, but I don't want to reinvent the wheel if someb= ody else already
> created something I can use in this context.

Overwriting the data will not help. The reading head(s) could be
adjusted and read the data on the side of the old track.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 matthias



--
--0000000000001915a206241e9fcc-- From nobody Thu Oct 10 12:46:32 2024 X-Original-To: questions@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 4XPTzg6H0Nz5Z0c2 for ; Thu, 10 Oct 2024 12:47:11 +0000 (UTC) (envelope-from kudzu@tenebras.com) Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPTzg5TTvz4PGw for ; Thu, 10 Oct 2024 12:47:11 +0000 (UTC) (envelope-from kudzu@tenebras.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-7ea06275ef2so572216a12.0 for ; Thu, 10 Oct 2024 05:47:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tenebras-com.20230601.gappssmtp.com; s=20230601; t=1728564430; x=1729169230; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QT36baqx3/ZGKupN04dTSUNrTyyoXC8zMuwLUg7A7Mo=; b=QAPPIpYPnWMGnh5O20VlAVu7thxT7eTmkaDOQu89zEbwXHUvokT+IyS027E8Gu7IKW zA7i5+4i5Boqx0H9+jUnG2S6qWcekjIJJgRpHURlFJ1HgkhN+HSHgijdkYLTyxwsnCJS qMKReBsUKBpioGZpStTh4k0l/Ekb6LHeUihAgiamg3Xme/FgYGG6WqH4YsZYJGTL2wsk 5m34GfAV0wdtl+3eshS3rhS12YtEJuvFBc5mIGp4pNQK57f6VwD8gtARuoxnlmMjhT0l vuIa89mCAWQybeSV8cSzk58s5UfWSj6Xn8Bpdga6bz6QzlAMyV6X8Jl0SL0SKhdhNfhh TxTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728564430; x=1729169230; 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=QT36baqx3/ZGKupN04dTSUNrTyyoXC8zMuwLUg7A7Mo=; b=cZXlSUKmVIK84Mpb44Ato7e1bzxn5CUJv2yH7NNXsSl6rbeyaDlbMMbxOggpjZT7dd v9cpRnNSsB6baA+lDbGDqSIP04FiDFCr5jyOXN+kIVyw8O/aXQM3KfuXNrDAGssvsnFC GM654WXLKqw9cUynQM/4uzt1UKngGn1u0+0x6fdTKJMszrWhDXevZIp6ySeyS83Dc0I9 VArN9K6isqjQ0FJZXMkeYMejt0Dprh0f9MeivQ3sK2wgZkv1RAtNqox/tshWIQgznbAW NYCuwnPxKm99f227T1W89eUVAHFWZfhi/xrGfIXlQM2MRG9ce2ZaATVKidop9KwcX4cG aGSQ== X-Gm-Message-State: AOJu0YxoAvDDg8BLQ1XltX/TXhnnKrvMVV/7jixbnheklF10SRhosoCA GXPxrPRjJtFLPmjfl8CKjBKFHFUADezII4+WOnfWH8uHhpeWmJB9k84BPEuP6NKfH8ljYogB3CK tTCnujLTrvPGCyeVC+ZcPeIUuz/mWBhsqQCKeH0L8W4KoIMry X-Google-Smtp-Source: AGHT+IFbXTqoqteRYtPo4WwL6FN2MENmxqEp4EWrbJsDaMaWh1bB/mRfg0eJ1hsoQQ2R3HoA+Cjy6OfYe5EkZyQnpII= X-Received: by 2002:a05:6a21:31c8:b0:1d8:ad90:8656 with SMTP id adf61e73a8af0-1d8ad90865cmr6278614637.23.1728564430464; Thu, 10 Oct 2024 05:47:10 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: <5117.1728561469@segfault.tristatelogic.com> In-Reply-To: <5117.1728561469@segfault.tristatelogic.com> From: Michael Sierchio Date: Thu, 10 Oct 2024 08:46:32 -0400 Message-ID: Subject: Re: How to zero a failing disk drive before disposal? To: "Ronald F. Guilmette" Cc: questions@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d98c0906241ec408" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XPTzg5TTvz4PGw X-Spamd-Bar: ---- --000000000000d98c0906241ec408 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Oct 10, 2024 at 7:58=E2=80=AFAM Ronald F. Guilmette wrote: > I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that is > unambiguously at > death's door: > > Any suggestions? If worse comes to worse I guess I will end up writing m= y > own tiny > little C program to just write 4KB blocks to a designated output file > while ignoring > all output errors, but I don't want to reinvent the wheel if somebody els= e > already > created something I can use in this context. There is no method of writing to a disk that can reliably delete or obscure all data =E2=80=93 modern disk drives silently remap sectors, making them unavailable to the host for writes. If the data on the drive is particularly sensitive, physical destruction of the media is the best approach. The DOD method is crush, then burn. ;-) =E2=80=93 M --000000000000d98c0906241ec408 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, Oct 10, 2024 at 7:58=E2=80=AFAM R= onald F. Guilmette <rfg@tristat= elogic.com> wrote:
I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) tha= t is unambiguously at
death's door:
=C2=A0
Any suggestions?=C2=A0 If worse comes to worse I guess I will end up writin= g my own tiny
little C program to just write 4KB blocks to a designated output file while= ignoring
all output errors, but I don't want to reinvent the wheel if somebody e= lse already
created something I can use in this context.

There is no method of writing to a disk that can reliably delete or obscu= re all data =E2=80=93 modern disk drives silently remap sectors, making the= m unavailable to the host for writes.=C2=A0 If the data on the drive is par= ticularly sensitive, physical destruction of the media is the best approach= .=C2=A0 The DOD method is crush, then burn. ;-)

=E2=80=93 M=C2=A0
--000000000000d98c0906241ec408-- From nobody Thu Oct 10 13:04:32 2024 X-Original-To: questions@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 4XPVMq52HBz5Z1k2 for ; Thu, 10 Oct 2024 13:04:39 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (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 (2048 bits) client-digest SHA256) (Client CN "smarthost1.sentex.ca", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPVMp2gJLz4Skf for ; Thu, 10 Oct 2024 13:04:38 +0000 (UTC) (envelope-from mike@sentex.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:1::12 as permitted sender) smtp.mailfrom=mike@sentex.net; dmarc=none Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [199.212.134.19]) by smarthost1.sentex.ca (8.18.1/8.18.1) with ESMTPS id 49AD4WnS087722 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Thu, 10 Oct 2024 09:04:32 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [IPV6:2607:f3e0:0:4:9551:e8d3:8d0:4668] ([IPv6:2607:f3e0:0:4:9551:e8d3:8d0:4668]) by pyroxene2a.sentex.ca (8.18.1/8.15.2) with ESMTPS id 49AD4Vkj078469 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 10 Oct 2024 09:04:31 -0400 (EDT) (envelope-from mike@sentex.net) Content-Type: multipart/alternative; boundary="------------QZauI1oxGGVzC6dR3gFFe4MQ" Message-ID: <4043e4c9-3365-4b91-ba7e-2004beeaa7ac@sentex.net> Date: Thu, 10 Oct 2024 09:04:32 -0400 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How to zero a failing disk drive before disposal? To: "Ronald F. Guilmette" Cc: questions@freebsd.org References: <5117.1728561469@segfault.tristatelogic.com> Content-Language: en-US From: mike tancsa Autocrypt: addr=mike@sentex.net; keydata= xsBNBFywzOMBCACoNFpwi5MeyEREiCeHtbm6pZJI/HnO+wXdCAWtZkS49weOoVyUj5BEXRZP xflV2ib2hflX4nXqhenaNiia4iaZ9ft3I1ebd7GEbGnsWCvAnob5MvDZyStDAuRxPJK1ya/s +6rOvr+eQiXYNVvfBhrCfrtR/esSkitBGxhUkBjOti8QwzD71JVF5YaOjBAs7jZUKyLGj0kW yDg4jUndudWU7G2yc9GwpHJ9aRSUN8e/mWdIogK0v+QBHfv/dsI6zVB7YuxCC9Fx8WPwfhDH VZC4kdYCQWKXrm7yb4TiVdBh5kgvlO9q3js1yYdfR1x8mjK2bH2RSv4bV3zkNmsDCIxjABEB AAHNHW1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5uZXQ+wsCOBBMBCAA4FiEEmuvCXT0aY6hs 4SbWeVOEFl5WrMgFAl+pQfkCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQeVOEFl5W rMiN6ggAk3H5vk8QnbvGbb4sinxZt/wDetgk0AOR9NRmtTnPaW+sIJEfGBOz47Xih+f7uWJS j+uvc9Ewn2Z7n8z3ZHJlLAByLVLtcNXGoRIGJ27tevfOaNqgJHBPbFOcXCBBFTx4MYMM4iAZ cDT5vsBTSaM36JZFtHZBKkuFEItbA/N8ZQSHKdTYMIA7A3OCLGbJBqloQ8SlW4MkTzKX4u7R yefAYQ0h20x9IqC5Ju8IsYRFacVZconT16KS81IBceO42vXTN0VexbVF2rZIx3v/NT75r6Vw 0FlXVB1lXOHKydRA2NeleS4NEG2vWqy/9Boj0itMfNDlOhkrA/0DcCurMpnpbM7ATQRcsMzk AQgA1Dpo/xWS66MaOJLwA28sKNMwkEk1Yjs+okOXDOu1F+0qvgE8sVmrOOPvvWr4axtKRSG1 t2QUiZ/ZkW/x/+t0nrM39EANV1VncuQZ1ceIiwTJFqGZQ8kb0+BNkwuNVFHRgXm1qzAJweEt RdsCMohB+H7BL5LGCVG5JaU0lqFU9pFP40HxEbyzxjsZgSE8LwkI6wcu0BLv6K6cLm0EiHPO l5G8kgRi38PS7/6s3R8QDsEtbGsYy6O82k3zSLIjuDBwA9GRaeigGppTxzAHVjf5o9KKu4O7 gC2KKVHPegbXS+GK7DU0fjzX57H5bZ6komE5eY4p3oWT/CwVPSGfPs8jOwARAQABwsB2BBgB CAAgFiEEmuvCXT0aY6hs4SbWeVOEFl5WrMgFAl+pQfkCGwwACgkQeVOEFl5WrMiVqwf9GwU8 c6cylknZX8QwlsVudTC8xr/L17JA84wf03k3d4wxP7bqy5AYy7jboZMbgWXngAE/HPQU95NM aukysSnknzoIpC96XZJ0okLBXVS6Y0ylZQ+HrbIhMpuQPoDweoF5F9wKrsHRoDaUK1VR706X rwm4HUzh7Jk+auuMYfuCh0FVlFBEuiJWMLhg/5WCmcRfiuB6F59ZcUQrwLEZeNhF2XJV4KwB Tlg7HCWO/sy1foE5noaMyACjAtAQE9p5kGYaj+DuRhPdWUTsHNuqrhikzIZd2rrcMid+ktb0 NvtvswzMO059z1YGMtGSqQ4srCArju+XHIdTFdiIYbd7+jeehg== In-Reply-To: X-Scanned-By: MIMEDefang 2.86 X-Spamd-Result: default: False [-2.39 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; R_SPF_ALLOW(-0.20)[+ip6:2607:f3e0::/32]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[199.212.134.19:received]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEFALL_USER(0.00)[mike]; RCPT_COUNT_TWO(0.00)[2]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[sentex.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4XPVMp2gJLz4Skf X-Spamd-Bar: -- This is a multi-part message in MIME format. --------------QZauI1oxGGVzC6dR3gFFe4MQ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/10/2024 8:46 AM, Michael Sierchio wrote: > > On Thu, Oct 10, 2024 at 7:58 AM Ronald F. Guilmette > wrote: > > I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that > is unambiguously at > death's door: > > Any suggestions?  If worse comes to worse I guess I will end up > writing my own tiny > little C program to just write 4KB blocks to a designated output > file while ignoring > all output errors, but I don't want to reinvent the wheel if > somebody else already > created something I can use in this context. > > > There is no method of writing to a disk that can reliably delete or > obscure all data – modern disk drives silently remap sectors, making > them unavailable to the host for writes.  If the data on the drive is > particularly sensitive, physical destruction of the media is the best > approach.  The DOD method is crush, then burn. ;-) We do both for disks.  We do a dd if=/dev/urandom first. Regardless if that fails/passes, we then physically destroy the disk.  The idea being if for some reason step 2 is missed, low effort prying eyes will not find anything.    Depends on your situation and sensitivity of the data.     ---Mike --------------QZauI1oxGGVzC6dR3gFFe4MQ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 10/10/2024 8:46 AM, Michael Sierchio wrote:

On Thu, Oct 10, 2024 at 7:58 AM Ronald F. Guilmette <rfg@tristatelogic.com> wrote:
I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that is unambiguously at
death's door:
 
Any suggestions?  If worse comes to worse I guess I will end up writing my own tiny
little C program to just write 4KB blocks to a designated output file while ignoring
all output errors, but I don't want to reinvent the wheel if somebody else already
created something I can use in this context.

There is no method of writing to a disk that can reliably delete or obscure all data – modern disk drives silently remap sectors, making them unavailable to the host for writes.  If the data on the drive is particularly sensitive, physical destruction of the media is the best approach.  The DOD method is crush, then burn. ;-)

We do both for disks.  We do a dd if=/dev/urandom first. Regardless if that fails/passes, we then physically destroy the disk.  The idea being if for some reason step 2 is missed, low effort prying eyes will not find anything.    Depends on your situation and sensitivity of the data.

    ---Mike


--------------QZauI1oxGGVzC6dR3gFFe4MQ-- From nobody Thu Oct 10 13:16:08 2024 X-Original-To: questions@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 4XPVdW5cRCz5Z22r for ; Thu, 10 Oct 2024 13:16:31 +0000 (UTC) (envelope-from robert@rrbrussell.com) Received: from fhigh-a5-smtp.messagingengine.com (fhigh-a5-smtp.messagingengine.com [103.168.172.156]) (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 4XPVdV601lz4VKm for ; Thu, 10 Oct 2024 13:16:30 +0000 (UTC) (envelope-from robert@rrbrussell.com) Authentication-Results: mx1.freebsd.org; none Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id CC3A811401A4; Thu, 10 Oct 2024 09:16:29 -0400 (EDT) Received: from phl-imap-10 ([10.202.2.85]) by phl-compute-06.internal (MEProxy); Thu, 10 Oct 2024 09:16:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rrbrussell.com; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm2; t=1728566189; x=1728652589; bh=baDF8JP1/9oqq31r8+EW7p/VCd62c7yR H0QNvg6DYC0=; b=D/uLv+E/MPMidU7U6dyo6PQ0CHczkoWzMb8mIClirwZ/9RER vZMQ+JCJIDrGLJgzU9/nII8brHp69dvtS0jP70ujpJjT4J0EEnSiVbLsbpqMnRU5 x4ImpVgHh3+QXKBg7MB3Yrw2WCXon8bGjSQArbCwo0lkjIzmE4IKhVfe6489hW5b 6mlWPEQhvzFRU/7syVUOn1EdY5Ac1hwB6eSpLTp/xKA5V0xG90YrG+FHZVZpjdzj KxpISY2TrApqctB/NZZ6y1wSJFNQNiB2xIAhlJm1wZvTnz/xIdrlVNkdW5HOHZll Mg7wp5yRDAdYOJ4/SFuyVH1JBeuYYvehSPOilw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1728566189; x= 1728652589; bh=baDF8JP1/9oqq31r8+EW7p/VCd62c7yRH0QNvg6DYC0=; b=E 1YyetftgOPfqlpHyCjW15gObbaxJoolrQoUtJXhT3RpR+t2yuAxrI7pwgL/r9JoB Gx2hKQMgCAJfSiL0q/j8szDbG+/PqlnJaaN3cGgx44tMmdI7U1goIeju7tlXnCAO btqh4AgPg574lgnjIzp6/oPbiTX74q9XCJ7p96fL9VC4XEUaZefghb0y5SwRelzn ecZMatHqdkB23/OxvM5Wyh6oXAaZH3FhORrf3hDoesS1rSixGl3M8DwKyUh6oCbf nER13VWt7mTDn1Ucg36EhuOwuj4idC0KJBQH6mAZ/b88QKEyviWs9dGyp1f8VBAP gpgqTsNVBINeER7Gg2DLQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdefhedgieehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefoggffhf fvvefkjghfufgtgfesthhqredtredtjeenucfhrhhomheprhhosggvrhhtsehrrhgsrhhu shhsvghllhdrtghomhenucggtffrrghtthgvrhhnpeeileevgfelkeeukeeifedviedvud eljeevgeejtdefvdefkeeghedtgeduieffgfenucevlhhushhtvghrufhiiigvpedtnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehrohgsvghrthesrhhrsghruhhsshgvlhhlrdgtoh hmpdhnsggprhgtphhtthhopeefpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehq uhgvshhtihhonhhssehfrhgvvggsshgurdhorhhgpdhrtghpthhtohepkhhuugiiuhesth gvnhgvsghrrghsrdgtohhmpdhrtghpthhtoheprhhfghesthhrihhsthgrthgvlhhoghhi tgdrtghomh X-ME-Proxy: Feedback-ID: ie421460a:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 4D3E63C0066; Thu, 10 Oct 2024 09:16:29 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Date: Thu, 10 Oct 2024 08:16:08 -0500 From: robert@rrbrussell.com To: "Michael Sierchio" , "Ronald F. Guilmette" Cc: questions@freebsd.org Message-Id: In-Reply-To: References: <5117.1728561469@segfault.tristatelogic.com> Subject: Re: How to zero a failing disk drive before disposal? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US] X-Rspamd-Queue-Id: 4XPVdV601lz4VKm X-Spamd-Bar: ---- On Thu, Oct 10, 2024, at 07:46, Michael Sierchio wrote: > On Thu, Oct 10, 2024 at 7:58=E2=80=AFAM Ronald F. Guilmette=20 > wrote: >> I have a pretty ancient 4TB spinning rust drive (WD4001FAEX) that is = unambiguously at >> death's door: >=20 >> Any suggestions? If worse comes to worse I guess I will end up writi= ng my own tiny >> little C program to just write 4KB blocks to a designated output file= while ignoring >> all output errors, but I don't want to reinvent the wheel if somebody= else already >> created something I can use in this context. > > There is no method of writing to a disk that can reliably delete or=20 > obscure all data =E2=80=93 modern disk drives silently remap sectors, = making=20 > them unavailable to the host for writes. If the data on the drive is=20 > particularly sensitive, physical destruction of the media is the best=20 > approach. The DOD method is crush, then burn. ;-) > > -M True M but you=E2=80=99re completely ignoring applicable threats. Unless= you=E2=80=99re likely a target of supply chain tampering, just use the = ATA Secure Erase feature built into the drives firmware and send the fai= ling drive out for proper recycling. Physical destruction of the drives is the only option if supply chain ta= mpering is a concern otherwise encrypt the disk, use the ATA Secure Eras= e, and reuse or recycle depending on estimated drive life left. The hdparm manual page discusses how to invoke the ATA Secure Erase feat= ure. It may require hot plugging the data cable for the drive. From nobody Thu Oct 10 15:17:24 2024 X-Original-To: questions@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 4XPYK740Bjz5Z9T3 for ; Thu, 10 Oct 2024 15:17:31 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPYK51tgXz4lHP for ; Thu, 10 Oct 2024 15:17:29 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=HB6Db37R; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4XPYK35K7vzDqWY for ; Thu, 10 Oct 2024 15:17:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728573447; bh=OrcIJ2YpBolfdhM/iVS87ttQi8DdHNB+hyef7CewU0E=; h=Subject:From:To:Date:In-Reply-To:References:From; b=HB6Db37RHQpl1KUERqTk1+fZbtNfN0XxikkfHywh4MJgWsoPTp7x8jfy4ZNC59eWx hvf+rATQZJfFGzyhGKPRyPwDf2gZk7ZqQ826CqxZ6drDL+TqWO8HgNbNPvcfqC6EUp rLXRP2wbfdh08jSnVmBWlXeKzsuInTJowa2gyuT0= X-Riseup-User-ID: 7FC7E864A94903F412E70C87B494717946C4B694DAEA5B36852E77C8E039421E Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XPYK30cP9zJmpK for ; Thu, 10 Oct 2024 15:17:26 +0000 (UTC) Message-ID: <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Thu, 10 Oct 2024 17:17:24 +0200 In-Reply-To: References: <5117.1728561469@segfault.tristatelogic.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.20 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx1.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[198.252.153.129:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[riseup.net:+]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPYK51tgXz4lHP X-Spamd-Bar: ---- On Thu, 2024-10-10 at 15:36 +0300, Odhiambo Washington wrote: > remove the [...] the magnets (for use elsewhere) Hi, in terms of sustainability and children's education, this is my favourite piece of advice. https://www.youtube.com/watch?v=3Drn6rgxsm5oA https://www.youtube.com/watch?v=3DNXD9gDCw7uU On Thu, 2024-10-10 at 04:57 -0700, Ronald F. Guilmette wrote: > I'm paranoid. Someone might have the skills to extract data even after the plates have been shredded and fused into a lump. Maybe it is best to sherd the plates, mix the fragments and shoot one half into the sun with a rocket and the other half onto Venus. On Thu, 2024-10-10 at 08:16 -0500, robert@rrbrussell.com wrote: > invoke the ATA Secure Erase feature ATA Secure Erase or ATA Cryptographic Key Reset are as secure as a pager or walkie-talkie, as it is impossible to know whose fingers were involved in their manufacture or in the supply chain. How paranoid were you when the drive was still in use? Was the computer hidden deep in a secret vault in a bunker in a mountain? If you are not too paranoid, consider to dismantle the drive and dispose a part of it in an environmentally friendly way, while placing the damaged plates in public waste bins in various places. Regards, Ralf From nobody Thu Oct 10 15:59:13 2024 X-Original-To: freebsd-questions@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 4XPZFS6VWsz5ZD8y for ; Thu, 10 Oct 2024 15:59:24 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from mailout.qeng-ho.org (mailout.qeng-ho.org [217.155.128.244]) (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 4XPZFR5szrz4txP for ; Thu, 10 Oct 2024 15:59:23 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd@qeng-ho.org designates 217.155.128.244 as permitted sender) smtp.mailfrom=freebsd@qeng-ho.org; dmarc=none Received: from [IPV6:2a02:8010:64c9:1::2] (unknown [IPv6:2a02:8010:64c9:1::2]) by mailout.qeng-ho.org (Postfix) with ESMTP id 20B323E2F5 for ; Thu, 10 Oct 2024 16:59:15 +0100 (BST) Message-ID: <08566be4-c21f-4074-bae0-3a5f87256c95@qeng-ho.org> Date: Thu, 10 Oct 2024 14:59:13 -0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: FreeBSD-Questions From: Arthur Chance Subject: Firefox 131 failing all https connections Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.29 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; R_SPF_ALLOW(-0.20)[+ip4:217.155.128.240/29]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:13037, ipnet:217.155.0.0/16, country:GB]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[qeng-ho.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4XPZFR5szrz4txP X-Spamd-Bar: --- I've just upgraded to Firefox 131 (131.0_1,2 to be precise) and I can only access http pages and any attempt to fetch an https page fails with an empty page. The web developer tools simply show the unhelpful NS_ERROR_FAILURE for the fetch. With the previous version (FF 129) everything worked correctly. I have the ca_root_nss pkg installed, but asking FF 131 about root certificates shows many expired ones so I suspect it's somehow failing to pick up the certificates from the pkg. Any suggestions where I go from here? Current OS: > uname -a FreeBSD arthur.home.qeng-ho.org 13.3-RELEASE-p7 FreeBSD 13.3-RELEASE-p7 GENERIC amd64 Firefox build options from poudriere: ===> The following configuration options are available for firefox-131.0_1,2: CANBERRA=off: Sound theme alerts DBUS=on: D-Bus IPC system support DEBUG=off: Build with debugging support FFMPEG=on: FFmpeg support (WMA, AIFF, AC3, APE...) LIBPROXY=off: Proxy support via libproxy LTO=off: Use Link-Time Optimization OPTIMIZED_CFLAGS=on: Use extra compiler optimizations PROFILE=off: Build with profiling support TEST=off: Build and/or run tests ====> Extra cubeb audio backends (OSS is always available) ALSA=off: ALSA audio architecture support JACK=off: JACK audio server support PULSEAUDIO=off: PulseAudio sound server support SNDIO=off: Sndio audio support -- Although not designed for computation, PIO is quite likely Turing complete, provided a long enough piece of tape can be found. It is conjectured that it could run DOOM, given a sufficiently high clock speed. — The Raspberry Pi Pico datasheet on its PIO capability. From nobody Thu Oct 10 16:13:47 2024 X-Original-To: questions@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 4XPZZG3RZnz5ZDyc for ; Thu, 10 Oct 2024 16:13:58 +0000 (UTC) (envelope-from matthew@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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPZZG2smjz4yhQ for ; Thu, 10 Oct 2024 16:13:58 +0000 (UTC) (envelope-from matthew@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728576838; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=nQ7ORWw1RKIOkD8C79gyXa+XWty43dsol/GK8vjlMkE=; b=WEWnfNPlXiRePeEWTR1thYV9lwY5WGp19AZ5fuO2atGLCyhBQX5VRubDe9/u+J0wzgsp9s DMAvLGqKChZoad1/t+bxS6VJz4Ovk4XlSwe9kEwsKEXlkeYnA8eD8w+6gPKhcDo0DZLIf2 hgWnVrXzZhFodO9XblkYsxss2tBkbkEKJrYEuRbKfoAxBZeTTEdF2GBuZbkqtZBVPLDvN3 pY2/0mQ88d/zHtfghShmipIcXFYdZcz9kgAPeP3Ssp835N/+YwzqwnvAcx2u/fo3vv6ta9 kmMQIyEs2QyzhvKS6JuHw4jo0/NkPxA15vbKJPb+1zO9oioEjr/eUKa5IvOwDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1728576838; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=nQ7ORWw1RKIOkD8C79gyXa+XWty43dsol/GK8vjlMkE=; b=A1pazGuwSFuQruSv95+LvknRxSq+OaKCqkgen9379MTCnGxH4M1rJ6MpeSnP8L5F1HoEkE HyTVT/MFtEgn1HToRDwLHw++Ri995phqtwNPReXs8JgnVK5YaZH4oSlP1yQsmlIKrMOCOe dNXTJil/OmymqlHTWtbdirmallrxsONvCPTSEBKV+tJpXWbBfTMmISdppoADNtXpcaHHcJ B0G9d1PAxhyIA9mIxIrDMA/wq5i22Wr72eHcXhJgVr5ay3w8oYd9qnBbW3NAKq8vArgtQL MlMt2FN+0pN0Ryss7omAmMVNliKubzDBnHwtmFq0HaqAtfkNLLplq64yL301gg== ARC-Authentication-Results: i=1; smtp.infracaninophile.co.uk; dmarc=fail (p=none dis=none) header.from=FreeBSD.org ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1728576838; a=rsa-sha256; cv=none; b=I3Xl/JyJ4Q8c2dVt5OPXzGZgsMk+BRvH5ddVAhl84Qmad++EJvTIA733lQrY3U9mj/EKNd aNugmhiWDF3FrXoe66gRvi5cySbFvnF9jpxuLKpwtzfa3kXbGVAgDkn+Haevk6tKqam7Kl rjNe5SbGaca0NUwChxht2+X0u9COfwkFdq7JGPhVTBw2wNkpdSCB6ErkKxdxdVoqm7OSYl EauoLBzR573LyXZuKpml3ke/PxDWqV7o91vnSKOeboLmF+odYD/mFEJRtAbUJI41++peao lmdj/wZ1Q30Eby/uyIPbBJXmO/mYn+d+XyXdM4+ZsPHdCjJPo69XSgzxfUutiA== Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (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) (Authenticated sender: matthew/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XPZZG1kQ4z1gKM for ; Thu, 10 Oct 2024 16:13:58 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from [IPV6:2001:8b0:151:1:4b8:3b9c:26cf:eb2f] (unknown [IPv6:2001:8b0:151:1:4b8:3b9c:26cf:eb2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 97CF512080 for ; Thu, 10 Oct 2024 17:13:55 +0100 (BST) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=fail (p=none dis=none) header.from=FreeBSD.org Message-ID: <9ef03152-dce3-463e-b18f-842d6eae318b@FreeBSD.org> Date: Thu, 10 Oct 2024 17:13:47 +0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How to zero a failing disk drive before disposal? To: questions@freebsd.org References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> Content-Language: en-GB From: Matthew Seaman Autocrypt: addr=m.seaman@infracaninophile.co.uk; keydata= xsFNBFJIL80BEADi7/VbnnErDU6pjEhI/SzEZ/HbDRkJ5g7HroAtqIRm6nj8ZwOAgZ/2ZnWn 5F+fXTuLsG0FLNtkd17FoVcuCi5e/GPliXI5cmamV7E1Yz4T8UsJ7RQolimyxVexccKd16Tc AA7B9bFlJSKkBUSD0buj7VjT07xWhRzu6Vgi5r0UjLALYJz977uZA0F1aOGOXREDEAOhdcNc kSNjynqAwDA6dCT1Elpi4key1fYjv4jyDF+GU/YXul2Y/rguA8FCkHd9vyym5eAsLQ5mG00V V9fkEHIpH5KorNVnl/ufHXnkZqmHAZVpFDcrshb7aZ/pL45PXyWgLj+e6etelgj3a2bZi0JF cVdXCnBZVP2oIyYblM11ugTbfCwodORU8a5KfPeztMdAtDr4e+32NTrPdPi5rLT+GUsYz+PL 3A3m3u8bdsFp40DlIrBtSByVjqERxcfhphrEB4J8BXHUG7OAtXkZMlW/PGKDwXJq0O6Z5Tcg YHAoEiSWbXiexHgXNJyP+sqnIlhLWhSJGeJ+C83wqI6oYlZUCW00NkPxcIHnQPV/z+5wQVci TMyaWC2YCIHz4Ljs+TnwWMz0E8PNFDfHVbQ0W4PRGV7gRAqxfL+yKufauIEGbEq8rNDbSwL3 bcUCxR4ZDlaUEUwT4J8naf7rjdgiEYHs2Ig3jeK1+ER4FPG1sQARAQABzTBNYXR0aGV3IFNl YW1hbiA8bS5zZWFtYW5AaW5mcmFjYW5pbm9waGlsZS5jby51az7CwZcEEwEKAEECGwMFCwkI BwMFFQoJCAsFFgIDAQACHgECF4ACGQEWIQRyz6whebywJLW1RZADb2ye5/OevwUCZidQTgUJ FcBUAQAKCRADb2ye5/Oev8KYD/9za25U6k0Qc6iyAX639+HO+v2AOR7yN74XldbjT6ZsD2f4 Gt8v3rb19TLv/uwywUmLquPNfopQxCJs8AyQVD2P1+MXaG7UNbzed7vj249GWuWq95e9QVp1 EWRH6X34RnU6rVA2g4CWcdECdXLkaJaf69TzDPlZNLtX+9rHErBQDKpQdQeMLaImbW/uAWiT +eLwrPwCKzblV61X7elB8h8/kMxsK24xuFb2GM3HGCkuYOc2gjXpN9YNCXdlwX8czebn660h ue9QB1kjL3leRUFeXA600sQBXNSGQksJCRlnXoKZDkiGOcnnb+cK3xJH/C4puG1pNWlB3b2m YgWrP67FCTXv0F1v3sPDwdIaXHWY0zz7/rpXMb+OqljQW9fMn6YfQeowlvbfCZKSCA4idjgy YETFVI8cJMnXQxNZdUnVlrYjTA2H9hhjG1Dnwt3Ept0c3xlrdTngqDvwTHBJTmUWz/wgMbjj 84zWZCVAbI9SkZVqqfjFNhgIe7aD1DstvvQ9My0Ie7XuobYFwx1s4w6Pxe7dunOWbGI7nvqk e9Snarlin58d+D38Pg6y90WLviimMmF2iayjsNCNqi7a26lqnirChecUFxLSvNcKdR92x2y6 u6pBWWoglfJ/Cp/H0uvz4X6PE909Npk7mshLLvzEDvMMvcHA/4x/kNrMwdeZB87BTQRSUUK4 ARAA1FhWoOejtwmsnGshoIbda2FmM+z/f97OzpagLhACHfP5Es/I18wG/0G+rdNuO2tjA9IM Z44GUMtjokDrDk63N9S+rVKy1QEy+UN6CiIfYTpTTAPnEY7IGN1JjGksPhn7aeuBCQwUMAV1 k+wklBCcOD6s8DD4kx0ZJqkH83XzWoBSVamdHvnM56C8yPVr5HHMC1tZInAWBMrF+cjl1EPf z3CqkVnG8Sxc5ydeibMS9Q3lHLeVkVlMRAmNqzNLfgJDUWtzac7JIjFEsxYYhpiaPcsstUUu Ha4zIRJ/yHDNbDttWRf1lrlFZLpeuap4BZ2hQw0UOZVNwGoFoS4ZqaZiv8mm0lX6s9/AdQD6 AVrpXWKa7JU2wDiay9sRbYh+5vVWGz9mhncK/Vfwtu5IjVp5v5WMz/WfnUxZMcNlfgTo4i1s www+qRBO2A4Yj8qKKWnTsl7aCX92itTiPgwbt6YgQPwgww72r67jPt5o8VMXDqPMPKzGicw1 AyxtMjsoSlnn91FuZctwil3vPpvzGXtBmrzQSbdDmy0KT5p5/W9pD/8UtLLLM6PLs5X0jIho vQHnQKEUO7xV3yNDAW9DPICeh7f/o9W+QJfQAXngNz0brvmgScAUXRaeAFeQbAmtEG92qlSV D7gb7WOemllgfbEn0Nanrv5aEcZCWx4WjybMLHEAEQEAAcLBfAQYAQoAJgIbDBYhBHLPrCF5 vLAktbVFkANvbJ7n856/BQJmJ1DIBQkVt0GQAAoJEANvbJ7n856/SOkP/iocAFde4BUQ8D8W QuG+dXum75rwlV1NutwIdzZyzLDF6l5ItV9t1VtWVOpd7lgWqHtUBGqjm6mw6qR9YoXNMeyc nokBq2YSunLuV2K/UEijNES6deNYYu1HIb4GbfeEODiK2xQ40dDPwpucSQmZ0FeHfnkO7hgI RlywbIyG8p4HHuKR01/W07pOGGRA6F8GRoI+m38ARe+r/2W4HlrJnS/+POKm6lu67wdtcBNq eYF3rcgrvh08bqZtIaEtGoyZ54tRpoWq6aTXvI88T5oABwZKn95m5KAvUlQ15IOGF049uAN4 APOExOtqVNcvQPypeRCoOTShW20C1ZM3ZaRc39alDu3bj1S24K/Ldav8Qe+kzWs744Tu+Qyt bWtpr+gvkrpPVXdFiFiDuCF3WQZrTdTr3Nm5ES2ePV2YW02M837VnmW8hm9id3iiBawyhdUy NtSPXXGTZSMD/TZ8urv2R3xMkpoh2j5PIJ4cF2ZJEz/VOaWv6LN4/+MgC7icVyUldoOZeWFj LS2YBgy50ICICmCefF4ekMGcbPi9+OAd1lLYwkLd1AAhQu1JPU163KW8/Bkc/FqrzE0iJxX9 N3I3Zyt3uswd1+7LxiswWZdkvBJvTpHtp1CeiA794MDJEVQfI9o5icfRBNOoPJM8c56FTs19 JmiH35KSh45LpcSbDr3t In-Reply-To: <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 10/10/2024 16:17, Ralf Mardorf wrote: > Someone might have the skills to extract data even after the plates have > been shredded and fused into a lump. The Néel temperature for steel is typically somewhere around 200 -- 500 ºC depending on the alloy. Steel that is hot enough to "fuse into a lump" will need to be significantly hotter than that -- nearly at the melting point. All of the magnetic information will have been wiped. Other ferromagnets useable for magnetic recording are going to behave similarly. Cheers, Matthew From nobody Thu Oct 10 16:15:38 2024 X-Original-To: questions@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 4XPZcS5kbRz5ZDt5 for ; Thu, 10 Oct 2024 16:15:52 +0000 (UTC) (envelope-from tomek@cedro.info) Received: from mail-yw1-x112a.google.com (mail-yw1-x112a.google.com [IPv6:2607:f8b0:4864:20::112a]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPZcS0Ztbz50kN for ; Thu, 10 Oct 2024 16:15:52 +0000 (UTC) (envelope-from tomek@cedro.info) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x112a.google.com with SMTP id 00721157ae682-6e2d2447181so9779397b3.1 for ; Thu, 10 Oct 2024 09:15:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cedro.info; s=google; t=1728576951; x=1729181751; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=883etgn0G+3zfXeK2DY2yK3jaRz2WGVglOkPjqCCyOY=; b=Zx1fAdcvuAOBVZf4epNSSZtPaYIKyosRhBJE6D1NE9tncwY2I/4vxiVEhXb5Pj7HZy Bh28tk1lmWBif/TpQ4Pmc/TonqEaPq0caopAUrcGGNytJ6+U2XW16QqiRjlDbussAkHy 6Mk9QEWK3o7dnqQxFXLupewJmtS3U3ExyS7NaWBccAolWcG8AzqZ64JRAg9g3Pkw5jWE jNw42Kxex+1rfADXkKMqAGCN7nw2ha4qnspyNwAw7zxI4X0KvdE6iSiEiEtV4hcBEy2+ aR7JSbHILFyOBVQaYelzN7OgEQ7chRD+td4lE5Rpt1hahIhnMIl4s27OZ8MbN2w/XCvO Olcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728576951; x=1729181751; 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=883etgn0G+3zfXeK2DY2yK3jaRz2WGVglOkPjqCCyOY=; b=RPxqPrkEigiKLVCuAg12tb+zLzjwCWVleL8FcLeuy4dV7qX1/0hwffiUPzyap6NeTo sXb2E2RAZ12pVJXVryLIMHVMgnGi5y4g/fdRzhO53mvIQ3V+/EuHToImkzh03/X7Frmm 0xT6YsCJ1ziHJjwWODTy+oh6Vy12msoVVCnrw/ASrkwyL/kzI8xtYFRi5BLRC6TTw1xg PobRUHy0Kw2GP2rma3mGdG+7hGpbQHmjm+HXg02csC+1KUJDwHaDRrlSd2GFp7LrvI0g ZrQIW+6f+6qdeFwgcFWqAqKLWxFbWs/NMihSKBVmgRi/MdZx/XtLLI0sPTBmd/5hAqGL ki2g== X-Gm-Message-State: AOJu0Yyjs78eHKMGQXTEbLUUkOgybF+QrkdB4Hsage4PQ9+P1r4csVJ6 BOA7yd+ltcKMhLShk1BqoQX4CqBacjzabKuVOJcoPwHEIAox92kXeOuCvaBrvzKRRbbCyyd8R/o = X-Google-Smtp-Source: AGHT+IGFT5c/Yc4jkG78dwGrhmaMB92hj8AmlK8LlV+GCGRkymLiYyRMPBpaJziPIcs3FQSXOmEoyw== X-Received: by 2002:a05:690c:740a:b0:6e2:c13e:20e9 with SMTP id 00721157ae682-6e3224eb3e9mr65761837b3.38.1728576951178; Thu, 10 Oct 2024 09:15:51 -0700 (PDT) Received: from mail-yw1-f180.google.com (mail-yw1-f180.google.com. [209.85.128.180]) by smtp.gmail.com with ESMTPSA id 00721157ae682-6e332b92dadsm2603217b3.54.2024.10.10.09.15.50 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Oct 2024 09:15:50 -0700 (PDT) Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-6e2d2447181so9779167b3.1 for ; Thu, 10 Oct 2024 09:15:50 -0700 (PDT) X-Received: by 2002:a05:690c:ec5:b0:6de:a3:a7ca with SMTP id 00721157ae682-6e322487f54mr69117377b3.32.1728576950328; Thu, 10 Oct 2024 09:15:50 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: <5117.1728561469@segfault.tristatelogic.com> In-Reply-To: <5117.1728561469@segfault.tristatelogic.com> From: Tomek CEDRO Date: Thu, 10 Oct 2024 18:15:38 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: How to zero a failing disk drive before disposal? To: "Ronald F. Guilmette" Cc: questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XPZcS0Ztbz50kN X-Spamd-Bar: ---- sysutils/ddrescue helped me to read broken drives several times, it retries then skips on errors. sysutils/e2fsprogs has program badblocks that can help disk rebuild in read only mode, or make things worse depending how its broken, and you can use it many loops of destructive write test to overwrite data. the safest way to dispose sensitive data is by physical destruction :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From nobody Thu Oct 10 16:30:46 2024 X-Original-To: freebsd-questions@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 4XPZxj1ty7z5ZGK7 for ; Thu, 10 Oct 2024 16:30:49 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from mailout.qeng-ho.org (mailout.qeng-ho.org [217.155.128.244]) (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 4XPZxh2krfz54cR for ; Thu, 10 Oct 2024 16:30:48 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd@qeng-ho.org designates 217.155.128.244 as permitted sender) smtp.mailfrom=freebsd@qeng-ho.org; dmarc=none Received: from [IPV6:2a02:8010:64c9:1::2] (unknown [IPv6:2a02:8010:64c9:1::2]) by mailout.qeng-ho.org (Postfix) with ESMTP id 5AE593E2BC; Thu, 10 Oct 2024 17:30:46 +0100 (BST) Message-ID: <65eb8b64-3273-4215-a493-ff670cba6729@qeng-ho.org> Date: Thu, 10 Oct 2024 15:30:46 -0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Firefox 131 failing all https connections To: Paul Procacci , FreeBSD-Questions References: <08566be4-c21f-4074-bae0-3a5f87256c95@qeng-ho.org> Content-Language: en-GB From: Arthur Chance In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.29 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+ip4:217.155.128.240/29]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:13037, ipnet:217.155.0.0/16, country:GB]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; DMARC_NA(0.00)[qeng-ho.org]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4XPZxh2krfz54cR X-Spamd-Bar: --- On 10/10/2024 15:22, Paul Procacci wrote: > > > On Thu, Oct 10, 2024 at 11:59 AM Arthur Chance > wrote: > > I've just upgraded to Firefox 131 (131.0_1,2 to be precise) and I can > only access http pages and any attempt to fetch an https page fails with > an empty page. The web developer tools simply show the unhelpful > NS_ERROR_FAILURE for the fetch. > > With the previous version (FF 129) everything worked correctly. I have > the ca_root_nss pkg installed, but asking FF 131 about root certificates > shows many expired ones so I suspect it's somehow failing to pick up the > certificates from the pkg. > > Any suggestions where I go from here? > > > Current OS: > > > uname -a > FreeBSD arthur.home.qeng-ho.org > 13.3-RELEASE-p7 FreeBSD 13.3-RELEASE-p7 > GENERIC amd64 > > Firefox build options from poudriere: > > ===> The following configuration options are available for > firefox-131.0_1,2: >      CANBERRA=off: Sound theme alerts >      DBUS=on: D-Bus IPC system support >      DEBUG=off: Build with debugging support >      FFMPEG=on: FFmpeg support (WMA, AIFF, AC3, APE...) >      LIBPROXY=off: Proxy support via libproxy >      LTO=off: Use Link-Time Optimization >      OPTIMIZED_CFLAGS=on: Use extra compiler optimizations >      PROFILE=off: Build with profiling support >      TEST=off: Build and/or run tests > ====> Extra cubeb audio backends (OSS is always available) >      ALSA=off: ALSA audio architecture support >      JACK=off: JACK audio server support >      PULSEAUDIO=off: PulseAudio sound server support >      SNDIO=off: Sndio audio support > > > -- > Although not designed for computation, PIO is quite likely Turing > complete, provided a long enough piece of tape can be found. It is > conjectured that it could run DOOM, given a sufficiently high clock > speed.  — The Raspberry Pi Pico datasheet on its PIO capability. > > > Two things come to mind. > > 1) Is the date/time correct on your machine? chronyc tells me this machine is 19 microseconds slow from the correct time. Close enough. :-) > 2) Do you have the latest nss package installed? arthur@arthur[4]▶ pkg info -x ca_root ca_root_nss-3.104 > > When this happens to me, granted not very often, it's usually because my > date/time wasn't synced. -- Although not designed for computation, PIO is quite likely Turing complete, provided a long enough piece of tape can be found. It is conjectured that it could run DOOM, given a sufficiently high clock speed. — The Raspberry Pi Pico datasheet on its PIO capability. From nobody Thu Oct 10 16:39:57 2024 X-Original-To: questions@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 4XPb8M2XGMz5ZGbT for ; Thu, 10 Oct 2024 16:40:03 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPb8L24Cbz56bD for ; Thu, 10 Oct 2024 16:40:02 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=Gg5ZKL47; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XPb8K2Qm2z9vyD for ; Thu, 10 Oct 2024 16:40:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728578401; bh=u/UBWnycCPrF7v99mtR7F3mbGJwUWUdYxD5yHn/1HSk=; h=Subject:From:To:Date:In-Reply-To:References:From; b=Gg5ZKL4703F5457g//5bLI6bhqeHO27VEKi5Di7RtkCcc4f7FXaGHFuCt/hExPid9 vvKaxx1xcEqqdbcj5lqv6Od8LrEIYA5JqLoo25oiY/h/7t+ZtM1SMzHYI3DYrJ9r9v /IiU6rv6P5OzXQH9rm4GltpOVqG1URUCKQSe0vr0= X-Riseup-User-ID: 8634F999388006E5EF6E069830361195C087C8E94D3E5FDB1AECD61500326EB4 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XPb8J6Km0zJsxq for ; Thu, 10 Oct 2024 16:40:00 +0000 (UTC) Message-ID: <4d4886050a110040091998cc8b96323f1fa215db.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Thu, 10 Oct 2024 18:39:57 +0200 In-Reply-To: <9ef03152-dce3-463e-b18f-842d6eae318b@FreeBSD.org> References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> <9ef03152-dce3-463e-b18f-842d6eae318b@FreeBSD.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPb8L24Cbz56bD X-Spamd-Bar: ---- On Thu, 2024-10-10 at 17:13 +0100, Matthew Seaman wrote: > Steel that is hot enough to "fuse into a lump" will need to be > significantly hotter than that -- nearly at the melting point.=C2=A0 All = of > the magnetic information will have been wiped. >=20 > Other ferromagnets useable for magnetic recording are going to behave=20 > similarly. Hi, you only need a morphogenetic field resonator to read data from a demagnetised lump, see https://static.spektrum.de/fm/912/f2000x857/245808923_pa.jpg ;). Regards, Ralf From nobody Thu Oct 10 17:46:15 2024 X-Original-To: questions@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 4XPcd41cMVz5YMfw for ; Thu, 10 Oct 2024 17:46:32 +0000 (UTC) (envelope-from tomek@cedro.info) Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPcd24KrPz40M4 for ; Thu, 10 Oct 2024 17:46:30 +0000 (UTC) (envelope-from tomek@cedro.info) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-e28fc33fd8eso996206276.1 for ; Thu, 10 Oct 2024 10:46:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cedro.info; s=google; t=1728582388; x=1729187188; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=8GvJ7jCq/qkNjd879dvKzZa6tlMZOgb/4PNVRJK1XkY=; b=duL6x8Qplyln8zmlEZHyz+EDo+4YzVib9g9c0HMbFqzTHVj2ToUTkU2dWjFZPHeKV0 En0qEcwiXRnXKg0jvamP3zXahB4tOGXv+BfG9f6OzEEzOgLN9ZDb8sFDp5awiEjSFUJZ cNCkAten57T9ooGvi/fPRKlc5Ut3f1E8OVf/Nrx5AglUlgRP/2JjAHtp+nNcEq6424l+ VjRNPCsJ9eHa6iezpaiA2tLkwzVBvDZH7ig1Ktrad+wwAQikN8WC8/7ppQ2hudgYUPqG hVKeh4Oq015VSR2SYadMc4rYuHuxfDIvuy7ESiXY3r24XkBi6uIlKn8ljZNOXoql/Ja8 PS6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728582388; x=1729187188; h=content-transfer-encoding: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=8GvJ7jCq/qkNjd879dvKzZa6tlMZOgb/4PNVRJK1XkY=; b=Fppk/Uk5HICPTFOkLpprFtRNXR7eO+H0v4SEFhAakJ9IRzXQ1vTgK+9GCzJTODNJeV MojOJPJaQ7AwA14ApaXCLo0XzzAWy3OG0w0cIqJbWBTlul8Ii6acsf6kyFFWrDjfmQIA Zn73q9e5eGdGmUFHbkmwg7cqtLu+c0AJxfpOe44MekC/XGTVJxKJNf/KVhEKFPa7ikjK c5wN+arJLnQidCuAt0r5kInyjzeYxyhkB1V8dgOgnVeBy7aIP7N8MjxuUGc5CsCqcfj3 ajMC05XSzsh+XUroKkW1vY0KDVnTeHhITLg85MkUBr5NqH1ezAsc3ImRTop5c0IFolf5 6/HQ== X-Gm-Message-State: AOJu0YzpjvXJ9V5dom1NjgTLi/bcdt4gH8HM/KKJu/nNFKlHC8xez4Up bEe6e2H1O+Vk4rKiyK2FVMJ85K4OymX4nyB8puq3v5bvyh+8NHC9qXeNgeZeKvlG05LLlcMMbic = X-Google-Smtp-Source: AGHT+IG3kWHbEotDqDax6jHA5HJ2qhXI7mtJUhLbPB8Mo3XBHg4bsMkCCtNVNnpyivfTTR8iPMgJpQ== X-Received: by 2002:a05:6902:846:b0:e29:890:c6d4 with SMTP id 3f1490d57ef6-e2916a18094mr359990276.41.1728582388388; Thu, 10 Oct 2024 10:46:28 -0700 (PDT) Received: from mail-yw1-f170.google.com (mail-yw1-f170.google.com. [209.85.128.170]) by smtp.gmail.com with ESMTPSA id 3f1490d57ef6-e290ee00013sm403976276.19.2024.10.10.10.46.27 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Oct 2024 10:46:27 -0700 (PDT) Received: by mail-yw1-f170.google.com with SMTP id 00721157ae682-6dde476d3dfso11543917b3.3 for ; Thu, 10 Oct 2024 10:46:27 -0700 (PDT) X-Received: by 2002:a05:690c:f93:b0:64b:5cc7:bcbc with SMTP id 00721157ae682-6e343dad61emr1568107b3.32.1728582387207; Thu, 10 Oct 2024 10:46:27 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> <9ef03152-dce3-463e-b18f-842d6eae318b@FreeBSD.org> <4d4886050a110040091998cc8b96323f1fa215db.camel@riseup.net> In-Reply-To: <4d4886050a110040091998cc8b96323f1fa215db.camel@riseup.net> From: Tomek CEDRO Date: Thu, 10 Oct 2024 19:46:15 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: How to zero a failing disk drive before disposal? To: Ralf Mardorf Cc: questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XPcd24KrPz40M4 X-Spamd-Bar: ---- On Thu, Oct 10, 2024 at 6:40=E2=80=AFPM Ralf Mardorf wrote: > On Thu, 2024-10-10 at 17:13 +0100, Matthew Seaman wrote: > > Steel that is hot enough to "fuse into a lump" will need to be > > significantly hotter than that -- nearly at the melting point. All of > > the magnetic information will have been wiped. > > Other ferromagnets useable for magnetic recording are going to behave > > similarly. > > you only need a morphogenetic field resonator to read data from a > demagnetised lump, see > https://static.spektrum.de/fm/912/f2000x857/245808923_pa.jpg ;). I have something like this somewhere in my basement.. we only need to make it pocket size now and battery powered plus the USB interface so it works on FreeBSD :D :D :D --=20 CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From nobody Thu Oct 10 18:07:36 2024 X-Original-To: questions@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 4XPd5V6vpgz5YP8M for ; Thu, 10 Oct 2024 18:07:42 +0000 (UTC) (envelope-from ccraft@netgenius.org) Received: from delivery.antispam.mailspamprotection.com (delivery.antispam.mailspamprotection.com [185.56.86.132]) (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 4XPd5V02sdz43Z5 for ; Thu, 10 Oct 2024 18:07:42 +0000 (UTC) (envelope-from ccraft@netgenius.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netgenius.org header.s=default header.b=JUDpepab; spf=pass (mx1.freebsd.org: domain of ccraft@netgenius.org designates 185.56.86.132 as permitted sender) smtp.mailfrom=ccraft@netgenius.org; dmarc=pass (policy=none) header.from=netgenius.org; arc=pass ("instance-us-central1-43c0.prod.antispam.mailspamprotection.com:s=arckey:i=1") ARC-Seal: i=1; cv=none; a=rsa-sha256; d=instance-us-central1-43c0.prod.antispam.mailspamprotection.com; s=arckey; t=1728583661; b=it+um9XVpDLMQMxSoNYdEu1vMbLk6LrskhGuR6fDEsr1yOICiuZFD1+4dNqzSRdVENEh3hl9fn jluH9wW+D4aIiVJGHs7OSkYLDfl5a199BcB1X6ZCCD24DJKOjWEGM6umXi8iauAFrBw2pkOcKi IBNuP5WQZHYEY6X5ackRMtUFp5bLMQaUE9fjRG7TLzGFGLyUREHm4Lr0CiVocIMhC7Z2oamKyr 9kFu0X5qtNzGDAmyXC+IQZRvW+tppgsyrI1GLr2JdIZ/sQPb1HHqn+oY5wVKNMw+kxCAee+sqI bLnTz/5Qef1sV6CbA37ncphXCXkWauyK/mPv0dDE2DfcVw==; ARC-Authentication-Results: i=1; instance-us-central1-43c0.prod.antispam.mailspamprotection.com; smtp.remote-ip=35.208.189.200; iprev=pass (200.189.208.35.bc.googleusercontent.com) smtp.remote-ip=35.208.189.200; auth=pass (LOGIN) smtp.auth=giowm1069.siteground.biz; dkim=pass header.d=netgenius.org header.s=default header.a=rsa-sha256; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed; d=instance-us-central1-43c0.prod.antispam.mailspamprotection.com; s=arckey; t=1728583661; bh=R/+C4JF+uEeXk3S4B6TB+/9UYCTcol46SwtgZtiQ6wo=; h=In-Reply-To:From:To:References:Subject:MIME-Version:Date:Message-ID: Content-Type:DKIM-Signature; b=PHeev2icEEtE7jEDfq35aCJFdUBvD7es6mGUDJuvbxuJFmc8v80+6SHjs5VbtKn8d0yddG2AFV xfSj4dknvXAms7fuHuJDRQ/UmkLk0Hr/C/3mTAgvlm45N7KpNpQrdYuS+yCm1U+6nIGldSdXoq rZ7K++eR7TAgiExLBsqlh3JTg0L1CpAoqpFkLVOUvdCuEFvd1ucJDuZuOZr4QUiLT3BToStv3x Dm7AuAVMb3a0Xw+tSjFaXCq1oJr7BjR1qliZjeZOrew8ftxLTtOw9fQhnBcx/WNJF1H7gyFlxy /Y23t0s0L/jpa+PWzvRwKcfqx4sDiLXLbBEV0z2o1qiYcA==; Received: from 200.189.208.35.bc.googleusercontent.com ([35.208.189.200] helo=giowm1069.siteground.biz) by instance-us-central1-43c0.prod.antispam.mailspamprotection.com with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98) (envelope-from ) id 1syxZa-00000002CSS-2bRD for questions@freebsd.org; Thu, 10 Oct 2024 18:07:39 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=netgenius.org; s=default; h=From:To:Subject:Date:cc:list-help: list-unsubscribe:list-subscribe:list-post:list-owner:list-archive; bh=yTbGVdscbs8BBXCXqe79d75r+5FO5ZZhzbNANubiAVQ=; b=JUDpepabsRLhrMzjwMImZflBFE laXHjspeLzBnKOEFid4PVFnycweEnKdzWM15Y+SV4vWsbqfzO1AwmfUMBsBMKTgR/Vy/d/K4ZdPgq plLfdWh773+ydXghB1cgeEPyijhsjiWZw7WEGUGZklfFYkXeo5SnjtDrXhUJ725xzZWM=; Received: from [216.147.121.198] (port=59528 helo=[192.168.1.96]) by giowm1069.siteground.biz with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.98) (envelope-from ) id 1syxZY-000000008SO-2MRx for questions@freebsd.org; Thu, 10 Oct 2024 18:07:36 +0000 Content-Type: multipart/alternative; boundary="------------5VnU5omhsB4kEsvvGNm08QVO" Message-ID: <479ed045-10df-4ab7-86aa-76e37b7d1e4e@netgenius.org> Date: Thu, 10 Oct 2024 12:07:36 -0600 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Fwd: How to zero a failing disk drive before disposal? Content-Language: en-US References: To: questions@freebsd.org From: Chris Craft In-Reply-To: X-Forwarded-Message-Id: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - giowm1069.siteground.biz X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - netgenius.org X-Source: X-Source-Args: X-Source-Dir: X-SGantispam-id: b1d157fe34b8d8c34c1d897a4264328f AntiSpam-DLS: false AntiSpam-DLSP: AntiSpam-DLSRS: AntiSpam-TS: 1.0 X-Spamd-Result: default: False [-3.78 / 15.00]; ARC_ALLOW(-1.00)[instance-us-central1-43c0.prod.antispam.mailspamprotection.com:s=arckey:i=1]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.69)[-0.687]; DMARC_POLICY_ALLOW(-0.50)[netgenius.org,none]; R_DKIM_ALLOW(-0.20)[netgenius.org:s=default]; R_SPF_ALLOW(-0.20)[+ip4:185.56.86.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[185.56.86.132:from]; XM_UA_NO_VERSION(0.01)[]; HAS_X_SOURCE(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[netgenius.org:+]; ASN(0.00)[asn:396982, ipnet:185.56.86.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; HAS_X_ANTIABUSE(0.00)[]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[185.56.86.132:from] X-Rspamd-Queue-Id: 4XPd5V02sdz43Z5 X-Spamd-Bar: --- This is a multi-part message in MIME format. --------------5VnU5omhsB4kEsvvGNm08QVO Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit The message was intended to go back to the list... (Sorry, Matt!) -------- Forwarded Message -------- Subject: Re: How to zero a failing disk drive before disposal? Date: Thu, 10 Oct 2024 10:19:03 -0600 From: Chris Craft To: Matthew Seaman I was going to mention "Curie point", but this seems to be a complex topic. (Forum discussion: https://www.overclockers.com/forums/threads/what-is-the-curie-point-of-hdd-magnetic-platters.454159/ ) I think you'd be just fine putting it in the oven on the cleaning cycle (about 550F). -C On 10/10/24 10:13, Matthew Seaman wrote: > On 10/10/2024 16:17, Ralf Mardorf wrote: >> Someone might have the skills to extract data even after the plates have >> been shredded and fused into a lump. > > The Néel temperature for steel is typically somewhere around 200 -- > 500 ºC depending on the alloy.  Steel that is hot enough to "fuse into > a lump" will need to be significantly hotter than that -- nearly at > the melting point.  All of the magnetic information will have been wiped. > > Other ferromagnets useable for magnetic recording are going to behave > similarly. > >     Cheers, > >     Matthew > --------------5VnU5omhsB4kEsvvGNm08QVO Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

The message was intended to go back to the list... (Sorry, Matt!)



-------- Forwarded Message --------
Subject: Re: How to zero a failing disk drive before disposal?
Date: Thu, 10 Oct 2024 10:19:03 -0600
From: Chris Craft <ccraft@netgenius.org>
To: Matthew Seaman <matthew@FreeBSD.org>


I was going to mention "Curie point", but this seems to be a complex topic. (Forum discussion: https://www.overclockers.com/forums/threads/what-is-the-curie-point-of-hdd-magnetic-platters.454159/ )

I think you'd be just fine putting it in the oven on the cleaning cycle (about 550F).

-C

On 10/10/24 10:13, Matthew Seaman wrote:
On 10/10/2024 16:17, Ralf Mardorf wrote:
Someone might have the skills to extract data even after the plates have
been shredded and fused into a lump.

The Néel temperature for steel is typically somewhere around 200 -- 500 ºC depending on the alloy.  Steel that is hot enough to "fuse into a lump" will need to be significantly hotter than that -- nearly at the melting point.  All of the magnetic information will have been wiped.

Other ferromagnets useable for magnetic recording are going to behave similarly.

    Cheers,

    Matthew

--------------5VnU5omhsB4kEsvvGNm08QVO-- From nobody Thu Oct 10 18:34:45 2024 X-Original-To: questions@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 4XPdj90hGzz5YRXV for ; Thu, 10 Oct 2024 18:35:09 +0000 (UTC) (envelope-from robert@rrbrussell.com) Received: from fout-a4-smtp.messagingengine.com (fout-a4-smtp.messagingengine.com [103.168.172.147]) (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 4XPdj75t6Gz46sH for ; Thu, 10 Oct 2024 18:35:07 +0000 (UTC) (envelope-from robert@rrbrussell.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=rrbrussell.com header.s=fm2 header.b=heiPRRDw; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="k PPuvxN"; spf=pass (mx1.freebsd.org: domain of robert@rrbrussell.com designates 103.168.172.147 as permitted sender) smtp.mailfrom=robert@rrbrussell.com; dmarc=pass (policy=quarantine) header.from=rrbrussell.com Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfout.phl.internal (Postfix) with ESMTP id A54E113801FB for ; Thu, 10 Oct 2024 14:35:06 -0400 (EDT) Received: from phl-imap-10 ([10.202.2.85]) by phl-compute-06.internal (MEProxy); Thu, 10 Oct 2024 14:35:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rrbrussell.com; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1728585306; x=1728671706; bh=9gPmJL477aJA4iCFcdqm31T893kDRidv0n22BxF1hig=; b= heiPRRDw/Z7Aw1pSb/eHbYzXObrRBYwSFasHlojkLQIH00XLsSubMQ6oWlA+Wcun /lFncmhrFvhhSnjF2iI/BJWeE59uoVGTEYkw5h5ahWoM4xGx1NpfZ5Xx2C/Awx/0 2JTbP/3JuX1EauAzQkpQIh6yG/jemc9sIWZLMkwYn+SfNiHMTm24ddJh15h9Xpc+ ++3xY0lWPuZWNmqVjh+rPAgBQ94JTRB0ZWPrG+QUdyVt8Pdd73yIZ31W5hcEe1EJ 64QVa57kNL85id54754JX7UgN7VpDMmv/HSj8ocrDuu4/NFcTYM5IA/hYn7xODOF J7dtCgpFdaz5Ob/u3xNLhQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1728585306; x= 1728671706; bh=9gPmJL477aJA4iCFcdqm31T893kDRidv0n22BxF1hig=; b=k PPuvxN+fd1FvqRvz00XZRBWUcJvKipEAOWsSXVYuTCR02/gJWe5tYR5huLPIF5Qa IMHyaRRlH5QC6vXT+KhVOlchcgVWZo8fj/ViLwb0KIwr7ZMT5JnyqGmFa//V37iv ocKafCya5UJvioYx7Bxb4AjObTPpj9DoWijRbSZnk0LYFBsO+LC4jp1LA99dTOLF x73HcymNQoVHGqiclxdSrnqkz7NNCKb+K3ExdcldjT21t3Gf7FDGX61eLK0ITtgW wwRLaRBchJUBXtsRwG401V2POWr/D5fQno2JvArna5d+jd9/bGdr/UJFGYRBOJjU 7Xxk9ajdDZPx0tFiegFoA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdefiedgtdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefoggffhf fvkfgjfhfutgfgsehtqhertdertdejnecuhfhrohhmpehrohgsvghrthesrhhrsghruhhs shgvlhhlrdgtohhmnecuggftrfgrthhtvghrnhepudehleetkeeujeekjefflefgueektd fggeetuddttedtudejgfffffeileeggfegnecuvehluhhsthgvrhfuihiivgeptdenucfr rghrrghmpehmrghilhhfrhhomheprhhosggvrhhtsehrrhgsrhhushhsvghllhdrtghomh dpnhgspghrtghpthhtohepuddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepqhhu vghsthhiohhnshesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: ie421460a:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 652E23C0066; Thu, 10 Oct 2024 14:35:06 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Date: Thu, 10 Oct 2024 13:34:45 -0500 From: robert@rrbrussell.com To: questions@freebsd.org Message-Id: <7de83c36-7ec5-4cf3-8e8d-4cad98d610b8@app.fastmail.com> In-Reply-To: <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-2.09 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[rrbrussell.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; R_DKIM_ALLOW(-0.20)[rrbrussell.com:s=fm2,messagingengine.com:s=fm2]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.147:from]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; NEURAL_HAM_SHORT(-0.00)[-0.003]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; FROM_NO_DN(0.00)[]; FREEFALL_USER(0.00)[robert]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[rrbrussell.com:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4XPdj75t6Gz46sH X-Spamd-Bar: -- On Thu, Oct 10, 2024, at 10:17, Ralf Mardorf wrote: > > On Thu, 2024-10-10 at 08:16 -0500, robert@rrbrussell.com wrote: >> invoke the ATA Secure Erase feature > > ATA Secure Erase or ATA Cryptographic Key Reset are as secure as a pag= er > or walkie-talkie, as it is impossible to know whose fingers were > involved in their manufacture or in the supply chain. Quit spreading FUD. The cost of building a subverted drive isn=E2=80=99t= worth the time or money for general distribution in the economy. You ne= ed a high percentage of the drive=E2=80=99s physical capacity dedicated = to spare space to get a decent chance of catching useable data in =E2=80= =9Creallocated=E2=80=9D space. Of course your competition can just sell = a higher capacity drive and put you out of business. The easiest way to destroy information is forgetting the encryption key = but most people don=E2=80=99t use FDE. From nobody Thu Oct 10 18:44:30 2024 X-Original-To: freebsd-questions@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 4XPdw14lBTz5YRtl for ; Thu, 10 Oct 2024 18:44:33 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from mailout.qeng-ho.org (mailout.qeng-ho.org [217.155.128.244]) (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 4XPdvz6yZ2z485d for ; Thu, 10 Oct 2024 18:44:31 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd@qeng-ho.org designates 217.155.128.244 as permitted sender) smtp.mailfrom=freebsd@qeng-ho.org; dmarc=none Received: from [IPV6:2a02:8010:64c9:1::2] (unknown [IPv6:2a02:8010:64c9:1::2]) by mailout.qeng-ho.org (Postfix) with ESMTP id 94EED3E2F8 for ; Thu, 10 Oct 2024 19:44:30 +0100 (BST) Message-ID: <0b4c7966-23b8-4111-ba4f-b284517577bf@qeng-ho.org> Date: Thu, 10 Oct 2024 17:44:30 -0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Firefox 131 failing all https connections [SOLVED] From: Arthur Chance To: FreeBSD-Questions References: <08566be4-c21f-4074-bae0-3a5f87256c95@qeng-ho.org> Content-Language: en-GB In-Reply-To: <08566be4-c21f-4074-bae0-3a5f87256c95@qeng-ho.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.25 / 15.00]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.99)[-0.988]; NEURAL_HAM_SHORT(-0.97)[-0.975]; R_SPF_ALLOW(-0.20)[+ip4:217.155.128.240/29]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:13037, ipnet:217.155.0.0/16, country:GB]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_DKIM_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[qeng-ho.org]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4XPdvz6yZ2z485d X-Spamd-Bar: --- On 10/10/2024 14:59, Arthur Chance wrote: > I've just upgraded to Firefox 131 (131.0_1,2 to be precise) and I can > only access http pages and any attempt to fetch an https page fails with > an empty page. The web developer tools simply show the unhelpful > NS_ERROR_FAILURE for the fetch. > > With the previous version (FF 129) everything worked correctly. I have > the ca_root_nss pkg installed, but asking FF 131 about root certificates > shows many expired ones so I suspect it's somehow failing to pick up the > certificates from the pkg. > > Any suggestions where I go from here? OK, it seems that I'd updated Firefox and security/ca_root_nss but hadn't updated security/nss. Not sure how the latter got missed, but installing the 3.104 version to match the ca_root_nss version fixed the problem. Back to shaving the yak. -- Although not designed for computation, PIO is quite likely Turing complete, provided a long enough piece of tape can be found. It is conjectured that it could run DOOM, given a sufficiently high clock speed. — The Raspberry Pi Pico datasheet on its PIO capability. From nobody Thu Oct 10 19:22:16 2024 X-Original-To: questions@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 4XPflv2jDxz5YVQr for ; Thu, 10 Oct 2024 19:22:35 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from mail.sermon-archive.info (sermon-archive.info [47.181.130.121]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPfls3Dxtz4GBY for ; Thu, 10 Oct 2024 19:22:33 +0000 (UTC) (envelope-from bc979@lafn.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of bc979@lafn.org designates 47.181.130.121 as permitted sender) smtp.mailfrom=bc979@lafn.org; dmarc=none Received: from smtpclient.apple (unknown [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 4XPflk68Z5z2g4wd for ; Thu, 10 Oct 2024 12:22:26 -0700 (PDT) From: Doug Hardie Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\)) Subject: Re: How to zero a failing disk drive before disposal? Date: Thu, 10 Oct 2024 12:22:16 -0700 References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> <7de83c36-7ec5-4cf3-8e8d-4cad98d610b8@app.fastmail.com> To: questions@freebsd.org In-Reply-To: <7de83c36-7ec5-4cf3-8e8d-4cad98d610b8@app.fastmail.com> Message-Id: <2D3640CE-2A76-4BBD-8906-AF7FAE02AA32@sermon-archive.info> X-Mailer: Apple Mail (2.3776.700.51) X-Virus-Scanned: clamav-milter 1.3.1 at mail X-Virus-Status: Clean X-Spamd-Result: default: False [-1.71 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; NEURAL_HAM_SHORT(-0.62)[-0.618]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:5650, ipnet:47.181.128.0/18, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; APPLE_MAILER_COMMON(0.00)[]; DMARC_NA(0.00)[lafn.org: no valid DMARC record]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; R_DKIM_NA(0.00)[]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4XPfls3Dxtz4GBY X-Spamd-Bar: - > On Oct 10, 2024, at 11:34, robert@rrbrussell.com wrote: >=20 > On Thu, Oct 10, 2024, at 10:17, Ralf Mardorf wrote: >>=20 >> On Thu, 2024-10-10 at 08:16 -0500, robert@rrbrussell.com wrote: >>> invoke the ATA Secure Erase feature >>=20 >> ATA Secure Erase or ATA Cryptographic Key Reset are as secure as a = pager >> or walkie-talkie, as it is impossible to know whose fingers were >> involved in their manufacture or in the supply chain. >=20 > Quit spreading FUD. The cost of building a subverted drive isn=E2=80=99t= worth the time or money for general distribution in the economy. You = need a high percentage of the drive=E2=80=99s physical capacity = dedicated to spare space to get a decent chance of catching useable data = in =E2=80=9Creallocated=E2=80=9D space. Of course your competition can = just sell a higher capacity drive and put you out of business. >=20 > The easiest way to destroy information is forgetting the encryption = key but most people don=E2=80=99t use FDE. >=20 Encryption is not the answer. There is always a key that will decrypt = the data. The only issue is to find it. NSA, M4, KGB (or whatever they = are know as now), and possibly several other intel agencies have the = resources to decrypt it. Chances they would be interested in your data = is pretty slim, but I have seen several times where people were able to = guess the key in just a few tries.=20 I believe the easiest approach is to disassemble the unit, remove the = platter and sand it. The information is in the iron oxide (brown = stuff). Sanding it removes it as dust. This is essentially what a head = crash does. It doesn't take a lot of effort to sand it. The head = contacting the disk does a great job. =20 -- Doug From nobody Thu Oct 10 20:08:08 2024 X-Original-To: freebsd-questions@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 4XPgmh3rxMz5YYY5 for ; Thu, 10 Oct 2024 20:08:20 +0000 (UTC) (envelope-from freebsd@upokojski.de) Received: from server1.upokojski.de (server1.upokojski.de [IPv6:2a03:4000:35:1e7::]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPgmg3qqnz4QPk for ; Thu, 10 Oct 2024 20:08:19 +0000 (UTC) (envelope-from freebsd@upokojski.de) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd@upokojski.de designates 2a03:4000:35:1e7:: as permitted sender) smtp.mailfrom=freebsd@upokojski.de; dmarc=none Received: from [IPV6:2003:f1:871b:cc00:c5dd:d0b6:a781:3bfa] (p200300f1871bcc00c5ddd0b6a7813bfa.dip0.t-ipconnect.de [IPv6:2003:f1:871b:cc00:c5dd:d0b6:a781:3bfa]) by server1.upokojski.de (Postfix) with ESMTPSA id A37F45829B for ; Thu, 10 Oct 2024 22:08:07 +0200 (CEST) Message-ID: <2b663bca-5579-41c8-9db3-02bf87424d0f@upokojski.de> Date: Thu, 10 Oct 2024 22:08:08 +0200 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US From: Udo Pokojski Subject: Mysql-Server not starting To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.07 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.977]; R_SPF_ALLOW(-0.20)[+mx]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[upokojski.de]; RCVD_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:197540, ipnet:2a03:4000::/32, country:DE]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPgmg3qqnz4QPk X-Spamd-Bar: --- Hallo, after doing an pkg update and pkg upgrade on FreeBSD 13.3, I cannot start the mysql-server. The command service mysql-server start returns no error. In the mysql error log, I can find the following messages: 2024-10-10T19:55:15.913147Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-10-10T19:55:16.148244Z 1 [ERROR] [MY-012263] [InnoDB] The Auto-extending innodb_system data file '/var/db/mysql/ibdata1' is of a different size 768 pages (rounded down to MB) than specified in the .cnf file: initial 8192 pages, max 0 (relevant if non-zero) pages! 2024-10-10T19:55:16.148370Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error. 2024-10-10T19:55:16.149901Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-10-10T19:55:16.150187Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-10-10T19:55:16.150233Z 0 [ERROR] [MY-010119] [Server] Aborting Something seems to wrong with my my.cnf file. The only line which affects the innodb file size is: innodb_data_file_path           = ibdata1:128M:autoextend I never changed this line an In have no idea how to fix the error. Any help is appreciated. Thanks in advance, Udo From nobody Thu Oct 10 20:13:51 2024 X-Original-To: freebsd-questions@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 4XPgvF2HKkz5YZG9 for ; Thu, 10 Oct 2024 20:14:01 +0000 (UTC) (envelope-from cli_junkie@protonmail.com) Received: from mail-4316.protonmail.ch (mail-4316.protonmail.ch [185.70.43.16]) (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 "protonmail.com", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPgvC5ztpz4S1f for ; Thu, 10 Oct 2024 20:13:59 +0000 (UTC) (envelope-from cli_junkie@protonmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=protonmail.com header.s=protonmail3 header.b=ix9Ziuan; spf=pass (mx1.freebsd.org: domain of cli_junkie@protonmail.com designates 185.70.43.16 as permitted sender) smtp.mailfrom=cli_junkie@protonmail.com; dmarc=pass (policy=quarantine) header.from=protonmail.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1728591234; x=1728850434; bh=yyltwO1dXKpu4MS5iGZ8KTc3TgdRetv2I45cmt9CMBk=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=ix9ZiuanLemBhW9GcKIIfdVIxZR1FTmhkRuigYCmyA4/CLLgoSkVthlIpWFUhd97z YAoFSI1FANPjpQCqs7y3JHqpaRJwaGLnzujKYeU7xCQ+gNI8a/sAS3Q7UN25TjEZzi ObLelIMPOlmXk86F7Z/B85KF1F9al72nIm2DfwAIqt3x0JoDm856zhAIY1/zcf8iYP REV3HeRSyFK+M5ZFqspbqBn+SMHaJI9f7S8hTP5w1D5sUiceVm+Zvba0vywwU0fjPv Twc1MTXAE37XU01B1a+ex6h0Vc3xZaPkvlPLAG3dDq52LHugsMiCrVQ5Q0E3WEWx/N hLkBxrIb5M6xA== Date: Thu, 10 Oct 2024 20:13:51 +0000 To: freebsd-questions From: Pat Subject: Re: Updating disconnected systems Message-ID: In-Reply-To: References: Feedback-ID: 34340203:user:proton X-Pm-Message-ID: d63bff4195c34192bd659c8210ff745b36ed999b List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.20 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail3]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; RWL_MAILSPIKE_VERYGOOD(-0.20)[185.70.43.16:from]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; FREEMAIL_FROM(0.00)[protonmail.com]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; MISSING_XM_UA(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[protonmail.com:+] X-Rspamd-Queue-Id: 4XPgvC5ztpz4S1f X-Spamd-Bar: ---- On Monday, September 30th, 2024 at 06:50, Dave Cottlehuber wrote: >=20 >=20 > On Fri, 27 Sep 2024, at 19:18, Pat wrote: >=20 > > I figure can use Poudriere for packages, but that doesn't work for the > > core system as far as I can tell? >=20 >=20 > Yes this is also possible. >=20 > Klara Systems released a tool, sync-be, to use zfs boot environments and > poudriere-image which works very nicely in airgapped systems. >=20 > It is a lot less complicated to setup and use than it appears to be, > probably is exactly what you want. >=20 > - servers configured with zfs boot environments > - poudriere-image (builds freebsd from sources and then builds packages) > - the resulting output is a new zfs boot environment, as a single tarball > - use https://github.com/KlaraSystems/sync-be to fetch and deploy it > - insert airgaps at appropriate points in the process >=20 > So a high-level upgrade process looks like: >=20 > - [net] update src & ports, and ports distfile tarballs > - [air] move them to your build machine > - `poudriere image -t zfs+send+be -j builder ...` > - [air] move the image file to the airgapped system > - install `/usr/local/bin/sync-be 13.4-RELEASE /etc/syncbe.conf < be20240= 9301146.be.zfs` > - `bectl activate -t ...` and reboot >=20 > the boot env allows a trivial rollback in case of issues to the prior > boot env. >=20 > The syncbe.conf file takes a little bit of work to prepare, it's the > server-specific files and directories that should be shifted from > the current BE (root / dataset) into the new one. /etc/sshd/, /etc/hostid= , > password files etc are common examples, and any custom stuff in /usr/loca= l/etc/ > or similar depending on your circumstances. >=20 > A+ > Dave Thank you Dave, and previously to Dewayne as well. Very nice and useful information. I plan to start this migration soon and may be back with further questions as I progress. And apologies for the extended delay, I've been traveling. Regards, Pat From nobody Thu Oct 10 21:07:37 2024 X-Original-To: questions@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 4XPj5D4nlhz5YdYb for ; Thu, 10 Oct 2024 21:07:44 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPj5C39fCz4cLZ for ; Thu, 10 Oct 2024 21:07:43 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=S90PLmOe; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XPj5B1LPvz9vxV for ; Thu, 10 Oct 2024 21:07:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728594462; bh=BVp/lRLXeaeWYiGni8D/C7gXYWxSTdsYvnxhNKQxzFA=; h=Subject:From:To:Date:In-Reply-To:References:From; b=S90PLmOeR9Q3ZTJZS8pxQTqwn/0dZdUn6puF0wdyLuche4EYF/36RZVtfjyCP8uBi zhQPjGbrf6UFYRZl4YI3mjVgIQRuxTmuxWtpGXPjMLDbkvA69kAVWxmlsIJFf6D3hC 4dF23BjFHDG+CV7NeFwwfGz63zOc4fy6q6Ch5gzo= X-Riseup-User-ID: 6F295CAB045F5298A9DB0F8F71F9CCEB5FD8CC4F81668F549B09BBB067D4541C Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4XPj594KYjzFtWP for ; Thu, 10 Oct 2024 21:07:41 +0000 (UTC) Message-ID: Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Thu, 10 Oct 2024 23:07:37 +0200 In-Reply-To: <2D3640CE-2A76-4BBD-8906-AF7FAE02AA32@sermon-archive.info> References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> <7de83c36-7ec5-4cf3-8e8d-4cad98d610b8@app.fastmail.com> <2D3640CE-2A76-4BBD-8906-AF7FAE02AA32@sermon-archive.info> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPj5C39fCz4cLZ X-Spamd-Bar: ---- On Thu, 2024-10-10 at 12:22 -0700, Doug Hardie wrote: > I believe the easiest approach is to disassemble the unit, remove the > platter and sand it. Then "they" don't know what was on the hard drive, but "they" do know that something was on it. Who owns a sandblasting machine? However, I'm sure most of us agree that sheer force is more effective than nerdy software. You wouldn't make notes on paper illegible with an eraser, you would first tear up the paper, then burn the shreds and grind the ashes in a mortar and mix the ashes into the dog food. For HDDs the Italian mafia probably uses pizza ovens. So it looks like an accident to the public prosecutor's office if the hard drive got into the pizzeria's pizza oven. On Thu, 2024-10-10 at 13:34 -0500, robert@rrbrussell.com wrote: >The cost of building a subverted drive isn=E2=80=99t worth the time or mon= ey >for general distribution in the economy. The first step is owning a company, this is possible: https://en.wikipedia.org/wiki/Crypto_AG The second step, which concerns your counter-argument, is possible by switching from CMR to a well-developed SMR-like process. Who really knows what efficient writing methods are available today? Even if it's probably just a silly fantasy with HDDs, it's not far-fetched with SSDs. The advantage of SSDs could be that the data is probably lost relatively quickly if they have not been supplied with power for a long time. From nobody Thu Oct 10 21:19:28 2024 X-Original-To: questions@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 4XPjM52FXbz5YfNg for ; Thu, 10 Oct 2024 21:19:45 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPjM44X44z4dl1 for ; Thu, 10 Oct 2024 21:19:44 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=TZgexX5v; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XPjM32hcSz9v7B for ; Thu, 10 Oct 2024 21:19:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728595183; bh=lMa3VK2m2vjNW32u62HUjMt2rdjluvgqF1PfA656YSo=; h=Subject:From:To:Date:In-Reply-To:References:From; b=TZgexX5vdiUfAPjURrfd47dUTqAvvrtsiZ9WfILYe9KA5F0dANOtjjayKIVEav11y QrjJ7096MBaJxr6yRTvOKWA97haHLC2AatGRB3lBmmPHw86iDUT9AmSNJT4sm0F4tJ 867RD1l/NijjxrYoQvF/+joONc5eUXM0L/05tDxw= X-Riseup-User-ID: 72074FD5C8C9C87C0668D458B781CFE4EEA36025B2EFE156CE89BC5E0281A7D6 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4XPjLq5n1vzFtnS for ; Thu, 10 Oct 2024 21:19:31 +0000 (UTC) Message-ID: Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Thu, 10 Oct 2024 23:19:28 +0200 In-Reply-To: References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> <9ef03152-dce3-463e-b18f-842d6eae318b@FreeBSD.org> <4d4886050a110040091998cc8b96323f1fa215db.camel@riseup.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPjM44X44z4dl1 X-Spamd-Bar: ---- On Thu, 2024-10-10 at 19:46 +0200, Tomek CEDRO wrote: > > https://static.spektrum.de/fm/912/f2000x857/245808923_pa.jpg=C2=A0;). >=20 > I have something like this somewhere in my basement.. we only need to > make it pocket size now and battery powered In my garage is a fuel cell powered Ocean's Eleven electromagnetic pulse machine, https://www.youtube.com/watch?v=3DA1H4LqEnAnY . From nobody Thu Oct 10 21:33:08 2024 X-Original-To: questions@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 4XPjff47bzz5YgvD for ; Thu, 10 Oct 2024 21:33:14 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPjff0WhLz4gKm for ; Thu, 10 Oct 2024 21:33:14 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=cTsA4au8; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XPjfc5xdWz9sSK for ; Thu, 10 Oct 2024 21:33:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728595992; bh=NMTwS47TYDYXcHGHy81sGXUiiMSGY6CBDKZPs+ruvJE=; h=Subject:From:To:Date:In-Reply-To:References:From; b=cTsA4au8scpWL1jk2KFWuJjcBRLqqNX29MFpmF775eG7PTkE0gekf4CMtByCwPrEM 3Tagl1EO+q3G60yn4yiUiv7omoLJe8iq9D9tEbBQ3/PaExc9eS32HKl17QTWrrIH5a oV5Bo9924EkecpqIjavyuAcLv7AVXf51G0dScaNA= X-Riseup-User-ID: 05A3557D8E02A084D888CA41F0ADF3E0248EC4932F9EC707CFBEA83158BCBE28 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4XPjfc2sXKzFvk4 for ; Thu, 10 Oct 2024 21:33:12 +0000 (UTC) Message-ID: Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Thu, 10 Oct 2024 23:33:08 +0200 In-Reply-To: References: <5117.1728561469@segfault.tristatelogic.com> <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> <7de83c36-7ec5-4cf3-8e8d-4cad98d610b8@app.fastmail.com> <2D3640CE-2A76-4BBD-8906-AF7FAE02AA32@sermon-archive.info> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPjff0WhLz4gKm X-Spamd-Bar: ---- On Thu, 2024-10-10 at 23:07 +0200, Ralf Mardorf wrote: > The advantage of SSDs could be that the data is probably lost > relatively quickly if they have not been supplied with power for a > long time. Hearsay, therefore "quickly" vs "long time" :D AFAIK SSDs really do function in such a way that the actual storage space is significantly larger than the space available to the user. It would cost a secret service nothing, just a backdoor to access the whole space. From nobody Fri Oct 11 00:38:47 2024 X-Original-To: questions@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 4XPnmq3T1Fz5YvNK for ; Fri, 11 Oct 2024 00:38:51 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPnmp0wn6z41Mq for ; Fri, 11 Oct 2024 00:38:50 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id B06464E690; Thu, 10 Oct 2024 17:38:47 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? In-Reply-To: List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9480.1728607127.1@segfault.tristatelogic.com> Content-Transfer-Encoding: quoted-printable Date: Thu, 10 Oct 2024 17:38:47 -0700 Message-ID: <9481.1728607127@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.10 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XPnmp0wn6z41Mq X-Spamd-Bar: -- In message , = Odhiambo Washington wrote: >I open the case, remove the platters and the magnets (for use elsewhere), >and repurpose the casing! Thank you. Yes, as a last step I shall be opening the case & pouring some small amount of sand inside (and then shaking vigorously). But if a nation state was determined to get my old credit card number, eve= n that might not stop them! :-) From nobody Fri Oct 11 00:52:11 2024 X-Original-To: questions@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 4XPp4F02sPz5YwP8 for ; Fri, 11 Oct 2024 00:52:13 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPp4D1WC0z43MT for ; Fri, 11 Oct 2024 00:52:12 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id 840374E690; Thu, 10 Oct 2024 17:52:11 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? In-Reply-To: <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9624.1728607931.1@segfault.tristatelogic.com> Date: Thu, 10 Oct 2024 17:52:11 -0700 Message-ID: <9625.1728607931@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.09 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.992]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XPp4D1WC0z43MT X-Spamd-Bar: -- In message <4592b3d058a5c2c2c5acf752706ade1e4e1ed7ca.camel@riseup.net>, Ralf Mardorf wrote: >On Thu, 2024-10-10 at 15:36 +0300, Odhiambo Washington wrote: >in terms of sustainability and children's education, this is my >favourite piece of advice. > >https://www.youtube.com/watch?v=3Drn6rgxsm5oA >https://www.youtube.com/watch?v=3DNXD9gDCw7uU I wish that I understood German. >Someone might have the skills to extract data even after the plates have >been shredded and fused into a lump. > >Maybe it is best to sherd the plates, mix the fragments and shoot one >half into the sun with a rocket and the other half onto Venus. Thank you. I will be contacting Elon Musk to see if I can arrange interplanetary passage for my platters. >How paranoid were you when the drive was still in use? Was the computer >hidden deep in a secret vault in a bunker in a mountain? Yes! How did you know? Has someone leaked photographs of my secret mountain lair?? >If you are not too paranoid, consider to dismantle the drive and dispose >a part of it in an environmentally friendly way, while placing the >damaged plates in public waste bins in various places. Thank you. That shall be done also. From nobody Fri Oct 11 01:00:07 2024 X-Original-To: questions@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 4XPpFP1H89z5YwmZ for ; Fri, 11 Oct 2024 01:00:09 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPpFN3gYMz44Br for ; Fri, 11 Oct 2024 01:00:08 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id D9CDC4E690; Thu, 10 Oct 2024 18:00:07 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? In-Reply-To: <4d4886050a110040091998cc8b96323f1fa215db.camel@riseup.net> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9728.1728608407.1@segfault.tristatelogic.com> Date: Thu, 10 Oct 2024 18:00:07 -0700 Message-ID: <9729.1728608407@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.10 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; R_SPF_ALLOW(-0.20)[+mx:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_NO_TLS_LAST(0.10)[]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XPpFN3gYMz44Br X-Spamd-Bar: -- In message <4d4886050a110040091998cc8b96323f1fa215db.camel@riseup.net>, Ralf Mardorf wrote: >you only need a morphogenetic field resonator to read data from a >demagnetised lump, see >https://static.spektrum.de/fm/912/f2000x857/245808923_pa.jpg ;). You guys are kraken me up! From nobody Fri Oct 11 02:42:21 2024 X-Original-To: questions@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 4XPrY06HpJz5Z50p for ; Fri, 11 Oct 2024 02:43:48 +0000 (UTC) (envelope-from dewayne@heuristicsystems.com.au) Received: from heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (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 (2560 bits) client-digest SHA256) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPrXx71Sbz4Gkp for ; Fri, 11 Oct 2024 02:43:45 +0000 (UTC) (envelope-from dewayne@heuristicsystems.com.au) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=heuristicsystems.com.au header.s=hsa header.b=ItQZ8dK1; spf=pass (mx1.freebsd.org: domain of dewayne@heuristicsystems.com.au designates 203.41.22.115 as permitted sender) smtp.mailfrom=dewayne@heuristicsystems.com.au; dmarc=none Received: from [10.0.5.4] (bigears.hs [10.0.5.4]) (authenticated bits=0) by heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPA id 49B2gKgH014637 for ; Fri, 11 Oct 2024 13:42:21 +1100 (AEDT) (envelope-from dewayne@heuristicsystems.com.au) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=heuristicsystems.com.au; s=hsa; t=1728614541; x=1729219342; bh=wyg9plwvc96o4GUybpIZ3mA2lXiV2zreOz2uyadYVns=; h=Message-ID:Date:Subject:To:From; b=ItQZ8dK1oR74kaggO3K/SMGGIJUuW+gaLpfyCKR6u4yDXs4/brNQl1GD8fjnobY8n zkHiiWkKV+5u4vvK4uER/JHKBX7R7x+3NVLSSivNSMGS8vl667unR61K3vyqQe8Qo4 Bh1SjVW+ZsPJ408XVVL9HxbNUrInAO28J8FBk8IAVqxwfYSgqCtGS X-Authentication-Warning: b3.hs: Host bigears.hs [10.0.5.4] claimed to be [10.0.5.4] Message-ID: <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> Date: Fri, 11 Oct 2024 13:42:21 +1100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How to zero a failing disk drive before disposal? To: questions@freebsd.org References: <5117.1728561469@segfault.tristatelogic.com> Content-Language: en-GB From: Dewayne Geraghty In-Reply-To: <5117.1728561469@segfault.tristatelogic.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-5.09 / 15.00]; DWL_DNSWL_MED(-2.00)[heuristicsystems.com.au:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_DKIM_ALLOW(-0.20)[heuristicsystems.com.au:s=hsa]; RCVD_IN_DNSWL_MED(-0.20)[203.41.22.115:from]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; XM_UA_NO_VERSION(0.01)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[heuristicsystems.com.au]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[heuristicsystems.com.au:+]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:1221, ipnet:203.40.0.0/13, country:AU]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_XAW(0.00)[] X-Rspamd-Queue-Id: 4XPrXx71Sbz4Gkp X-Spamd-Bar: ----- A good question Ronald. I worked for a provider of services for the statutory care of children (eg removed from parents). There are significant penalties for certain types of information loss. We bench-drilled the hard-disks before sending them (out of our chain of custody) to a furnace. Admittedly this is an extreme case and for the reasons already stated in this thread, there was no other way to ensure, say a name and location, were not available. And yes, all machines have full disk encryption (FDE). For personal devices we overwrite the device multiple times, though I'm interested in what a "ATA Secure Erase" does to a healthy storage device and whether all sectors are touched? From nobody Fri Oct 11 04:06:31 2024 X-Original-To: freebsd-questions@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 4XPtNm2c1Vz5Z9Ml for ; Fri, 11 Oct 2024 04:06:48 +0000 (UTC) (envelope-from jmpalacios@gmail.com) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPtNl1MdQz4Pbh for ; Fri, 11 Oct 2024 04:06:47 +0000 (UTC) (envelope-from jmpalacios@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-x829.google.com with SMTP id d75a77b69052e-460391553ecso14709911cf.1 for ; Thu, 10 Oct 2024 21:06:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728619605; x=1729224405; darn=freebsd.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=KRmIuT2VVhz68BL91/HPUVC03ZEAbiiuz14aS24LkhY=; b=S1JWaR/c4I8vkE4K449ekXo7SZ++Hh6ivk49b1Lg086SikT26ukq32Gke/B44TuVAS RV3PcEU7RpAojHbNznnZs7hR5EYCj0uAnlYooHL2yBmFXkI2HgCs4q6yJAlI9IlMoUfl KfTX4Dv6sw3I7tORJ6RLsevk8Rn5dYj3FDUCFDh8Kdyny9zPO3eRGLciRUO+PbTgCFbt TQ81819XC23yF8aW+98n8yx6CRstqw5C/DRiDolz7IvTdwG9NMXQFUQVMHpEOLW1Oofn CfPKkjyEE2fUnGCaEJ5x/KeWGrM0VUWO9cMouvltzlqemuR5W2I2QN613nKEJnNrVOMD rw7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728619605; x=1729224405; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=KRmIuT2VVhz68BL91/HPUVC03ZEAbiiuz14aS24LkhY=; b=V/V+86dq7+qjfXxMUDXsnp7xCniQsOnJMk3ZNXwN9/4yIeKnXZyFqe4cCUuB1AV6qy 7JblK2erXSIiL1owf6bFvBP+Jz7a6pJ3KsrEOd831xdhkTp+bph1/bQnwCabSzh8j0O/ yuYgn313UOJ7X/cFmOqy+DIOn5G1L+Y60+8GXU001QjCgShM9mzz+mBi/2Ex1LmaDmgI +vme4H+bZWEEpZZ38XVfRtKIizW+ZaotqCMF+9hVPx+Uj32RT+6XAN/qpY7GXUTlIPrY cL1V2wgveBzZYKHKgkzinvknPhSsntINU0iqsp4DzkcuTq2a4pqdgFDtHw5apgdxteuv il4w== X-Gm-Message-State: AOJu0YwvkzDclT6UY73hBXvMBZ0ItIVJKv3drHLxVG7FuCPu7xc3PlF+ yxhlV7HebGOsLLvK64em+nEP2tJiIZFaXUyk3GuhDljir1nnjvxusoa0RQ== X-Google-Smtp-Source: AGHT+IEBYgy72keYtGuNmTMq2WDoo8CmrhbZ2a9idJyK0SehUaZx65dvbYgwE3brxGXshytciSElCw== X-Received: by 2002:a05:622a:110f:b0:45b:5e8d:981e with SMTP id d75a77b69052e-4604bc49c8bmr23461021cf.54.1728619605035; Thu, 10 Oct 2024 21:06:45 -0700 (PDT) Received: from smtpclient.apple ([2600:4041:7970:8b10:99e6:1e16:6ac0:6b7e]) by smtp.gmail.com with ESMTPSA id d75a77b69052e-46042802624sm11774971cf.53.2024.10.10.21.06.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 Oct 2024 21:06:43 -0700 (PDT) From: Juan Manuel Palacios Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_12ACA1C8-469D-4E69-B98F-E03D366F738E" List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) Subject: Re: Mysql-Server not starting Date: Fri, 11 Oct 2024 00:06:31 -0400 In-Reply-To: <2b663bca-5579-41c8-9db3-02bf87424d0f@upokojski.de> Cc: freebsd-questions@freebsd.org To: Udo Pokojski References: <2b663bca-5579-41c8-9db3-02bf87424d0f@upokojski.de> X-Mailer: Apple Mail (2.3776.700.51.11.1) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XPtNl1MdQz4Pbh X-Spamd-Bar: ---- --Apple-Mail=_12ACA1C8-469D-4E69-B98F-E03D366F738E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Udo, What I=E2=80=99d do in this case would be to, first and foremost, back = up your data directory (zfs snapshot of the host would suffice, if = you=E2=80=99re on that filesystem, with the service stopped of course = =E2=80=94but is a given in this case=E2=80=94), and then start the = service with InnoDB in recovery mode: https://dev.mysql.com/doc/refman/8.4/en/forcing-innodb-recovery.html=EF=BF= =BC I've seen similar errors to yours, but involving the InnoDB log files, = e.g. ib_logfile0, which could be safely moved to the side to have the = MySQL recreate it/them upon restart. But in your case it appears that = it=E2=80=99s the ibdata files what are corrupt, which are the = "system=E2=80=99s tablespace=E2=80=9D files, = https://dba.stackexchange.com/a/27106, so I=E2=80=99d definitely be more = careful with those. HTH! > On Oct 10, 2024, at 4:08=E2=80=AFPM, Udo Pokojski = wrote: >=20 > Hallo, >=20 >=20 > after doing an pkg update and pkg upgrade on FreeBSD 13.3, I cannot = start the mysql-server. >=20 > The command service mysql-server start returns no error. >=20 >=20 > In the mysql error log, I can find the following messages: >=20 > 2024-10-10T19:55:15.913147Z 1 [System] [MY-013576] [InnoDB] InnoDB = initialization has started. > 2024-10-10T19:55:16.148244Z 1 [ERROR] [MY-012263] [InnoDB] The = Auto-extending innodb_system data file '/var/db/mysql/ibdata1' is of a = different size 768 pages (rounded down to MB) than specified in the .cnf = file: initial 8192 pages, max 0 (relevant if non-zero) pages! > 2024-10-10T19:55:16.148370Z 1 [ERROR] [MY-012930] [InnoDB] Plugin = initialization aborted with error Generic error. > 2024-10-10T19:55:16.149901Z 1 [ERROR] [MY-010334] [Server] Failed to = initialize DD Storage Engine > 2024-10-10T19:55:16.150187Z 0 [ERROR] [MY-010020] [Server] Data = Dictionary initialization failed. > 2024-10-10T19:55:16.150233Z 0 [ERROR] [MY-010119] [Server] Aborting >=20 >=20 > Something seems to wrong with my my.cnf file. The only line which = affects the innodb file size is: >=20 > innodb_data_file_path =3D ibdata1:128M:autoextend >=20 > I never changed this line an In have no idea how to fix the error. >=20 > Any help is appreciated. >=20 >=20 > Thanks in advance, >=20 > Udo >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 --Apple-Mail=_12ACA1C8-469D-4E69-B98F-E03D366F738E Content-Type: multipart/related; type="text/html"; boundary="Apple-Mail=_7CECCF8A-07AD-4F4B-AF09-BF06CCE0E7D3" --Apple-Mail=_7CECCF8A-07AD-4F4B-AF09-BF06CCE0E7D3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = Udo,

What I=E2=80=99d do in this case would be to, = first and foremost, back up your data directory (zfs snapshot of the = host would suffice, if you=E2=80=99re on that filesystem, with the = service stopped of course =E2=80=94but is a given in this case=E2=80=94), = and then start the service with InnoDB in recovery = mode:

3D"favicon.ico"

I've seen similar errors to = yours, but involving the InnoDB log files, e.g. ib_logfile0, which could = be safely moved to the side to have the MySQL recreate it/them upon = restart. But in your case it appears that it=E2=80=99s the ibdata files = what are corrupt, which are the "system=E2=80=99s tablespace=E2=80=9D = files, https://dba.stackexchange.com/a/27106, so I=E2=80=99d definitely = be more careful with = those.

HTH!

On Oct 10, 2024, at 4:08=E2=80=AFPM, Udo Pokojski = <freebsd@upokojski.de> wrote:

Hallo,


after = doing an pkg update and pkg upgrade on FreeBSD 13.3, I cannot start the = mysql-server.

The command service mysql-server start returns no = error.


In the mysql error log, I can find the following = messages:

2024-10-10T19:55:15.913147Z 1 [System] [MY-013576] = [InnoDB] InnoDB initialization has = started.
2024-10-10T19:55:16.148244Z 1 [ERROR] [MY-012263] [InnoDB] = The Auto-extending innodb_system data file '/var/db/mysql/ibdata1' is of = a different size 768 pages (rounded down to MB) than specified in the = .cnf file: initial 8192 pages, max 0 (relevant if non-zero) = pages!
2024-10-10T19:55:16.148370Z 1 [ERROR] [MY-012930] [InnoDB] = Plugin initialization aborted with error Generic = error.
2024-10-10T19:55:16.149901Z 1 [ERROR] [MY-010334] [Server] = Failed to initialize DD Storage Engine
2024-10-10T19:55:16.150187Z 0 = [ERROR] [MY-010020] [Server] Data Dictionary initialization = failed.
2024-10-10T19:55:16.150233Z 0 [ERROR] [MY-010119] [Server] = Aborting


Something seems to wrong with my my.cnf file. The = only line which affects the innodb file size = is:

innodb_data_file_path       =     =3D ibdata1:128M:autoextend

I never changed = this line an In have no idea how to fix the error.

Any help is = appreciated.


Thanks in = advance,

Udo










= --Apple-Mail=_7CECCF8A-07AD-4F4B-AF09-BF06CCE0E7D3 Content-Transfer-Encoding: base64 Content-Disposition: inline; filename=favicon.ico Content-Type: image/vnd.microsoft.icon; x-unix-mode=0666; name="favicon.ico" Content-Id: AAABAAEAEBAAAAEACABoBQAAFgAAACgAAAAQAAAAIAAAAAEACAAAAAAAAAEAABILAAASCwAAAAEA AAABAAB0RQAAeEkAAHlLAAB6TAAAek0AAHtNAAB7TgAAfE4AAHxPAAB9UAAAflEAAH5SAAB/UgAA f1MAAIBUAACAVQAAgVUAAIJXAACEUwAAhFQAAIRVAACDWAAAg1kAAIRZAACEWgAAhVoAAIVbAACF WwEAhVwBAIddBACHXQUAhl0GAIddBgCHXgkAilsAAIheBwCIXwkAiWALAIpiDQCNZhIAjmcSAI5n EwCNZRQAjmYUAI9oFwCPaBgAj2kaAJZrHACTbScAlXEmAJdzKgCXcywAl3QsAJpyKQCYdCoAmHUu AKF7NwCgfzYAoH48AJp8QQCjhEcApIRAAKaHSgCoiUcAqIpPAKyPTwClilIAqYxRAKqNUwCpklUA qZBaAK+TXwCymF8ArpFgALCUaACxnGwAtpxsALifcgC7o3cAuqJ5AL+pgwDCrYoAxLCMAMWxjgDF sY8Ax7SSAMi1kwDLuZsAzLmcAMy6oADOvKEAz76jANC/pgDRwagA1cevANXHsADYyrQA2s28AN3Q vgDd0b4A3NDAAN7SxADf1McA4dbHAOTa0QDl3NAA5t3TAOri2QDr5N0A7+rnAPDr6QDx7OkA8e3q APLt6gD///8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAcygbGxsVET4lATQ7HRsocygXFxsbDVBvTT1RIhcbGygbGxsbEjpTR2hdHRcXGxsXGxcbGwNT N0FyLg0bGxsbGxsXGxcNWiUmQg0bGxsXGxsbGxsbEVolFBEVGxcbGw00GxsbFwNZNhcbGRsbGxcV axsXGxQlZjEXGxsbGxcDVmAbFxcNXD4NFxkbGRkDOG8lGxsNRlUBFxsZGRkJL29AAxsXEWIsETAb GRkCMm9KAxcXDVhMATxPDQMNS21DAxsbDVNOAAMRBx1JaV8sBxcbGzVhFz9kZ2VsXjkNEhsbGxsr WGliRCsvIwMNFxcbFxcoRR0VBwMXFxcbGxsbGxsoSIABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA= --Apple-Mail=_7CECCF8A-07AD-4F4B-AF09-BF06CCE0E7D3-- --Apple-Mail=_12ACA1C8-469D-4E69-B98F-E03D366F738E-- From nobody Fri Oct 11 06:09:41 2024 X-Original-To: freebsd-questions@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 4XPx6w46qlz5YKT6 for ; Fri, 11 Oct 2024 06:10:00 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPx6v3b5Vz4Z3G for ; Fri, 11 Oct 2024 06:09:59 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="a/77ibZE"; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::112f as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-6dbb24ee34dso14889467b3.2 for ; Thu, 10 Oct 2024 23:09:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728626998; x=1729231798; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OAxRHrKDtOmQFYrMBTY8+JANs/SW6Vq4IejrAUE15O4=; b=a/77ibZEyYJFnz32EIkN1EBiGZreBMRLAkk1PnRMrxcW/HsjdxeGsiau2++dtK/qxD n0EPDpywtvTleZ/fKU+qEA8qinwxVVdeX5lgCmKFnUERSiXaR/QvCOLk6gM9BAAL6Wbj LdDs4m16hTJCY0zeXvgQI7QnauIoajrCY+x9wxvTGtbFBKWkTqORiB2CEb/BFKSlPWbH EMooXcUHy/U7qF9kKGkkeGHqWqka65UhRd9T28qnYf7KLbVYtV3fxto/MZ89hI8ebFDH EisaO59AQxcBA2JMj8wItK+52X8DbLzwU9t9T2M4nII8ajuGUix+bYI4F5mUbp7Of3xT YRQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728626998; x=1729231798; 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=OAxRHrKDtOmQFYrMBTY8+JANs/SW6Vq4IejrAUE15O4=; b=g24NKWUTjO3ASoSXA8lQSOTcMIXEOK9CSfMwLrfsIoYTwSmcJv2FpKPKOjwuXTg1LQ qwhesihkewIBOcswb8pzZci/qfb1ghPDvsz+56YGF/YDpa5/9/YloWFCrQlLRWuaeS1r GcvbGd1ES1cIA2+XJVbXOXZRwUrM/3PvO/lNEA5NbhK8A4TqQGppvpR0pKIPadlzfYvf 8gmt6PS/L2eY47mAyWVGT4Lx8krHL5jLRaV9ntaTWOGdPACND1DY1mBCdflmNS4+cH+Q FODY4eViOvdkbnRmOYawxa8yPOe2XALbf6XAMZl29/012+FPHtoz1805oX/DW6n9sJqn 56nQ== X-Gm-Message-State: AOJu0Yzv6SCebFiXM1NobKhmRxdBBQt0klMf+2iAiaPG4dM4/xLLYJpU JhHJPwN0dwTs3Ncw2rKaPUqO0OZZfekl1jNK1fUEvPZXW5cQf+HoLQ6inoVJ1Z0UzULHMGnKmrE Gd1RtJdjlmgwwxEhPuyVjTJ/Q65uC0A== X-Google-Smtp-Source: AGHT+IEGxvk9Fr+qSfP3jMSUZ3JSJfx7rVFtNYUv58j3dSOc3MOBT0FZ5ZBp23flbB0yFGdCYykmDB2ymE8odJ+x0oQ= X-Received: by 2002:a05:690c:4286:b0:6db:4536:85b9 with SMTP id 00721157ae682-6e3479c297cmr9948987b3.23.1728626998224; Thu, 10 Oct 2024 23:09:58 -0700 (PDT) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: <20241009063710.09572e05@dismail.de> In-Reply-To: <20241009063710.09572e05@dismail.de> From: Kevin Oberman Date: Thu, 10 Oct 2024 23:09:41 -0700 Message-ID: Subject: Re: FreeBSD releases To: LuMiWa Cc: FreeBSD Questions Content-Type: multipart/alternative; boundary="0000000000002db47006242d56c7" X-Spamd-Result: default: False [-3.70 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_ALL(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112f:from] X-Rspamd-Queue-Id: 4XPx6v3b5Vz4Z3G X-Spamd-Bar: --- --0000000000002db47006242d56c7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 9, 2024 at 3:37=E2=80=AFAM LuMiWa wrote: > Hi! > > As a binary packages user I have one question, please. > For example: > releng/14.1 14.1-RELEASE June 4, 2024 > expected eol March 31, 2025 > > This mean that are all packages built on version 14.0 for six months. > This mean if we want applications built for 14.1 we need to use ports, > special for apps like drm-kmod and more and build by ourselves. Am I > wright? > > Thank you. > > -- > =E2=80=9CI hate books; they only teach us to talk about things we know no= thing > about.=E2=80=9D > > =E2=80=95 Jean-Jacques Rousseau > > Yes. As long as 14.0 was supported, ports are built on 14.0. Now that 14.= 0 is EOL, as of October 1, ports are built on 14.1. There SHOULD be no problem in running 14.0 packages on 14.1 as the user space ABI is guaranteed to not change. The notable exception is ports that provide kernel modules. While most work as FreeBSD tries to keep the ABI consistent, it is not guaranteed. Notably, the drm-*kmod packages need to be built from the port with the kernel sources matching the kernel sources on the build machine. This has also happened with the virtualbox kmod and probably others. For multiple systems running hte same kernel, the port may be built once, a package built and copied to other systems. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --0000000000002db47006242d56c7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Oct 9, 2024 at 3:37=E2= =80=AFAM LuMiWa <lumiwa@dismail.de<= /a>> wrote:
Hi!

As a binary packages user I have one question, please.
For example:
releng/14.1=C2=A0 14.1-RELEASE June 4, 2024
expected eol March 31, 2025

This mean that are all packages built on version 14.0 for six months.
This mean if we want applications built for 14.1 we need to use ports,
special for apps like drm-kmod and more and build by ourselves. Am I
wright?

Thank you.

--
=E2=80=9CI hate books; they only teach us to talk about things we know noth= ing
about.=E2=80=9D

=E2=80=95 Jean-Jacques Rousseau

Yes. As long as 14.0 was supported, ports are = built on 14.0. Now that 14.0 is EOL, as of October 1, ports are built on 14= .1. There SHOULD be no problem in running 14.0 packages on 14.1 as the user= space ABI is guaranteed to not change. The notable exception is ports that= provide kernel modules. While most work as FreeBSD tries to keep the ABI c= onsistent, it is not guaranteed. Notably, the drm-*kmod packages need to be= built from the port with the kernel sources matching the kernel sources on= the build machine. This has also happened with the virtualbox kmod and pro= bably others.

For multiple systems runni= ng hte same kernel, the port may be built once, a package built and copied = to other systems.


--
--0000000000002db47006242d56c7-- From nobody Fri Oct 11 07:12:01 2024 X-Original-To: questions@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 4XPyVb28yPz5YPNr for ; Fri, 11 Oct 2024 07:12:07 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPyVZ12XPz4h2h for ; Fri, 11 Oct 2024 07:12:06 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=UoIyoQR5; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XPyVX5FBqz9sjZ for ; Fri, 11 Oct 2024 07:12:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728630724; bh=WeX6vV8fgsjyUwSLan11BDLFE8lW7z12LQS4TtJHKbE=; h=Subject:From:To:Date:In-Reply-To:References:From; b=UoIyoQR5PEQmEhhrr515iMOmICWf0TizS5q/xPHUwvVlydvOSJWURQVssmZjFnudE 1vLuStJVMk1lEKRnALr32LGAVKj05t/yO87DayqIGwAIY2dpELxCAsRDlkxyd3Nvpx GkhJ52Jm6LXBRkaymLDp2q0KJVslXt6rV3yPxZWg= X-Riseup-User-ID: 8921A002837CE6D2FAA219944494EF75AA3D3B17F69805C2740CEEC0CCFCFD38 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4XPyVX10M3zFtZt for ; Fri, 11 Oct 2024 07:12:03 +0000 (UTC) Message-ID: <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Oct 2024 09:12:01 +0200 In-Reply-To: <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> References: <5117.1728561469@segfault.tristatelogic.com> <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPyVZ12XPz4h2h X-Spamd-Bar: ---- On Fri, 2024-10-11 at 13:42 +1100, Dewayne Geraghty wrote: > I worked for a provider of services for the statutory care of children > (eg removed from parents). [...] We bench-drilled the hard-disks > before sending them (out of our chain of custody) to a furnace. +1 > For personal devices we overwrite the device multiple times After countless discussions about [1] and having recovered and not recovered lost data myself, I am firmly convinced that it is sufficient for a private household to overwrite just 1 time. After that Joe and Jane Lunchbucket can't recover the data anymore and it's also quasi impossible for a geek to recover something. The problem with the Lunchbucket family's HDDs is that they only replace them when they are defective anyway. At best, you can free up stuck heads and be happy if you can get your 4 TB drive overwritten at all. In these cases, the question of how often you should overwrite does not even arise. It is not for nothing that it is said that you should mount a drive "read only" as soon as possible after data has been lost in order to have any chance of recovering anything at all. Criminals and secret services will think twice about whether it is worth subjecting the Lunchbucket family's hard drive to time-consuming and costly forensic treatment. [1] =E2=80=A2 rocketmouse@archlinux ~=20 $ man shred | grep -eiterations -eCAUTION -A1 -n, --iterations=3DN overwrite N times instead of the default (3) -- CAUTION: shred assumes the file system and hardware overwrite data i= n place. Although this is common, many platforms operate otherwise. Also,= backups and mirrors may contain unre=E2=80=90 movable copies that will let a shredded file be recovered later. Se= e the GNU coreutils manual for details. From nobody Fri Oct 11 07:33:32 2024 X-Original-To: questions@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 4XPyzP1XWVz5YR1V for ; Fri, 11 Oct 2024 07:33:37 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPyzM1NjJz4l4L for ; Fri, 11 Oct 2024 07:33:35 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id 1E6E54E690; Fri, 11 Oct 2024 00:33:33 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? In-Reply-To: <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14090.1728632012.1@segfault.tristatelogic.com> Date: Fri, 11 Oct 2024 00:33:32 -0700 Message-ID: <14091.1728632012@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.09 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XPyzM1NjJz4l4L X-Spamd-Bar: -- In message <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au>, Dewayne Geraghty wrote: >A good question Ronald. I worked for a provider of services for the >statutory care of children (eg removed from parents). There are >significant penalties for certain types of information loss. We >bench-drilled the hard-disks before sending them (out of our chain of >custody) to a furnace. Admittedly this is an extreme case and for the >reasons already stated in this thread, there was no other way to ensure, >say a name and location, were not available. Interesting. I decided to go ahead and use S.M.A.R.T. secure erase on this drive after all, and then take the cover off and then... (Fortunately I have the necessary Torx[tm] screwdrivers to get the cover off.) I hadn't thought of drilling some holes in the platters after that, but that is part of my plan now. NICE IDEA! THANKS! I'm pretty sure that will render the platters entirely un-spinable. From nobody Fri Oct 11 07:44:27 2024 X-Original-To: questions@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 4XPzCx6VC9z5YS53 for ; Fri, 11 Oct 2024 07:44:29 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPzCw6W6Sz4pFj for ; Fri, 11 Oct 2024 07:44:28 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id BE38F4E690; Fri, 11 Oct 2024 00:44:27 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? In-Reply-To: <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14176.1728632667.1@segfault.tristatelogic.com> Date: Fri, 11 Oct 2024 00:44:27 -0700 Message-ID: <14177.1728632667@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.09 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XPzCw6W6Sz4pFj X-Spamd-Bar: -- In message <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net>, Ralf Mardorf wrote: >After countless discussions about [1] and having recovered and not >recovered lost data myself, I am firmly convinced that it is sufficient >for a private household to overwrite just 1 time. After that Joe and >Jane Lunchbucket can't recover the data anymore and it's also quasi >impossible for a geek to recover something. Agree. But I'm a "belt & suspenders" kind of guy. :-) >The problem with the Lunchbucket family's HDDs is that they only replace >them when they are defective anyway. At best, you can free up stuck >heads and be happy if you can get your 4 TB drive overwritten at all. I should know one way or the other in about 8 hours. >It is not for nothing that it is said that you should mount a drive >"read only" as soon as possible after data has been lost in order to >have any chance of recovering anything at all. Fortunately, I had the Good Sense to have multiple recent backups, so I don't believe I lost anything. But I cloned the failing drive onto a fresh near-new drive (which I'm using now) which could posibly mean that I have some corrupted files on the new production drive. I'm in the process of md5'ing all important files on both the new production drive and one of my backups. When that's all done I'll compare the two sets of md5 hashes and retrieve anything where I got a mismatch from the backup drive. (I believe that the backup in question was made _before_ I installed the now-failing drive and tried to use it as a production drive.) From nobody Fri Oct 11 07:39:16 2024 X-Original-To: questions@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 4XPzFr2n0mz5YSBj for ; Fri, 11 Oct 2024 07:46:08 +0000 (UTC) (envelope-from markus.graf@markusgraf.net) Received: from mx.virtual-earth.de (mx.virtual-earth.de [176.9.220.178]) (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 4XPzFd6JgLz4q45 for ; Fri, 11 Oct 2024 07:45:57 +0000 (UTC) (envelope-from markus.graf@markusgraf.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=mx.virtual-earth.de header.s=220816 header.b=B0YLwdG7; spf=temperror (mx1.freebsd.org: error in processing during lookup of markus.graf@markusgraf.net: DNS error) smtp.mailfrom=markus.graf@markusgraf.net; dmarc=temperror reason="SPF/DKIM temp error" header.from=markusgraf.net (policy=temperror) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.virtual-earth.de; s=220816; t=1728632745; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BXY8ym52Y4ed4vmg2uZGKk1bKhpP4lbVFqsOfuJFYvY=; b=B0YLwdG7nK116G0oLACcynNQ1qbcJJGtxncab3b2vjVsSjSMsq0LBS1IjssukYrNnrd1+Y YgOBXxdlp5TCX8PH3rNMopjM7jP4+uE/jRvJe5olHnLH6gnKB3L0RkAaf9ZOZeX9ewbQ0z +ao/Nw60/06uCoccg229C3Iy1p0GQUw= Received: from beasty.markusgraf.net (p200300E12F27D300Dc02Fd481c85d7a4.dip0.t-ipconnect.de [2003:e1:2f27:d300:dc02:fd48:1c85:d7a4]) by mx.goodhope.local (OpenSMTPD) with ESMTPSA id 277b0a25 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Fri, 11 Oct 2024 09:45:45 +0200 (CEST) References: <5117.1728561469@segfault.tristatelogic.com> User-agent: mu4e 1.8.13; emacs 29.4 From: Markus Graf To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? Date: Fri, 11 Oct 2024 09:39:16 +0200 In-reply-to: Message-ID: <86cyk7hyl3.fsf@beasty.markusgraf.net> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Spamd-Result: default: False [-2.19 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.994]; R_DKIM_ALLOW(-0.20)[mx.virtual-earth.de:s=220816]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:24940, ipnet:176.9.0.0/16, country:DE]; R_SPF_DNSFAIL(0.00)[temporary DNS error]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_DNSFAIL(0.00)[markusgraf.net : SPF/DKIM temp error,none]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DKIM_TRACE(0.00)[mx.virtual-earth.de:+] X-Rspamd-Queue-Id: 4XPzFd6JgLz4q45 X-Spamd-Bar: -- Years ago I heared the recommended way for embassies was to have an emergency set ready, consisting of a solid chisel and a heavy hammer. Make shure to shatter the disks. When you have time put your chisel to the the hard disk where the platters are, then hit hard. If in a hurry put the chisel to the laptop where the disks are an hit hard ;-) Tomek CEDRO writes: > sysutils/ddrescue helped me to read broken drives several times, > it > retries then skips on errors. > > sysutils/e2fsprogs has program badblocks that can help disk > rebuild in > read only mode, or make things worse depending how its broken, > and you > can use it many loops of destructive write test to overwrite > data. > > the safest way to dispose sensitive data is by physical > destruction :-) -- Markus Graf From nobody Fri Oct 11 07:47:29 2024 X-Original-To: questions@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 4XPzHV58rJz5YS8W for ; Fri, 11 Oct 2024 07:47:34 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XPzHT2nHGz4r0r for ; Fri, 11 Oct 2024 07:47:33 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=DA0cJc4n; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4XPzHS056gzDqH9 for ; Fri, 11 Oct 2024 07:47:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728632852; bh=W6lEXwYwQf9Fgbz/5JsHbMsOxKwKPq1doeviWCBUe68=; h=Subject:From:To:Date:In-Reply-To:References:From; b=DA0cJc4n3fPQ1OBDRZ8IurF1zMd5klrvAym+wUYVNDoa1FSX1sxR82VNcKtqLsXeh Y7j9wsmoH94D/cBmEYEm1PxDXvrjtcssWzh1nxYK2PHmW3Apiydr1QMrQKBqb0WyK8 q5WC9Ja7Qz2e3eQoKAx+WvDG/1TOj9HlQBq7d0pQ= X-Riseup-User-ID: 343164A90913514B65FCAB0B1A610BED41BF60CC1102303E16E900BC949E9E66 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XPzHR2vTHzJmvR for ; Fri, 11 Oct 2024 07:47:31 +0000 (UTC) Message-ID: Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Oct 2024 09:47:29 +0200 In-Reply-To: <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net> References: <5117.1728561469@segfault.tristatelogic.com> <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> <0bd5d79d35bb036fc73cd226edae1b969b22e3ee.camel@riseup.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.20 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx1.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[198.252.153.129:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[riseup.net:+]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XPzHT2nHGz4r0r X-Spamd-Bar: ---- On Fri, 2024-10-11 at 09:12 +0200, Ralf Mardorf wrote: > After countless discussions [...] I am firmly convinced that it is > sufficient for a private household to overwrite just 1 time. >=20 > The problem with the Lunchbucket family's HDDs is that they only > replace them when they are defective anyway. For sure we will not use kind of a shred program that tries to overwrite files, we will use kind of a dd command with a random pattern, zeros or else. On Thu, 2024-10-10 at 04:57 -0700, Ronald F. Guilmette wrote: > I could just dd /dev/zero to the thing. But there's a catch. > According to what I have read, dd will halt if it encounters a write > error. By https://unix.stackexchange.com/questions/229354/how-to-ignore-write-errors-= while-zeroing-a-disk a "sdd" command is mentioned, wich seems to be provided by https://sourceforge.net/projects/schilytools/files/ and it might be available for FreeBSD, https://www.freshports.org/devel/schilybase . FWIW the Arch User repository provides schily-tools-sdd, but Arch Linux doesn't provide a live media. Ubuntu and friends provide a live media, but they don't provide schilytools, but it might build without issues on an Ubuntu or so live media, https://www.unixmen.com/install-schily-tools-on-linux/ . From nobody Fri Oct 11 07:59:42 2024 X-Original-To: questions@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 4XPzYX3pjFz5YSxv for ; Fri, 11 Oct 2024 07:59:44 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XPzYW3nDsz4tn6 for ; Fri, 11 Oct 2024 07:59:43 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id 8534B4E690; Fri, 11 Oct 2024 00:59:42 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? In-Reply-To: List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14322.1728633581.1@segfault.tristatelogic.com> Content-Transfer-Encoding: quoted-printable Date: Fri, 11 Oct 2024 00:59:42 -0700 Message-ID: <14323.1728633582@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.09 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XPzYW3nDsz4tn6 X-Spamd-Bar: -- In message , = Ralf Mardorf wrote: >https://unix.stackexchange.com/questions/229354/how-to-ignore-write-error= s-while-zeroing-a-disk > >a "sdd" command is mentioned, wich seems to be provided by >https://sourceforge.net/projects/schilytools/files/ > >and it might be available for FreeBSD, >https://www.freshports.org/devel/schilybase . > >FWIW the Arch User repository provides schily-tools-sdd, but Arch Linux >doesn't provide a live media. Ubuntu and friends provide a live media, >but they don't provide schilytools, but it might build without issues on >an Ubuntu or so live media, >https://www.unixmen.com/install-schily-tools-on-linux/ . Thanks Ralf. I'll definitely give this a try if I can't get the SMART secure erase to complete. From nobody Fri Oct 11 08:21:11 2024 X-Original-To: questions@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 4XQ02N5TVrz5YVJb for ; Fri, 11 Oct 2024 08:21:16 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XQ02M53H7z3xcP for ; Fri, 11 Oct 2024 08:21:15 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=SJjPSyaV; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XQ02L1gz6z9vLs for ; Fri, 11 Oct 2024 08:21:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728634874; bh=3fTfnBmYTU1c8sNsH2m9EH7z0hfLMrW1FQdZ8NITHjA=; h=Subject:From:To:Date:In-Reply-To:References:From; b=SJjPSyaVt6HYUN7tf+IS3SI9dvbqxvpr+giJ9dxdgPBKKQBMNjFsrErcqTDJ0hD8z dJCneEwMRVUFVBSIcHbnV6462DCYxO35yUmRP2SxozE0hqXzAd3pVHoRJjUUJySq5O kg+JmeM1nykScmgBicWA3/ilxqChcc/nwCXNP1ZE= X-Riseup-User-ID: 3AD00552FAE6BEDFA66C8C8745A4207711770AD4B93E8979785235EF3CD40A16 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XQ02K5tT8zJsS8 for ; Fri, 11 Oct 2024 08:21:13 +0000 (UTC) Message-ID: <88d89e51653960a519a85c5edd9686e73ea9e144.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Oct 2024 10:21:11 +0200 In-Reply-To: <14177.1728632667@segfault.tristatelogic.com> References: <14177.1728632667@segfault.tristatelogic.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XQ02M53H7z3xcP X-Spamd-Bar: ---- On Fri, 2024-10-11 at 00:44 -0700, Ronald F. Guilmette wrote: > > It is not for nothing that it is said that you should mount a drive > > "read only" as soon as possible after data has been lost in order to > > have any chance of recovering anything at all. >=20 > Fortunately, I had the Good Sense to have multiple recent backups, so > I don't believe I lost anything. I just wanted to say that on the one hand we rightly fear data loss and therefore make backups instead of relying on the fact that one time overwritten data possibly can be restored, because it's basically not possible, at least not without a lab with glowing green liquids, flashing Tesla coils and stuff like that and on the other hand, we believe that data that has only been overwritten once can be recovered by any petty criminal who can wear a black hoodie and is able to sit on a chair in front of a keyboard, without equipment such as glowing green liquids, flashing Tesla coils. Data that has been overwritten even once is gone, to be able to read it you need at least the right Torx[tm] screwdriver, wearing a hoodie and being able to sit on a chair is no longer enough. From nobody Fri Oct 11 08:39:56 2024 X-Original-To: questions@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 4XQ0S13z2Jz5YWj1 for ; Fri, 11 Oct 2024 08:40:01 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XQ0S03VP8z41S1 for ; Fri, 11 Oct 2024 08:40:00 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=mB4TCWQ6; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4XQ0Rz4GG5zDqPJ for ; Fri, 11 Oct 2024 08:39:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728635999; bh=1N+gZeMYArve+hrZ0q+eOTE1v6Hs99i6tu5ebegM7iQ=; h=Subject:From:To:Date:In-Reply-To:References:From; b=mB4TCWQ6Rn+3SZgITL8TMsY3kFp8TiKA3YrJkP1e18KkKxeEXZX9mgCEOxC0Q0ssS a2Y+gnCQImmH5uLL0KgzvVtTNYOMggUImpMfXSYWcVxrO5LFC2n7mIajcHj+4N0UP1 V090CsZ6cAXKKde38A2K6Bb+ZhY3kvQ0Wmh8/R9k= X-Riseup-User-ID: B726DC6D0B177AF7EECE866B8C6D9002495072B025040420289597731DC9A93B Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4XQ0Rz08f8zFtpX for ; Fri, 11 Oct 2024 08:39:58 +0000 (UTC) Message-ID: <396ccf3a13ac75765e9014588f2feacd70a38cd5.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Oct 2024 10:39:56 +0200 In-Reply-To: References: <5117.1728561469@segfault.tristatelogic.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.20 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx1.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[198.252.153.129:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[riseup.net:+]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XQ0S03VP8z41S1 X-Spamd-Bar: ---- On Thu, 2024-10-10 at 14:21 +0200, Matthias Apitz wrote: > Overwriting the data will not help. The reading head(s) could be > adjusted and read the data on the side of the old track. There is no side of an old track on a Shingled Magnetic Recording HDD, the tracks are overlapping. Apart from this triviality, what do you use to adjust the position of the heads, green glowing liquid or Tesla Colis? What is possible is by no means affordable for everyone. You have to be very special and have very specialised opponents for such forensic methods to come into question. From nobody Fri Oct 11 09:30:51 2024 X-Original-To: questions@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 4XQ1Zn0z8lz5Yb0k for ; Fri, 11 Oct 2024 09:30:57 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XQ1Zm1JnDz44w6 for ; Fri, 11 Oct 2024 09:30:56 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=qUZ94D8W; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4XQ1Zk4YnczDqNL for ; Fri, 11 Oct 2024 09:30:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728639054; bh=/vsM7OplEoTyNCRQMunAAEZ1cTWRP9JJPDfIW4Nybt8=; h=Subject:From:To:Date:In-Reply-To:References:From; b=qUZ94D8W5oBnkkeN1JHHlw1STQPLQgivqOLpzF2N/Xu7U0wuD3q0f478R+MrFa6zt ocIzxV1L9xaQGMq78DtUVnr6HdPQksjpEX2UyV9kUZ7SWgiK4TryBMyiAoNWJiy1RL hb8IqwNwkqK1J1e0XW24LXeMVrw0SHqudkS/8SiA= X-Riseup-User-ID: 8C71D7BEFA34FC3B79DAC9D68D4076EEFE0E84A7AF9DB1F2C876D5363D6C4901 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XQ1Zk0Q5HzJmvR for ; Fri, 11 Oct 2024 09:30:53 +0000 (UTC) Message-ID: Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Oct 2024 11:30:51 +0200 In-Reply-To: <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> References: <5117.1728561469@segfault.tristatelogic.com> <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.20 / 15.00]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx1.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[198.252.153.129:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[riseup.net:+]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XQ1Zm1JnDz44w6 X-Spamd-Bar: ---- On Fri, 2024-10-11 at 13:42 +1100, Dewayne Geraghty wrote: > We bench-drilled the hard-disks before Sorry for the flood of emails, a virus (for humans, not computers) is keeping me glued to the keyboard. Drill holes probably have a much more dramatic effect on hard discs than on CDs, as the burr of a drill hole alone ensures that there is no clearance to the heads, so that the discs can no longer rotate. Open and deburr? ;) I've just googled the old audio CD myth from the early days of the CD, namely that you could drill large holes in them and still use them without any loss of quality, and I've actually found a video in German that is only 5 years old and still claims this IMO nonsense and justifies it with https://en.wikipedia.org/wiki/Cross-interleaved_Reed%E2%80%93Solomon_coding . However, the whole thing was not demonstrated. If thick holes have been drilled into all the places where the audio recording is stored in which you say the PIN of your debit card, then even "interpolation" cannot restore the spoken PIN. I will now try to keep my fingers off the keyboard. My point should be clear by now. There are too many myths about how data can still be recoverd. What may potentially be possible is hardly to be expected in reality. From nobody Fri Oct 11 09:46:29 2024 X-Original-To: questions@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 4XQ1wt6g36z5YcJ8 for ; Fri, 11 Oct 2024 09:46:38 +0000 (UTC) (envelope-from lumiwa@dismail.de) Received: from mx1.dismail.de (mx1.dismail.de [78.46.223.134]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XQ1ws3JD6z49W3 for ; Fri, 11 Oct 2024 09:46:37 +0000 (UTC) (envelope-from lumiwa@dismail.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=dismail.de header.s=20190914 header.b=WepxVV5U; spf=pass (mx1.freebsd.org: domain of lumiwa@dismail.de designates 78.46.223.134 as permitted sender) smtp.mailfrom=lumiwa@dismail.de; dmarc=pass (policy=reject) header.from=dismail.de Received: from mx1.dismail.de (localhost [127.0.0.1]) by mx1.dismail.de (OpenSMTPD) with ESMTP id 70a6d843 for ; Fri, 11 Oct 2024 11:46:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=dismail.de; h=date:from :to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=20190914; bh=n2UFMjn1 nRVO4lHpsW7dpV75JtBdsb682PFDo9jwk4I=; b=WepxVV5U/nMyfd9lxmlsxQSN T9Lc82Es/Px869JqLNY5rsYrqbCFXxFOmX94jYg9mvfEGZWvP4BsHHEclnDRT7VG UxCYp6iajdr1wd38XLaG1r2JXTfQT7aHmBlw+N1/dR32rZATcb9mwPsRtVLPbPTd Inv8knN41S7rfmAF2O0iYtSH0wExw7SqtcBYgI1n/jCmL54q+ELBPvHF8MRVi3Ut 0sX40NkWu+vcjPAbT7JtOqpPcJoDGZRSPEyV+bUE5pvz6XaztnOZJmUz1/pjcpZV uJ4BYloiio61nYePLMTILKpj9k8dFXX5ReO0M2Qar5UW/dYrszYroHEpC90fag== Received: from smtp2.dismail.de ( [10.240.26.12]) by mx1.dismail.de (OpenSMTPD) with ESMTP id c4465533 for ; Fri, 11 Oct 2024 11:46:33 +0200 (CEST) Received: from smtp2.dismail.de (localhost [127.0.0.1]) by smtp2.dismail.de (OpenSMTPD) with ESMTP id 9fe826fe for ; Fri, 11 Oct 2024 11:46:33 +0200 (CEST) Received: by dismail.de (OpenSMTPD) with ESMTPSA id 3e83169a (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for ; Fri, 11 Oct 2024 11:46:33 +0200 (CEST) Date: Fri, 11 Oct 2024 05:46:29 -0400 From: LuMiWa To: questions@freebsd.org Subject: Re: FreeBSD releases Message-ID: <20241011054629.7be5def2@dismail.de> In-Reply-To: References: <20241009063710.09572e05@dismail.de> X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-5.09 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[dismail.de:dkim]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[dismail.de,reject]; R_DKIM_ALLOW(-0.20)[dismail.de:s=20190914]; R_SPF_ALLOW(-0.20)[+ip4:78.46.223.134]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[78.46.223.134:from]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:78.46.0.0/15, country:DE]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[dismail.de:+] X-Rspamd-Queue-Id: 4XQ1ws3JD6z49W3 X-Spamd-Bar: ----- On Thu, 10 Oct 2024 23:09:41 -0700 Kevin Oberman wrote: > On Wed, Oct 9, 2024 at 3:37=E2=80=AFAM LuMiWa wrote: >=20 > > Hi! > > > > As a binary packages user I have one question, please. > > For example: > > releng/14.1 14.1-RELEASE June 4, 2024 > > expected eol March 31, 2025 > > > > This mean that are all packages built on version 14.0 for six > > months. This mean if we want applications built for 14.1 we need to > > use ports, special for apps like drm-kmod and more and build by > > ourselves. Am I wright? > > > > Thank you. > > > > -- > > =E2=80=9CI hate books; they only teach us to talk about things we know > > nothing about.=E2=80=9D > > > > =E2=80=95 Jean-Jacques Rousseau > > > > Yes. As long as 14.0 was supported, ports are built on 14.0. Now > > that 14.0 > is EOL, as of October 1, ports are built on 14.1. There SHOULD be no > problem in running 14.0 packages on 14.1 as the user space ABI is > guaranteed to not change. The notable exception is ports that provide > kernel modules. While most work as FreeBSD tries to keep the ABI > consistent, it is not guaranteed. Notably, the drm-*kmod packages > need to be built from the port with the kernel sources matching the > kernel sources on the build machine. This has also happened with the > virtualbox kmod and probably others. >=20 > For multiple systems running hte same kernel, the port may be built > once, a package built and copied to other systems. >=20 >=20 Thank you very much. When I used ports I never had a problem but when I switched to packages problems start showing... --=20 =E2=80=9CI hate books; they only teach us to talk about things we know noth= ing about.=E2=80=9D =E2=80=95 Jean-Jacques Rousseau=20 From nobody Fri Oct 11 15:34:10 2024 X-Original-To: questions@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 4XQ9fJ5S4sz5Z31Y for ; Fri, 11 Oct 2024 15:34:32 +0000 (UTC) (envelope-from robert@rrbrussell.com) Received: from fhigh-a6-smtp.messagingengine.com (fhigh-a6-smtp.messagingengine.com [103.168.172.157]) (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 4XQ9fH6Stcz4rqt for ; Fri, 11 Oct 2024 15:34:31 +0000 (UTC) (envelope-from robert@rrbrussell.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=rrbrussell.com header.s=fm2 header.b=cVNiDbVX; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="E KwkKp3"; spf=pass (mx1.freebsd.org: domain of robert@rrbrussell.com designates 103.168.172.157 as permitted sender) smtp.mailfrom=robert@rrbrussell.com; dmarc=pass (policy=quarantine) header.from=rrbrussell.com Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id 07BB71140204 for ; Fri, 11 Oct 2024 11:34:31 -0400 (EDT) Received: from phl-imap-10 ([10.202.2.85]) by phl-compute-06.internal (MEProxy); Fri, 11 Oct 2024 11:34:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rrbrussell.com; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1728660871; x=1728747271; bh=HAoswNqP4HJ9FRrXvcht/ZRbQLqvkVmLu6tmJwsYEcc=; b= cVNiDbVXwEDjar3Nx2z7saUqAkMzMn6H+y9qsAmr5/YPEOCHr8WeUV1sRLlMAoqH LKYXerqaGNAiLiY9O5kNcHDYOOTdWEn8wI733hDc8ggg1X6yk5D7/N/KywGhxlB6 kaH1OZ4UXmRLzT9biYcwVB4IHYBh7CRbMiK9uJ95o/ZYS09k0GJkqSeNJT+inNp+ QTDvwoFMvypAWizNgW/pomDD6t1U3aeGyDY41yi9A1eO3bmlmdh98nLdIab3yhUp nkzTCYPhsjDjBZlInKeDh74wdvDnVy4Q6qunomAxMbnVt4uAORmoPt+cSNupV3JH uIg7DQc6u/B03jShFjsI9A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1728660871; x= 1728747271; bh=HAoswNqP4HJ9FRrXvcht/ZRbQLqvkVmLu6tmJwsYEcc=; b=E KwkKp3zZ8YRg4GnFBaxzjBOVUR3n4UK9BJvoxLfaJ3bDAMOtn4oS/wXrjKE2l+Hx etlJlJ2VxjxGb1U6XCE92ln26ytT9kTialsKxSdVM0E5ut7Z444s6JM/2DP6FP52 9Pmqb0HwKQYw++500wTveMmTeQs30mtjzLwr89JzfMwZiVyiSEn0NdC9hf6BhkZc WnQSmfcHLdkFnneAIw0RA0vXWXMKZ5y67ERrfHwbqNG9g1KT+byBiZLP1s2GTqIM p6uSvJboeZBlBccMDLDLAuz2GtTnU2FRR1XsMZGGvdgnfHdhtFc8ItZ/f8COaG45 tWDUMc2AAGAYX7RGUu20w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdefkedgledtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefoggffhf fvkfgjfhfutgfgsehtqhertdertdejnecuhfhrohhmpehrohgsvghrthesrhhrsghruhhs shgvlhhlrdgtohhmnecuggftrfgrthhtvghrnhepudehleetkeeujeekjefflefgueektd fggeetuddttedtudejgfffffeileeggfegnecuvehluhhsthgvrhfuihiivgeptdenucfr rghrrghmpehmrghilhhfrhhomheprhhosggvrhhtsehrrhgsrhhushhsvghllhdrtghomh dpnhgspghrtghpthhtohepuddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepqhhu vghsthhiohhnshesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: ie421460a:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id B27A93C0066; Fri, 11 Oct 2024 11:34:30 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Date: Fri, 11 Oct 2024 10:34:10 -0500 From: robert@rrbrussell.com To: questions@freebsd.org Message-Id: <746da1d5-72f8-42fc-917b-f4de0e4d98f9@app.fastmail.com> In-Reply-To: <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> References: <5117.1728561469@segfault.tristatelogic.com> <2544410a-8a99-4b2e-a194-c8326a2e0ddd@heuristicsystems.com.au> Subject: Re: How to zero a failing disk drive before disposal? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.07 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.983]; DMARC_POLICY_ALLOW(-0.50)[rrbrussell.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; R_DKIM_ALLOW(-0.20)[rrbrussell.com:s=fm2,messagingengine.com:s=fm2]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.157:from]; XM_UA_NO_VERSION(0.01)[]; FROM_NO_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; FREEFALL_USER(0.00)[robert]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[rrbrussell.com:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4XQ9fH6Stcz4rqt X-Spamd-Bar: --- On Thu, Oct 10, 2024, at 21:42, Dewayne Geraghty wrote: > A good question Ronald. I worked for a provider of services for the=20 > statutory care of children (eg removed from parents). There are=20 > significant penalties for certain types of information loss. We=20 > bench-drilled the hard-disks before sending them (out of our chain of=20 > custody) to a furnace. Admittedly this is an extreme case and for the=20 > reasons already stated in this thread, there was no other way to ensur= e,=20 > say a name and location, were not available. > > And yes, all machines have full disk encryption (FDE). > I agree with securing the data, but drilling is not thorough enough to s= top recovery and marks the drive as a high value target. You are basical= ly betting that microscopic magnetic domain scanning will not improve fa= ster than the areal storage density of the drives you throw away. Not a = bet I want to take personally. > > For personal devices we overwrite the device multiple times, though I'= m=20 > interested in what a "ATA Secure Erase" does to a healthy storage devi= ce=20 > and whether all sectors are touched? ATA Secure Erase is a firmware level overwrite and reread of all physica= l drive sectors. I have seen the drive=E2=80=99s bad sector count increa= sed by this process. It takes slightly longer than a simple dd if=3D/dev= /zero of=3Ddrive. I don=E2=80=99t suggest filling a drive entirely with zeros or ones. Tho= se writes can be =E2=80=9Coptimized=E2=80=9D out by the firmware. It mig= ht set a bit flag in the sector header instead of performing the full wr= ite. They don=E2=80=99t complete faster, they just aren=E2=80=99t guaran= teed to actually overwrite the old data. The why has to do with a very l= ong side tangent about how MFM encodings with error correction work. If you want to overwrite use anything except for a string of all ones or= zeros. From nobody Fri Oct 11 16:22:00 2024 X-Original-To: questions@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 4XQBjH0lQqz5Z5Y2 for ; Fri, 11 Oct 2024 16:22:11 +0000 (UTC) (envelope-from ml-ktk@netlabs.org) Received: from r2-d2.netlabs.org (r2-d2.netlabs.org [213.238.45.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XQBjF3rKXz52sl for ; Fri, 11 Oct 2024 16:22:09 +0000 (UTC) (envelope-from ml-ktk@netlabs.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of ml-ktk@netlabs.org designates 213.238.45.90 as permitted sender) smtp.mailfrom=ml-ktk@netlabs.org; dmarc=none Received: (qmail 23452 invoked by uid 89); 11 Oct 2024 16:22:01 -0000 Received: by simscan 1.4.0 ppid: 23447, pid: 23449, t: 0.1347s scanners: clamav: 0.99.2/m:59/d:26096 Received: from unknown (HELO ?192.168.96.180?) (ml-ktk@netlabs.org@213.55.185.244) by 0 with ESMTPA; 11 Oct 2024 16:22:01 -0000 Message-ID: <3b3e5cc8-3624-40ab-a1b3-bbf9af58b16b@netlabs.org> Date: Fri, 11 Oct 2024 18:22:00 +0200 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Issue with MediaWiki Installation: IntlException and Locale Problems in Apache To: questions@freebsd.org References: Content-Language: en-US From: Adrian Gschwend In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.22 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.926]; R_SPF_ALLOW(-0.20)[+ip4:213.238.45.90/32]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:9211, ipnet:213.238.32.0/20, country:DE]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[netlabs.org]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4XQBjF3rKXz52sl X-Spamd-Bar: --- On 30.09.2024 20:39, Adrian Gschwend wrote: > I created a minimal PHP test case to see if I could reproduce the error > outside of MediaWiki. Here's the test script: TL;DR fix summary: Turns out that I screwed up several /usr/loca/ dir permissions by accident (via tar). So poor Apache couldn't read /usr/local/lib anymore which lead to this super weird error with intl. That's also the reason why it worked on cli as I tried that as root... all good now, Apache is happy again. regards Adrian From nobody Fri Oct 11 19:46:07 2024 X-Original-To: freebsd-questions@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 4XQHDd3DWGz5ZKCZ for ; Fri, 11 Oct 2024 19:46:09 +0000 (UTC) (envelope-from lexi@le-fay.org) Received: from fuchsia.eden.le-Fay.ORG (fuchsia.eden.le-fay.org [IPv6:2001:8b0:aab5:107::11]) by mx1.freebsd.org (Postfix) with ESMTP id 4XQHDc3vcvz4BKM for ; Fri, 11 Oct 2024 19:46:08 +0000 (UTC) (envelope-from lexi@le-fay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=le-fay.org header.s=fuchsia header.b=JcB4WkUU; spf=pass (mx1.freebsd.org: domain of lexi@le-fay.org designates 2001:8b0:aab5:107::11 as permitted sender) smtp.mailfrom=lexi@le-fay.org; dmarc=none Received: from iris.eden.le-Fay.ORG (iris.eden.le-fay.org [IPv6:fd12:8247:3:1::7]) by fuchsia.eden.le-Fay.ORG (Postfix) with ESMTP id F363E31B51 for ; Fri, 11 Oct 2024 19:46:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=le-fay.org; s=fuchsia; t=1728675968; bh=yYTj+GKdVUMmmPrIyru2WrK3VV7H1YTuGhyMPE6ysu8=; h=Date:To:From:Subject; b=JcB4WkUUfbeacVaTjdiKWdg7AX6GiVOb36Ysv+Siff44KALzAHBz7SbzLPy8IQWqq HKjEZ0vB415WyJkyBjT1jPKE/Zvi2cTNHSPxaW8ro1fUvAdBWpdD/ACURVIiyHAfYU K1R+mAQnxb5U9iQ0S2n5jSbuEX86+MRnI0JwSgbo= Received: from [IPV6:2001:8b0:aab5:c110:34f9:44b0:3400:c997] (unknown [IPv6:2001:8b0:aab5:c110:34f9:44b0:3400:c997]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by iris.eden.le-Fay.ORG (Postfix) with ESMTPSA id 11A842C0489 for ; Fri, 11 Oct 2024 20:46:06 +0100 (BST) Message-ID: <98c10355-6878-4d92-89c6-c32d97e635b1@le-fay.org> Date: Fri, 11 Oct 2024 20:46:07 +0100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: freebsd-questions@freebsd.org From: Lexi Winter Subject: daemon to auto-renenew Kerberos tickets? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.39 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; R_DKIM_ALLOW(-0.20)[le-fay.org:s=fuchsia]; R_SPF_ALLOW(-0.20)[+ip6:2001:8b0:aab5:107::11:c]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20712, ipnet:2001:8b0::/32, country:GB]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DMARC_NA(0.00)[le-fay.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[le-fay.org:+] X-Rspamd-Queue-Id: 4XQHDc3vcvz4BKM X-Spamd-Bar: -- hello, let's say i run 'kinit --renewable' and get a ticket with a lifetime of 10h which is renewable for 5d. is there some kind of daemon i can run that automatically renew this ticket until the renewable period runs out, until i log out? using MIT Kerberos for Windows, this happens automagically as long as i'm logged in, but i can't find any way to do this in FreeBSD. i understand i could crontab 'kinit -R' or something like that, but i'm hoping for something that does this only for logged-in users, but also for all users who are logged-in. From nobody Sun Oct 13 13:40:16 2024 X-Original-To: questions@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 4XRM1h2JrMz5YyHQ for ; Sun, 13 Oct 2024 13:40:24 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4XRM1f57M5z51Dr for ; Sun, 13 Oct 2024 13:40:22 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com; dmarc=none Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id A684E4E690; Sun, 13 Oct 2024 06:40:16 -0700 (PDT) From: "Ronald F. Guilmette" To: questions@freebsd.org Subject: Re: How to zero a failing disk drive before disposal? In-Reply-To: <746da1d5-72f8-42fc-917b-f4de0e4d98f9@app.fastmail.com> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <32910.1728826816.1@segfault.tristatelogic.com> Content-Transfer-Encoding: quoted-printable Date: Sun, 13 Oct 2024 06:40:16 -0700 Message-ID: <32911.1728826816@segfault.tristatelogic.com> X-Spamd-Result: default: False [-2.10 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_NO_TLS_LAST(0.10)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; DMARC_NA(0.00)[tristatelogic.com]; MISSING_XM_UA(0.00)[] X-Rspamd-Queue-Id: 4XRM1f57M5z51Dr X-Spamd-Bar: -- In message <746da1d5-72f8-42fc-917b-f4de0e4d98f9@app.fastmail.com>, = robert@rrbrussell.com wrote: >I agree with securing the data, but drilling is not thorough enough to >stop recovery and marks the drive as a high value target. You are basical= ly >betting that microscopic magnetic domain scanning will not improve >faster than the areal storage density of the drives you throw away. Not a >bet I want to take personally. OK, so this brings up a new, different, but related problem I have. I'm basically cleaning out my closet and erasing all the drives I no longer need in preparation for selling them on eBay. (If any of you folks need SATA drives, some w/ high mileage, some low, of any size including 4TB, 2TB, 1TB, 500GB, or 250GB let me know via off-list email. I got a lot of them that need to go. Most of what I've got is WD or HGST. I've never been a Seagate fan.) Anyway, one of the drives I've got that I am hoping to dispense with soon is an older model WD "Passport" external 4TB USB3 drive. Optimally, I'd like to simply perform a S.M.A.R.T. secure erase on the thing, but there's a catch. Various online sources say that one needs to use S.M.A.R.T. to set a passowrd on the drive before initiating a S.M.A.R.T. secure erase, HOWEVER it is also said in mutiple places that using S.M.A.R.T. to set a password on a USB external drive can be deadly, as in it may brick the device. HOWEVER it is also said in mutiple places that the exception(s) to this general rule are at least _some_ WD Passport USB external drives. So, do any of you folks happen to know whether I can sefely do this on an older model WD 4TB USB3 Passord drive? The original box, which I still ha= ve, says: MODEL: WDBYFT0040BBK-WESN The thing identifies itself to S.M.A.R.T. as follows: Model Family: Western Digital Elements / My Passport (USB, AF) Device Model: WDC WD40NMZW-11GX6S1 Serial Number: WD-WX41D77D4DX6 LU WWN Device Id: 5 0014ee 607feedd8 Firmware Version: 01.01A01 User Capacity: 4,000,753,475,584 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-3 (minor revision not indicated) SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Is there a list someplace of which WD USB Passport drives are safe to manipulate via S.M.A.R.T.? I need to erase this for disposal, but obviously, I would prefer not to br= ick it. Unless I can be sure that I can do that safely using S.M.A.R.T. comma= nds I'll have no choice but to just dd /dev/zero to the thing and hope that do= es the job. Regards, rfg P.S. My apologies that this topic is not really FreeBSD specific. I won'= t complain if someone hits me with a wet noodle and/or chastizes me for bein= g off-topic. I beg all indulgence. P.P.S. I'm actually not THAT paranoid. I kinda don't think that there a= re any nation state actors waiting around for me to sell my tired old drives on e= Bay. :-) That having been said, I still don't plan on buying any pagers anytim= e soon. = From nobody Sun Oct 13 15:05:29 2024 X-Original-To: questions@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 4XRNw03QHbz5Z4Gw for ; Sun, 13 Oct 2024 15:05:36 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XRNvy4Wj4z56Kd for ; Sun, 13 Oct 2024 15:05:34 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=eKIcFXQs; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XRNvx07hlz9vfY for ; Sun, 13 Oct 2024 15:05:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728831933; bh=4MY4DoRGPXrgIUzITqNryVkBTuMCxqPEWqam77t2P6U=; h=Subject:From:To:Date:In-Reply-To:References:From; b=eKIcFXQsfxQwDd454fXL2U0Qrc98NIJjvjemi/f6D1UBHJyIEomAwIa9OGT40XkQ7 CVIGJQ199cjl9ihBdwYgMHXyfaeItBR6biN8rQG8qMGwELhgmNAJt7NxR1ox+4UiLt QKxNKctlJCWoj678Id2ztzGIzmSr3bpqDCHiEWV0= X-Riseup-User-ID: D42F359844B22E6202D44FAEA67484890DF5018ADB5E2310C0F8B32777CA3DBA Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4XRNvw4NJ0zJskT for ; Sun, 13 Oct 2024 15:05:32 +0000 (UTC) Message-ID: <0687f794db7f586c45646bb475bd833b604a2175.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Sun, 13 Oct 2024 17:05:29 +0200 In-Reply-To: <32911.1728826816@segfault.tristatelogic.com> References: <32911.1728826816@segfault.tristatelogic.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XRNvy4Wj4z56Kd X-Spamd-Bar: ---- On Sun, 2024-10-13 at 06:40 -0700, Ronald F. Guilmette wrote: > Anyway, one of the drives I've got that I am hoping to dispense with > soon is an older model WD "Passport" external 4TB USB3 drive.=C2=A0 > Optimally, I'd like to simply perform [snip] Hi, Since I use Linux daily and FreeBSD only rarely, I do not know the programmes that FreeBSD offers for this purpose, but I fear that there will only be insignificant differences in this area. Under Linux it is, apart from allegedly existing exceptions, not possible to access an underlying, mostly SATA drive via the USB controller. >From off-list correspondence, I know with absolute certainty that the joys of normal operation with drives in USB enclosures are actually always the plague, no matter which OS you use. I use a specific enclosure from a specific company, whose controller has firmware that causes me no problems in normal operation. I assemble these things myself. If you don't have an alternative connection to the USB port and the case can't be opened, then the desired commands will most likely not get through to the drive. Regards, Ralf Translated with DeepL.com (free version) From nobody Sun Oct 13 16:42:29 2024 X-Original-To: questions@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 4XRR4K359pz5ZBKb for ; Sun, 13 Oct 2024 16:42:57 +0000 (UTC) (envelope-from robert@rrbrussell.com) Received: from fhigh-a4-smtp.messagingengine.com (fhigh-a4-smtp.messagingengine.com [103.168.172.155]) (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 4XRR4H6s19z451y for ; Sun, 13 Oct 2024 16:42:55 +0000 (UTC) (envelope-from robert@rrbrussell.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=rrbrussell.com header.s=fm2 header.b=X5eEHE7h; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="a 5bSeXd"; spf=pass (mx1.freebsd.org: domain of robert@rrbrussell.com designates 103.168.172.155 as permitted sender) smtp.mailfrom=robert@rrbrussell.com; dmarc=pass (policy=quarantine) header.from=rrbrussell.com Received: from phl-compute-06.internal (phl-compute-06.phl.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id 5F0D311400E3 for ; Sun, 13 Oct 2024 12:42:50 -0400 (EDT) Received: from phl-imap-10 ([10.202.2.85]) by phl-compute-06.internal (MEProxy); Sun, 13 Oct 2024 12:42:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rrbrussell.com; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1728837770; x=1728924170; bh=37m/Ja0EskIQi5ZY5ndpw0/T/C2Vk1O+1PWrn6ZaFjg=; b= X5eEHE7hB/hvXmqDlJ6PXkd/1l08VxosKyOjrBEpD3MRtFZ7pIXWinSWt4eecV4z QGwzr91Gqc1quVU2nDFNKoGOO8Tijs4jJ1HFg7J/cBVE3Llc5/vTCbHZ7O2JAf5x NLgHxsqEQ3M62zu1xwqgT+Anu3YvKILYZS/5p0X5/dTZ8qzJ+29KLFTC7tS44kpV wI/VFeCOlYV7BflnL5I6C0obmqnpiQMZU9ciF5DhhJeI3YBpX21/MWVYNgw8smSR PXeYFiggPB9vS+hRSGexGCZwnDs3A8FS8b2jkTAkNQ2lBju0c2g4WGGS33bzH96S xEsVxy+rbO3AApp6EUP6YQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1728837770; x= 1728924170; bh=37m/Ja0EskIQi5ZY5ndpw0/T/C2Vk1O+1PWrn6ZaFjg=; b=a 5bSeXddWbNHfZ5aSFXwCUydrurJWdVqXgpHevpLP3dqcysDFjXhlt7b4JliL4ixh KAOt3MjMkFJgQHAJXHoiREqSqMk9tuhKW0bOpRxDYM54AKXI1vVS9bwzphnRzZHK Cp3OgDY3/rnOZE1oub4lpyUiApxakZm3IA0cHaZHpD6d/AX24CGjY1h/wmjq2s2n TwdJ3gaLKOBXa9ViWLAx7GBHjdIXyFWbRCT/XRZkenQhfZot+bbH3S5Rmvco8C8P 1gxNzJLF3Ks7x1gUD4W9vdwaXafmqdEZ7gm0vtOOk60f2yjtq/il3+BbQ81kArks A4AGjvgJLhcSQO5UDlWVg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdegfedguddtiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepofggff fhvffkjghfufgtgfesthhqredtredtjeenucfhrhhomheprhhosggvrhhtsehrrhgsrhhu shhsvghllhdrtghomhenucggtffrrghtthgvrhhnpeduheelteekueejkeejffelgfeuke dtgfegtedutdettddujefgffffieelgefggeenucevlhhushhtvghrufhiiigvpedtnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehrohgsvghrthesrhhrsghruhhsshgvlhhlrdgtoh hmpdhnsggprhgtphhtthhopedupdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehq uhgvshhtihhonhhssehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: ie421460a:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 23EE23C0066; Sun, 13 Oct 2024 12:42:50 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 Date: Sun, 13 Oct 2024 11:42:29 -0500 From: robert@rrbrussell.com To: questions@freebsd.org Message-Id: <06ab6d80-2ebd-4f23-b8e6-136c28b2e98f@app.fastmail.com> In-Reply-To: <0687f794db7f586c45646bb475bd833b604a2175.camel@riseup.net> References: <32911.1728826816@segfault.tristatelogic.com> <0687f794db7f586c45646bb475bd833b604a2175.camel@riseup.net> Subject: Re: How to zero a failing disk drive before disposal? Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.09 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[rrbrussell.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; R_DKIM_ALLOW(-0.20)[rrbrussell.com:s=fm2,messagingengine.com:s=fm2]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.155:from]; XM_UA_NO_VERSION(0.01)[]; FREEFALL_USER(0.00)[robert]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; FROM_NO_DN(0.00)[]; ASN(0.00)[asn:151847, ipnet:103.168.172.0/24, country:AU]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[rrbrussell.com:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4XRR4H6s19z451y X-Spamd-Bar: --- On Sun, Oct 13, 2024, at 10:05, Ralf Mardorf wrote: > On Sun, 2024-10-13 at 06:40 -0700, Ronald F. Guilmette wrote: >> Anyway, one of the drives I've got that I am hoping to dispense with >> soon is an older model WD "Passport" external 4TB USB3 drive.=C2=A0 >> Optimally, I'd like to simply perform [snip] > > Hi, > > Since I use Linux daily and FreeBSD only rarely, I do not know the > programmes that FreeBSD offers for this purpose, but I fear that there > will only be insignificant differences in this area. > > Under Linux it is, apart from allegedly existing exceptions, not > possible to access an underlying, mostly SATA drive via the USB > controller. > > From off-list correspondence, I know with absolute certainty that the > joys of normal operation with drives in USB enclosures are actually > always the plague, no matter which OS you use. > > I use a specific enclosure from a specific company, whose controller h= as > firmware that causes me no problems in normal operation. I assemble > these things myself. > > If you don't have an alternative connection to the USB port and the ca= se > can't be opened, then the desired commands will most likely not get > through to the drive. > > Regards, > Ralf > > Translated with DeepL.com (free version) hdparm is the required program on both Linux and *BSD. The procedure is= set drive security password and then issue Secure Erase. =E2=80=94 Robert From nobody Sun Oct 13 17:03:55 2024 X-Original-To: questions@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 4XRRXq6q3qz5ZChh for ; Sun, 13 Oct 2024 17:04:11 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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 (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XRRXp1bFxz476s for ; Sun, 13 Oct 2024 17:04:10 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=eNCdhX3g; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4XRRXn0GTMz9vd5 for ; Sun, 13 Oct 2024 17:04:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1728839049; bh=F+aFXhz299L67D4jvNCGPk25kqrDEQoetdo2VnQ7XPo=; h=Subject:From:To:Date:In-Reply-To:References:From; b=eNCdhX3gldP4uPK3RyeigN6sWzVN2PRhEpDKIWEDRAektimLLd58yI51U/cbLfcmv 4zXy84jRPg3I9EMju5+uIQffNjoaoOQFkn4hw/pKi7viSjnQvRO5UF7B/HdlXh1e4o cgINlP3oUkZiOBxpt+9Rklo7AU1/kWkWdnCEgahU= X-Riseup-User-ID: 9046E66FFF4DD945F4988C2232CBF4E43FC43D3EE65353097258557EE211EAAA Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4XRRXY2mjbzFwnk for ; Sun, 13 Oct 2024 17:03:57 +0000 (UTC) Message-ID: Subject: Re: How to zero a failing disk drive before disposal? From: Ralf Mardorf To: questions@freebsd.org Date: Sun, 13 Oct 2024 19:03:55 +0200 In-Reply-To: <06ab6d80-2ebd-4f23-b8e6-136c28b2e98f@app.fastmail.com> References: <32911.1728826816@segfault.tristatelogic.com> <0687f794db7f586c45646bb475bd833b604a2175.camel@riseup.net> <06ab6d80-2ebd-4f23-b8e6-136c28b2e98f@app.fastmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 X-Spamd-Result: default: False [-4.30 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_LOW(-1.00)[riseup.net:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; RWL_MAILSPIKE_VERYGOOD(-0.20)[198.252.153.6:from]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; MISSING_XM_UA(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4XRRXp1bFxz476s X-Spamd-Bar: ---- On Sun, 2024-10-13 at 11:42 -0500, robert@rrbrussell.com wrote: > hdparm is the required program on both Linux and *BSD.=C2=A0 The procedur= e > is set drive security password and then issue Secure Erase. Hi, regarding brand new information from 2013 you shouldn't use hdparm for this task. "hdparm Warning: Do not attempt to issue a Secure Erase ATA command on a device connected through USB; see https://ata.wiki.kernel.org/index.php/ATA_Secure_Erase and this answer for [*] details." - https://wiki.archlinux.org/title/Securely_wipe_disk#hdparm The kernel.org link is obsolete, "This page was last modified on 22 July 2013, at 16:58." [*] https://web.archive.org/web/20180711170859/http://www.tomshardware.co.uk/an= swers/id-1984547/secure-erase-external-usb-hard-drive.html I get "The connection has timed out". Regards, Ralf