From nobody Wed Mar 16 08:35:02 2022 X-Original-To: freebsd-current@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 36B2C1A24C99 for ; Wed, 16 Mar 2022 08:35:47 +0000 (UTC) (envelope-from yasu@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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KJNrz0zRsz3HZv; Wed, 16 Mar 2022 08:35:47 +0000 (UTC) (envelope-from yasu@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1647419747; 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=HAWt2bYRbWvkJ51cc5zZITJpEFAW1anyJQRyl5DkDoE=; b=FKoM9LfUBMkhlc+wIBgSeZYnh60S4PAdYWwI7twmCJxAFwAKuHW80ZVJtrontLC75rTazb 7aTakUlA0znakVLlUcS71ragKr8XFhOvcoH6q2r5PpS9nlf2Luw2SaLERPhhkKZgekzsGE 5exP/AadTMEa2FwrCRGwX0QKycn2zH/D/inzRWgkTyL4AQkjdG6FOVPoaQj63Bq/rql5b+ vsmcAd/FWoK7oYLspUuD/SL7rfgnAbHWKjhlmgfgR0p03NFI4aEhszdVCLKc1u7mY9M1UX CwZtTZcadaPwj9HdjV8GXB9aNDBAuDFMiclzd3C2MAB84RWO7jkXN7V94OOC2A== Received: from localhost (unknown [IPv6:240b:11:220:fe00:8db2:139b:2f84:dcc6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: yasu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 6B39F28A5F; Wed, 16 Mar 2022 08:35:46 +0000 (UTC) (envelope-from yasu@FreeBSD.org) Date: Wed, 16 Mar 2022 17:35:02 +0900 (JST) Message-Id: <20220316.173502.1588712462049603767.yasu@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: getnetgrent(3) fails to parse long netgroup entry if it is stored in NIS From: Yasuhiro Kimura In-Reply-To: References: <20220316.014814.1921859297745365117.yasu@FreeBSD.org> X-Mailer: Mew version 6.8 on Emacs 29.0.50 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1647419747; 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=HAWt2bYRbWvkJ51cc5zZITJpEFAW1anyJQRyl5DkDoE=; b=l2PKY5wQeJe2zbIrjc6SPIafkuBFWqcRjt1mTGLnGXSEiG6hJh9iXJ/9qy5ldNKRQfrbzV Eqm67acPUXOSMjK60687iU0vmtxmTiTCo7v4jWB9BAl90iBUIBM/Qhq6lrRizgUGm1jdBW w13gdm3PPfW5Qsglb/kh0FLpuFLlbPa/4Tdtv06GsZLMPJZq4Upwd4CKwU2OvsNnMrlEJg NZ+q/Fdou7dqseu10gy7mctOV0E+Yx6tHfEdHpbdx9i2KrVlHUMDa9kRorGfLZB6TeSx6T pu8K3/9Jx6kAm3fM3b/VdlPuO7HHBppBg3J/HtV/zFhQfwONpd4NOdnP4QYSWw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1647419747; a=rsa-sha256; cv=none; b=xkz8g3Y5of/zeZC6NDndiZFZMqc7cjNbhz5HCREO/gHnyLB8FKJLrlsJbnVc5RlLbaZKBZ zRfSttM8TbqwhhbuBlRaBbkZP4Lq0mGNKTDoUUwujZhicRUn0Y8aF4oPguDKI+LuL45Hie ppK3zhGtSEfKB5Juz45Xz62xh5jXyC+Y+svJmXtt6u18xQKjWOcnCeWRTbPkvFbUb691R3 ZRDlIzSgMcCV53mu3r27VdTgo17PVPvtKlIdg6XZf5iSr3BJXCEKRZ82VDUiW/u6TQJz2e dNuK8pWD5NREjuKO+J76iKwBZoz+j9fnv68qqfVn4Q7JSHKiDiaRlqg8D6DRKg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N From: Rick Macklem Subject: Re: getnetgrent(3) fails to parse long netgroup entry if it is stored in NIS Date: Tue, 15 Mar 2022 23:15:30 +0000 > "man 5 netgroup" notes that a netgroup line is limited to > 1024bytes. > > Are you sure you haven't just exceeded this limit? Thanks for pointing out. It's exactly the cause of my problem. I didn't know there is such limit. From: Rick Macklem Subject: Re: getnetgrent(3) fails to parse long netgroup entry if it is stored in NIS Date: Wed, 16 Mar 2022 05:12:49 +0000 > Oh, and you can have netgroups in netgroups, so you can > do something like... > > net0 net1,net2 > net1 (host1,,),(host2,,) > net2 (host3,,),(host4,,) > > then net0 has all 4 hosts in it. > > I think you need to break the large netgroup up into sub netgroups > where each one is <= 1024 bytes long. I fixed the problem in this way. Thank you so much! --- Yasuhiro Kimura