From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24663 invoked from network); 6 Jan 2023 05:45:13 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 6 Jan 2023 05:45:13 -0000 Received: from gaff.inri.net ([168.235.71.243]) by 9front; Fri Jan 6 00:43:52 -0500 2023 Received: from smtpclient.apple ([104.59.85.219]) by gaff; Fri Jan 6 00:43:51 -0500 2023 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Stanley Lieber Mime-Version: 1.0 (1.0) Message-Id: <0AA81591-7254-4486-819A-304695EDF52E@stanleylieber.com> References: In-Reply-To: To: 9front@9front.org Date: Fri, 6 Jan 2023 00:43:40 -0500 X-Mailer: iPhone Mail (20C65) List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: RESTful pipelining SSL over ACPI core metadata Subject: Re: [9front] cwfs footgun Reply-To: 9front@9front.org Precedence: bulk On Jan 6, 2023, at 12:22 AM, hiro <23hiro@gmail.com> wrote: >=20 > =EF=BB=BFbtw, if you just echo into cwfs.cmd, you will never even see any > feedback e.g. "auth enabled" message. >=20 > the image suggests otherwise. i guess the only real way to know whether or not you were safe is to have yo= ur files exposed by failing to enable auth. at least then you=E2=80=99re sur= e. sl