From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CF4B4221FCB for ; Tue, 14 Oct 2025 16:10:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760458205; cv=none; b=YCp2dFn2neCh+e80PFiaGiirdZc9VAi4fP79uXry+uvYduwLX6cDNHzeqUCgNx1xzgraSHvmneV5dFS6R5AW+qy6/dpLJkDCQc9+xZF9ep80IbxwkRPn3QdheGbIJ6/IBD32ZYJaBi0Dwx5Vy8gah0JmD21jpjcsBfUlznQS4wQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760458205; c=relaxed/simple; bh=3Sctr01iFgH3F48haP8GhUKpuP3hKXytOobelPIcaSI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=SBwphqBNkdI27/GXzRbirJynAUil9DEMxgxEJclX/xfMllZGFHGuxtC6nz/D4rpp0oUR6PmClyIGevcB8un2OQqIwHTq9BKiaZnSVftAF4sL9uHNL4EFXerYjIaL0mZ+ZC2sZXsxGlD1V3yd+OeyG0D3OXbU7Wa8NkokAg2+vE4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=C3vW4oZw; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="C3vW4oZw" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 628FCC4CEE7; Tue, 14 Oct 2025 16:10:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1760458205; bh=3Sctr01iFgH3F48haP8GhUKpuP3hKXytOobelPIcaSI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=C3vW4oZwiJTd2X8NuXgckGNY9sDCnC6EB2TsccmrypWCt6qpHbWcgR+K1HZJsPyqV 26EAz8sZRSZb0tfYtm3s9NdOFfjm/oQIZrFIrIRLY0CYynHI4UykAPTUdPGjkDFz7A h70w5eFd4tkIscggOIkO0YydW+YnKK4XBU7YboYGQei+R/j8LRPhc1607k053uRB1B IJKS6R4e4wuiz7+WbDErfxmt2Bs0IPBFKcmKyfl6mwRZgo0TNGxOnOQECPuDpXeSB2 9OOaSpMZCU8dMU9yo2osaAMllyTz/VgOgSfChXE3mk4I3eI2xfP2GCh+8199r0lnAP y3jckDMXg2/lA== Date: Tue, 14 Oct 2025 09:10:04 -0700 From: Kees Cook To: Theodore Ts'o Cc: Borislav Petkov , Konstantin Ryabitsev , Daniel Gomez , users@kernel.org, Luis Chamberlain , Chuck Lever , kdevops@lists.linux.dev Subject: Re: Forbidden requests for kernel.org/releases.json Message-ID: <202510140909.2CB85EF52@keescook> References: <20250410103037.GCZ_edzWEQSfxV880T@fat_crate.local> <20250411-talented-elegant-earthworm-e741ef@lemur> <20250415090144.GAZ_4geJqztHoDjnRM@fat_crate.local> <20251013131539.GBaOz7ezw1jp5ZCaiw@fat_crate.local> <20251013151955.GH354523@mit.edu> Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20251013151955.GH354523@mit.edu> On Mon, Oct 13, 2025 at 11:19:55AM -0400, Theodore Ts'o wrote: > Konstantin, > > I wonder to the AI bot protection versus CI tools that need to > periodicaly track git trees so we can do tests would be to set up a > read-only gitolite account? This could be using the ra.kernel.org, or > it could be a secondary server, since we only need read-only access. > > If each CI builder has their own ssh key, you'll be able to track if a > particular account is being too abusive in terms of load on the git server. Alternatively to SSH keys, would client-side TLS certs be lower complexity to implement? -- Kees Cook