[art] Putting actual credentials in URIs was an accident of history, let's repurpose those fields instead?

"Soni L." <fakedme+art@gmail.com> Fri, 24 February 2023 15:42 UTC

Return-Path: <fakedme+art@gmail.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6654C14F726 for <art@ietfa.amsl.com>; Fri, 24 Feb 2023 07:42:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fYI3bm7AjqXL for <art@ietfa.amsl.com>; Fri, 24 Feb 2023 07:42:40 -0800 (PST)
Received: from mail-oa1-x33.google.com (mail-oa1-x33.google.com [IPv6:2001:4860:4864:20::33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACD4DC14F721 for <art@ietf.org>; Fri, 24 Feb 2023 07:42:40 -0800 (PST)
Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-172b0ba97b0so1356968fac.4 for <art@ietf.org>; Fri, 24 Feb 2023 07:42:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:sender:from:to:cc:subject :date:message-id:reply-to; bh=rE7AzDU/Dcp+f5J7de4gxmgK5X+f/mjVgfpp5YUoYbs=; b=L1FXuTKmejMD/K4KWf+CQlMT3O9YnGY2boaVj/uEUaZHePTE/UJsJcZd8f8PEzY6dV YAS1k71Oqaqv11R+bGkCjXn73TcVMfR8/jjjFi6PQ1Ob450Y/NA66BR2AftiQO128IAs EYiCGKKQbFNEZZNeMMEX0r/s2rGTQY4DfGeyeHKAQdffSygPp8BVMfuWXUPVw1zjEkGh +QJn9n/NdQbf+A2g2j/0axRQ7+04PB4SDZ8hKDijbCXconvD7/Vk7tJCLc5jCirX42w0 3VS0EanpZj278AxVuqxWP3ES0D4NtUDP7o6wLQqQarAonHb6DYiMt/u5SzBdIJF78M44 07dA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=rE7AzDU/Dcp+f5J7de4gxmgK5X+f/mjVgfpp5YUoYbs=; b=1JvtqMOZukOHYdfO+DVDN3B/p8lVeWzYlmA7Jvf496w7U/9g913woFYmEJIiCAzlYK hd0YgPQvAjynlwtzWaNo2ZLy6vWzhiD5ALFPbj3mWrbgk/VmHTbHE/cE38rSU/1n1jmL uph/Spckbm7al0twLEBpWNr+4agpLjY0ExNoTdfn9yZ4cK2GC011j32pVcp/ibtLNsdD RMWpOErDThmrmoaXqQIezDMZeWNkH8KrKpqlF96csyvPPpcaDzFp5a2z7b34PxtgwkWG NfoEIdlTKutFfmmMuVU50zm6Y/UVBPpO8cNPv/khLaCxkDWiN60Rn5vYKrp4b8Ibre5u 0lMg==
X-Gm-Message-State: AO0yUKXSz9DTZ3JnD2O18ujkXgqgH7R0tbfaL45ccVmNCTQi6uRRvhCn DsyqnMlBUZo6zLlJu+HCKAiETAnBP/Y=
X-Google-Smtp-Source: AK7set/LeSM19tBpcMf15IgLLVcDrXGS3dPF3Q3A7MPXDsOwGSQz3wo1ktuAHO015/7ysnDYbZmJpA==
X-Received: by 2002:a05:6870:3045:b0:172:36ab:bd11 with SMTP id u5-20020a056870304500b0017236abbd11mr6749306oau.4.1677253359895; Fri, 24 Feb 2023 07:42:39 -0800 (PST)
Received: from ?IPV6:2804:431:cfcc:774::536f:6e69? ([2804:431:cfcc:774::536f:6e69]) by smtp.googlemail.com with ESMTPSA id du23-20020a0568703a1700b0016a310dc4a9sm3990157oab.9.2023.02.24.07.42.38 for <art@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Feb 2023 07:42:39 -0800 (PST)
Sender: "Soni L." <fakedme@gmail.com>
Message-ID: <9568aaa5-21f3-a40c-92ed-57d8b217813f@gmail.com>
Date: Fri, 24 Feb 2023 12:42:37 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.0
Content-Language: en-US
To: art@ietf.org
From: "Soni L." <fakedme+art@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/Wjh-0sPAcyqkRoKBHmfHmCL8BXY>
Subject: [art] Putting actual credentials in URIs was an accident of history, let's repurpose those fields instead?
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2023 15:42:45 -0000

So how bad of an idea would it be to repurpose "username" and "password" 
in URIs for all sorts of stuff? E.g. 
https://soniex2.tumblr.com/post/705832532473724928/so-heres-our-plan-we-wanna-have-web-git-urls

---

so here’s our plan: we wanna have web+git URLs, and it should look like 
web+git://username:namespace@hostname/path

so for example, on something like github, username = the username of the 
owner of the repo, namespace = always empty since github doesn’t support 
namespaces, hostname = github.com, path = repo name.

on something like bitbucket, which does support namespaces, the 
namespace can be non-empty.

on something more selfhosted, the username and namespace could be 
omitted entirely.

e.g. we could have web+git://fedi-to@github.com/fedi-to.github.io

e.g. we could have web+git://soniex2.autistic.space/dfu

how cursed is this?

-- 
1st person: we/us
2nd person: it/its
3rd person: she/they