Coda File System

Re: Real life lessons of disconnected mode

From: <>
Date: Sat, 1 Jul 2006 16:15:14 +0200

forgot to mention one thing about disconnected mode.

It did not feel right when I had to create a fake token just to access
my own cached files. I do shut down the computer in opposite to hybernation,
and Venus forgets my old tokens (which is all right).

I do not see a reason why a user is forced into forging a token
to access files. Either he/she should be denied access unless a valid token
is presented (that would mean no disconnected mode!),
or he/she should be allowed to access cached files which were allowed once
during a connected session, independently of the presence of the token.

No security is gained otherwise (you generate a fake token easily)
but an annoyance is created.

I can not log in to my environment directly, as it depends on things under
my $HOME, so I am forced to login in two steps, first "failsafe" or on
an alphanumeric console, forge a token, then log in as usual.
In connected mode I am forced into doing clog the same two-step way.

It would be exactly as secure but a lot more convenient to be able to
always login as usual if your homedir is cached and then clog if you
have the connectivity to do it.

Note, I am very happy with Coda, nothing else comes near its features,
but such small changes can make a lot of difference in the impression,
especially for newcomers.

Received on 2006-07-01 10:16:02