How to disallow logout

Aryeh Friedman aryeh.friedman at gmail.com
Sat Sep 11 15:18:59 UTC 2010


I would prefer to have the plain text around after a power failure
because it could be several days of work and as I said the only reason
for all this is to make the client comfortable and not that I do not
trust the team (I do trust them)

On Sat, Sep 11, 2010 at 11:10 AM, Oliver Fromme <olli at lurza.secnetix.de> wrote:
> Aryeh Friedman wrote:
>  > 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
>
> If it's just a reminder to yourself, then I would simply
> remove the keybinding for ^D (or bind it to something else;
> the details depend on your login shell) and alias "exit"
> and "logout" to a script that checks the working directory
> of your version control system.  If things have been checked
> in correctly, it logs you out, otherwise it prints a message
> and terminates, throwing you back to the shell prompt.
>
> Additionally, you could put the checked-out files on a
> geli-encrypted device and/or on a memory file system.  That
> will make sure that there ist no unencrypted stuff left
> behind after a power-failure or crash.
>
> Best regards
>   Oliver
>
> --
> Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
> Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
> secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
> chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
>
> FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd
>
> "Python is an experiment in how much freedom programmers need.
> Too much freedom and nobody can read another's code; too little
> and expressiveness is endangered."
>        -- Guido van Rossum
>


More information about the freebsd-hackers mailing list