From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 11 11:13:25 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 436A4106566C for ; Sat, 11 Sep 2010 11:13:25 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 086668FC13 for ; Sat, 11 Sep 2010 11:13:24 +0000 (UTC) Received: by iwn34 with SMTP id 34so3590632iwn.13 for ; Sat, 11 Sep 2010 04:13:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=hhcQf0mJAcPYyRKYdh2e9qKYXfddlCAVDs4wTz6uWig=; b=Zsss9gtMMe4Re3wy1YRYyHE6pQooUIEr0n2uHey5wUaunGAKO1x0MaoiJEBQJ56bN+ e9srpZBKGF7Ggva+yEmWflF5nzHC0yhf7zEVr/tR1ljW40mkXYTzq6GtsRhSEoHtm970 4hjMAHQw4RIzW2FpO2Gst0jvjvyugPV04gFHU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=X0c9rlYvatiYaU3SxAODWyHR9aRpSoP14+VMB7GadT1UWF6/eVaRWAcaV1tohkzDuz Z6IlAtND1w/P+/Mmddl2P11ChcG4kNn2VcWApHw4C+7hHMlM4Svm+eLkqqPRYO9P8eHd oJYNUec9eSzt/kIeSbqpgsHM43mk7LnfW/3s8= MIME-Version: 1.0 Received: by 10.231.16.75 with SMTP id n11mr2312197iba.49.1284203601316; Sat, 11 Sep 2010 04:13:21 -0700 (PDT) Received: by 10.231.184.223 with HTTP; Sat, 11 Sep 2010 04:13:21 -0700 (PDT) In-Reply-To: References: <4C8AE7A2.1090802@DataIX.net> <4C8AE9CB.9070008@DataIX.net> <20100911090739.GA3797@straylight.ringlet.net> <4C8B5FAB.1010502@DataIX.net> Date: Sat, 11 Sep 2010 07:13:21 -0400 Message-ID: From: Aryeh Friedman To: jhell Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: How to disallow logout X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Sep 2010 11:13:25 -0000 On Sat, Sep 11, 2010 at 7:07 AM, Aryeh Friedman wrote: >> >> Firstly this just sounds like a case where the admin needs to provide a >> equally sound and safe way of making sure everything is cleaned up on >> logout and is offering a global way of doing it so the developer will >> not forget. > > In this case the admin and developer are the same person... namely at > the clients request I am the only person allowed to work on the > project and I just want to make it so I can't accidently do something > like control-d or something like that and leave a plain text version > of a project that has a very strict NDA laying around (liquidated > damages of $250k)... the scenrio is we a are a team (each one of us is > in diff city) of freelance CS people and all use the same server for > all our development to make cooperation possible when needed (not in > this case) have centralized backups, etc. and as mentioned on this one > project the client has forced me to sign a NDA saying I can't even > show the code to the other team members without the client's > permission and thus am storing the repo using security/fuse-encfs, but > since the version control system (devel/aegis) requires creating a > development directory that is not encrypted I want to force/remind > myself to checkin what ever I was working into the encrypted repo when > I go "home" (it is a home office ;-)) at night or out to lunch > Forgot to mention all these percautions are to make the client comfortable with letting me take advanatage of the server's development enviroment instead of spending almost a week configuring the same env on my desktop machine... namely I trust the other team members to not look at the code even if it was not encrypted.