Not to use Microsoft Mail. Thanks for that! I was really worried about having to find a bad reason to not use it, but you gave me a good one.

Absolutely nothing bad can come of this.

So "Personal Accounts" will be cordoned off. That don't mean much. Will the Facebook /databases/ be cordoned off? If not, it just means you won't be able to access personal accounts from at work, but Facebook will still link everything in the background. Won't it be so fun to have Facebook automagically add all your coworkers to prospective friends on your personal account. And what if you change companies? Do those accounts exist in a single "work facebook" database? or does each corporate account have its own isolated database?

Way to many questions that I doubt will be answered when this is launched, or even afterwords.

(I don't facebook, don't have one, don't want one, and would be pissed if my employer decided to jump on this bandwagon.)

And, while I forgot about it at first, TrueCrypt should be encrypting the hibernation file if you are using System Encryption (on Windows) and the hibernation file is stored on the system drive (generally is). So again, this appears as it would be even more limiting for finding keys in a file, since someone who is "security conscious" most likely has their system drive encrypted, and is making sure hibernation file is on it.

As a result, you would actually be further ahead to hibernate your computer for your little bathroom break than you would be to sleep it (Since sleep leaves everything in RAM).

*I say should because there are various little nuances to that, OS, hibernation file placement, TrueCrypt Version, etc that may result in your key being written in a non-encrypted state.

Security conscious people never hibernate or sleep a machine.

FTFY.

Or at least they don't do it leaving their encrypted containers in an accessible state. You can sleep and hibernate all you want, so long as you dismount your containers prior to doing so, and ensure the keys are wiped from RAM.

I'm assuming the request can be as specific as one call/SMS to basically a data dump of a cell tower (Basically everything about every phone within range of a certain tower.)

So, optimistically we're talking between 1.3 Million (low end) and 1.3 Billion (high end [assuming 1,000 devices within range of a given tower or group of towers for triangulation]) data points of information. Everything from who someone was talking to, when, to text message conversations, to where was this customer and who may have been with them in the area (via tower dump of one or multiple neighbor towers to allow triangulation)?

(The tower information dump was not mentioned within this article, but I recall reading about that practice recently, and I believe it was another article on /.)

Little scary isn't it?

I think one way you could make KeePass multiuser is the following setup. Keepass itself isn't, but by utilizing the existing groups of AD/*nix I think you could actually have an efficient way of doing this.

Create Keepass (v2.x) databases, one per group that you have. All the databases can share a common password if you want (won't affect security). When you create them, ensure all have a keyfile as well as a password. I would suggest naming them something like : Database-General, Keyfile-General; Database-Local Admins, Keyfile-Local Admins; Databasse-Group C, Keyfile-Group C. Distribute the common password to those individuals who need access to the shared passwords.

Simply set the read permissions on the various key files to the respective groups that these individuals should be a member of. (Alternative would be just set the read permissions on the databases as well, but if you have local keyfiles you can post the databases to a intranet website, while spreading the access key files around the file system into default drives/directories.

This means you will have multiple databases, but it shouldn't be unmanageable unless you use uber-fine granularity (3 people need one password, but are three different groups and nobody else needs that password.)

One benefit to keepass as well is in certain situations you can create a config file that will over-ride user preferences. Read the help file, I've never had a need to configure it but I think with AD policy you could make use of it.

I second this one. In my safety deposit box, I have some letters prepared for certain events from my grandmother she wrote before she passed. Marriage, First Child, Etc. They're clearly labeled to be opened at certain events. Do the same, key events in their lives. Granted you don't want to go overboard with them (IE every special event), but perhaps for the next few years, you can pre-write Birthday cards through X age for each, Driver Licenses, Graduation, the same list as above.

It'll be a way for her to pass on her knowledge and life experience in a timely manner to them, and be able to still participate in a bit of their raising long after she's gone.

I'll also weigh in on a comment above. Do document, don't over-document. Unless you're going to be editing the footage down to some reasonable quantity, it'll mostly be for naught. Remember, every minute recorded takes a minute to watch. If you have two hundred hours of footage, most aren't going to want to sit through it unless looking for something. Diaries, journals, are excellent in this regard. They can be read much faster than written, can be picked up and put down for most with little need to go back and re-read the last half an hours worth to get back in your mind where you were. That, and if she's going through treatments during these final days, her personal image is going to start to degrade. It's going to be hard to watch it personally, but do you want your children to watch the entire thing? Probably not. Books let you maintain your own image of her, even when she looks her worst. Of course you will want key things recorded and that's OK, but most want to be remembered at or near their best, not arguably their worst.

Damn, you beat me to it. When I watched that episode, I was thinking that somehow the consoles changed shape (such as micro-bladders beneath the surface to give a 'raised' surface) but this definitely makes a lot more sense. Yet again, Star Trek is leading the way in predicting things.

Now all they have to do is get the touch screen to interpret the difference between 'feeling' the screen to locate the button, and the intent to press the touchscreen button. And get it to do it well, and consistently. (Yes, I know most touch pads have this feature to prevent 'palming' them, but how reliable would they be in this scenario?

In addition, the TrueCrypt user community lately is getting the shaft from the "TrueCrypt Foundation".

Case in point, if you visit their forums, starting about 6 months ago, around the time of release of v6, the forum administrators now delete anything "critical" of TrueCrypt. Basically, your only allowed to discuss the positives of the software, or problems with the intended operation of it. Any "bugs" or "weaknesses" mentioned result in having the thread either locked, more than likely deleted, and if you push an issue, open a second thread on a 'deleted thread' your likely to have your account locked.

5.1a was the last version released before this new policy of "only positives". Not to mention that the forums are already so heavily locked down (No public email addresses to register accounts, no private messages on the board, no threads that are not 'on topic'). Some of us tried (semi-successfully) to have frequent contributors meet over on Wilder's Security forums. (http://www.wilderssecurity.com/) Difficult though since they started deleting our postings since they weren't on topic, and private messages are impossible.

Sadly, as a result of this, I used to heavily endorse TrueCrypt, but I can no longer stand behind them until they let the community get re-involved, for the good and the bad.

I just canceled my account, after individually deleting each section, and replacing undeletable information with 'garbage' data.

One thing I did notice, I recently changed my password (On 17JAN09) and was not prompted to change my password upon login. It makes me wonder when this breach happened, and if anyone will be prompted to change their passwords, or if I had already changed my password after the breach, but prior to the official notification.

Darnit.. My bad.

I don't know how I got to that article then since I'm usually a bit better screening my news... *Thwaps head.

Ah. Now I know. Bad title + link from an article from today (was about Win 7).... There should be rules against putting 'Breaking' in a title that is static and doesn't disappear after time.

Time to go crawl back in my hole.

Three of four sub-cables connecting Asia-North America have been cut.

This is getting a little crazy, and pardon the tinfoil hat that I'm wearing, how many 'undamaged' cables does this leave?

I think this is really starting to become hard to blame on 'coincidence.'

http://blogs.zdnet.com/gadgetreviews/?p=669

New tag system apparently. Mouse over the various tags and you'll see there are three tag types--Top, System, and Type. I'm presuming that since there are more stories submitted than anything, the Story tag will be on almost every entry.