From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id C11B724B86 for ; Sun, 10 Nov 2024 14:59:58 +0100 (CET) Received: from dane.soverin.net ([185.233.34.30]) by 9front; Sun Nov 10 08:57:36 -0500 2024 Received: from smtp.soverin.net (c04smtp-lb01.int.sover.in [10.10.4.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by dane.soverin.net (Postfix) with ESMTPS id 4XmZ4Y6mdqz2xKs; Sun, 10 Nov 2024 13:57:33 +0000 (UTC) Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.100]) by soverin.net (Postfix) with ESMTPSA id 4XmZ4Y1hcPzHS; Sun, 10 Nov 2024 13:57:33 +0000 (UTC) Authentication-Results: smtp.soverin.net; dkim=pass (2048-bit key; unprotected) header.d=pheist.org header.i=@pheist.org header.a=rsa-sha256 header.s=soverin1 header.b=U6mflQEn; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pheist.org; s=soverin1; t=1731247053; 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; bh=D/I07998E6F8zRTyYeo7YiJtAAbFQeXLwkR0MA+Vdp0=; b=U6mflQEnXml2FflW/Y3+3JIrFyRXd7cJaj48xZSMoXPV/KtccXsYn4lAKLoWNOqwLHfirH yvnm6TnELPGyArVz+Pl5cis8qkOFH8ZSPeTqDqDGDWqpB0vKUqz31Wyl6DNcn4lvQNXZ+x 4ut/XkrBeO20+CURFz68bPMrzAAzpkoaZQcZ8g/peN3cP1daUQz3IdtxecM6OdyEos4X0c wCftQPe1cGLEv0XUCSCY+GsIh7Ob9jz1coND9Ce8+kdDJ9CsVLYiLvUGx0tARQLs2/m9Ix ZZIzPxeoWM5iquaKqcnwEV/PLNsVnB2BSZ965/9y78WhF4YiZ85JS3WquJs/QQ== Message-ID: To: 9front@9front.org Date: Sun, 10 Nov 2024 14:56:52 +0100 From: theinicke@pheist.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Spampanel-Class: ham Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: generic singleton GPU module Subject: Re: [9front] Problem with authentication on file server Reply-To: 9front@9front.org Precedence: bulk Hi, not really an expert, but usually altering /lib/ndb/local might require t= o execute auth/wrkey again, depending on what has changed... Also maybe you want to history -D /lib/ndb/local to see what you changed exactly? And finally you could remove /adm/keys and recreate them, ex. using auth/changeuser (if anything else fails and no one has a better idea :) Good luck, Tobias Heinicke Quoth =C3=96zg=C3=BCr Kesim : > Hi, >=20 > I have a 9front file+cpu+auth server on my desk that I occasionally use > for some experiments. About a week ago I did a sysupdate on the machin= e > and some changes to ndb/local (IIRC, only adding an authdom to the > ipnet). Now connection to it via drawterm (the 9front version) fails, > with the following complaint: >=20 > drawterm: can't authenticate: auth_proxy rpc: p9any client ask for keys= : unable to find common key >=20 > Altering ndb/local didn't help. Before I dig deeper and try to extract > more information from the cpu server -- does anybody have an idea and a > hint where I should look? >=20 > Cheers, > oec