From nobody Sat Aug 3 15:03:38 2024 X-Original-To: freebsd-hackers@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 4WbmDl6QsPz5SZbv for ; Sat, 03 Aug 2024 15:03:51 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f170.google.com (mail-oi1-f170.google.com [209.85.167.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WbmDl4g1dz4NrD for ; Sat, 3 Aug 2024 15:03:51 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oi1-f170.google.com with SMTP id 5614622812f47-3db1d0fca58so5716965b6e.3 for ; Sat, 03 Aug 2024 08:03:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722697430; x=1723302230; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=2y0SlcuGw9006ZKTM/jdrrrOFK3c8HrAxRSA0U3qAyo=; b=iMCUVPIJoFOi22sO+rCSPI8EXHwgGIyPPElbQFHmqRC0dNzuSZTBC36bMTv8srYjvi Ru6GLLmV2GzAmPUpQFHn8H44YMfIRJlh56THIcrEbON9ZwjFs4OGQHXceGihyLUKd8Kl AgMN++rgkdmY5lzsdZfMvXGKn058ob+k14x2+N79apuQ1UgVn6+ifyhMFnQtxLhO6jKQ D7y83s/S1rxYjSKzyZKKZTa8EBBYYsFU4HrD3LVIH3UimikVz78jwhS0pi6akJhgKvEV Jfm05UCu+JcBK4l97GlIWR0c2rYo2Y95d6Wf0ZMsQLs93serKe7+eQ93F3SY2snbC2Mt qmiQ== X-Gm-Message-State: AOJu0YwkQM/81lrtRlufyh7cWVK7V+3HZNOVyMMbj01LiDdvt40fIDwC /zWbcAQAKpaJ+Kl/jBXmK51Rs4IrBRlnG3vTWFAEOPr6GWiCcgcRxe6Z6pvlgEVAa+AysE6PZB+ xgu3mz8/i6+9Dec/awvcfMDotLWtAsrNA X-Google-Smtp-Source: AGHT+IH8bjixZSHbjOsqB1ybyhl7Pwx28SwF0ZRjvNARVentDEosJTkvJZIYiIF1IedMkdFVPea/h7WxLv+soV0oJwo= X-Received: by 2002:a05:6808:130d:b0:3d5:5c77:fc2f with SMTP id 5614622812f47-3db55840a42mr6614835b6e.48.1722697430236; Sat, 03 Aug 2024 08:03:50 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 References: <202408030413.4734D5gd042998@donotpassgo.dyslexicfish.net> In-Reply-To: <202408030413.4734D5gd042998@donotpassgo.dyslexicfish.net> From: Alan Somers Date: Sat, 3 Aug 2024 09:03:38 -0600 Message-ID: Subject: Re: RFC: ACLs on fusefs To: Jamie Landeg-Jones Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Queue-Id: 4WbmDl4g1dz4NrD On Fri, Aug 2, 2024 at 10:13=E2=80=AFPM Jamie Landeg-Jones wrote: > > Alan Somers wrote: > > > TLDR; > > how useful would it be if fusefs(4) could support ACLs? > > I, personally, don't use ACLs generally, so have not missed them on > fusefs. > > However, I do make extensive use of XATTRs, so those are what I've > really missed. > > I didn't know xatrs were now supported - is that a new thing, or maybe > the client I use (borgs sshfs implementation) needs to be updated? > > Cheers, Jamie Our fusefs has supported xattrs for a long time. But the specific fuse file system needs support too. Looking right now, I don't see any support in sysutils/fusefs-sshfs .