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 17673 invoked from network); 18 Dec 2022 20:28:58 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 18 Dec 2022 20:28:58 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 9front; Sun Dec 18 15:27:00 -0500 2022 Message-ID: <2D6A5CBCE3E998E64FB930549528582D@felloff.net> Date: Sun, 18 Dec 2022 21:26:50 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: virtual structured enhancement GPU realtime manager Subject: Re: [9front] cwfs footgun Reply-To: 9front@9front.org Precedence: bulk > so i toggled twice here, and i got: > "none disabled" as the last line. the previous state doesnt matter in config mode. cwfs has not read your configuration when you type the commands in config mode. it records what you explicitely set. and the effecting state after ending the condifuration is what it said after you run the command. basically, as you hit end. it will read the config block and then "merge" whatever you told it in config mode with whatever it read in the config block and then write that back. the reason for this is that you tell it what the config block device is in config mode ;) so this means, if it says "none disabled" and you type "end" then: you'll have "nonone" in your config, and authenticating as none will not be allowed from a new network connection. > i guess that means that none access is disabled? yes. > my cwfs config block (first block at beginning of my cwfs cache > partition) doesn't mention any "nonone". i was referring to config mode. the "nonone" command was removed in from the runtime console PRECISELY because people get confused and ASSUME and GUESS that it would persist across reboots. it does not. > does this mean after a reboot none will be enabled? yes. -- cinap