From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mail.toke.dk (Postfix) with ESMTPS id 1AFF37CB466 for ; Thu, 14 Jan 2021 13:39:42 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key) header.d=kerneis.info header.i=@kerneis.info header.b=yXFyEolf; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b=KEED3g29 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B6CD55C01EC for ; Thu, 14 Jan 2021 07:39:20 -0500 (EST) Received: from imap3 ([10.202.2.53]) by compute6.internal (MEProxy); Thu, 14 Jan 2021 07:39:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kerneis.info; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=YFbjdWWJuOY/HbrE+0IXk8TF6HveFNE VQPcpMY4nPYE=; b=yXFyEolfABCc5pjfdZQU7bpV42uUXtCGN28x6j5yAgzd/Lx jsPWsJ6a7sHl2ChphZ58h7D1uwp0m4izShDQqNSTYq8tcpWH6KviOAGWHmOOprby u6o9/cKTIDc/Sf1TAG4gnSfHlPBP/+NbZP7QNs/Z4bmG7a64FbdrKnEj4zpyDkul tmCxcTsylcz9l3/P+eQcWQ/TMTfMSnpNnPcWBjUGOBmJXlwj23o6iJnCe+2TTefQ plE3RsDxLgypkbBWfFYaBGYGzsD9aD7c4W76YIvmNvxek+k4flVFejboZnf1N4af vlSbG8xzWygd8XZQIEEskSM0bzKin+0kIytPzuQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=YFbjdW WJuOY/HbrE+0IXk8TF6HveFNEVQPcpMY4nPYE=; b=KEED3g292llMyA8dQUFhbw K6WvfdLIyeaunaKuLeD50fZIlmeX75mvmvVXSUDGl5IW5lgwSf8WXknGhuigN/Ua 7ZHSIHcMIaB1EBmqd3amc6Gq5HT27IZoYp5j4Lql9zgn7k3ipe/FW9FlhluBzaKG 9JoOGo1k59gYebT5IUcihYL88HO3+hMCM4XwZ72mbY0MIaUVlvsEi45ZLYatmKtM 8jUPQcTLjlBffWMA3m6zfuXP68BuC00h6TpgwOrZT0iDo3m49eaSMvop75zNYWYJ ODGnp49eWGKRkYUmEYU7iosImqYkeLzOyYHRtHk73daQ+pNP25IibYKgjKmLnlQA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrtddtgdduiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdfirggsrhhivghlucfmvghrnhgvihhsfdcuoehgrggsrhhi vghlsehkvghrnhgvihhsrdhinhhfoheqnecuggftrfgrthhtvghrnhepheegudejfefhgf dujeeiudevtdevgeelueegheffleelheefueduveevkeeluedvnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghgrsghrihgvlheskhgvrhhnvg hishdrihhnfhho X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2993F4E00C2; Thu, 14 Jan 2021 07:39:20 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-45-g4839256-fm-20210104.001-g48392560 Mime-Version: 1.0 Message-Id: In-Reply-To: <87r1mnelus.wl-jch@irif.fr> References: <394af17f-0f68-2c37-e9db-043433fd2bb7@stroeder.com> <87r1mnelus.wl-jch@irif.fr> Date: Thu, 14 Jan 2021 13:38:59 +0100 From: "Gabriel Kerneis" To: galene@lists.galene.org Content-Type: text/plain Message-ID-Hash: Q2C3VRLYPSBD5RKPSWOBA7LQEHMKHAJ4 X-Message-ID-Hash: Q2C3VRLYPSBD5RKPSWOBA7LQEHMKHAJ4 X-MailFrom: gabriel@kerneis.info X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: autolock always locks List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: On Thu, 14 Jan 2021, at 13:36, Juliusz Chroboczek wrote: > > "autolock": true, > > > After entering the session as "msop", I verify that option menu shows > > ops right. > > > But I cannot enter as another user "foo" (without password). > > The op needs to manually unlock the group by saying "/unlock". Think of > a job interview: the interviewers all have op privileges, they join the > locked group, and when they decide they're ready, they unlock the group > and invite the candidate to join. > > As they start chatting with the candidate, they might forget to lock the > group again. If they leave the group unlocked, there might be information > that is confidential under European law in the chat; the autolock feature > ensures that a third party cannot access the chat after the interviewers > have left. Are non-ops automatically kicked out when the last op leaves (or when the group is locked again with /lock)? -- Gabriel