From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2010-November/000479.html | 88 +++++++++++++++++++++++++ 1 file changed, 88 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2010-November/000479.html (limited to 'zarb-ml/mageia-sysadm/2010-November/000479.html') diff --git a/zarb-ml/mageia-sysadm/2010-November/000479.html b/zarb-ml/mageia-sysadm/2010-November/000479.html new file mode 100644 index 000000000..5cc4896e4 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-November/000479.html @@ -0,0 +1,88 @@ + + + + [Mageia-sysadm] Usernames, uids, and groups + + + + + + + + + +

[Mageia-sysadm] Usernames, uids, and groups

+ nicolas vigier + boklm at mars-attacks.org +
+ Wed Nov 10 15:38:32 CET 2010 +

+
+ +
On Wed, 10 Nov 2010, Buchan Milne wrote:
+
+> > But we already need need (restricted) shell access for mdvsys submit.
+> 
+> Why? In the original repsys model, a request to "build pkg foo rXXXX for 
+> release Y" was all that was required. While I agree it may be quicker to go 
+> with mdvsys/iurt etc. now, why should submission require shell access? AFAIK, 
+> other similar tools (koji, OBS) don't.
+
+Yes, mdvsys is only using ssh to submit the request (calling create-srpm
+with some arguments). We can maybe use something else than ssh to submit
+the request, if the setup on the servers and support in mdvsys can be
+done without too much work.
+
+What other protocol do you suggest for sending the build requests ?
+I see Koji is using SSL certificates or Kerberos for authentication.
+
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ -- cgit v1.2.1