Oracle Open World is Next Week!

I can't believe another year has passed - Oracle Open World is just next week. What makes this extra exciting? Attendees will get their first official peek at the final Oracle Solaris 11 release.  Both Larry Ellison (Sunday) and John Fowler (Tuesday) will be talking about it, as well as 15 sessions and meet the experts Monday through Friday.

Are you planning to attend?

Grace Hopper Conference is just around the corner!

I can't believe the Grace Hopper Celebration of Women in Computing is coming up in November! So soon! Oracle is a silver sponsor of the conference this year, and there are several women from Oracle that are presenting!

Again this year, I'm on the Communities Committee, but this year I'm co-chair! We make sure that major sessions are both blogged and have notes taken, encourage people to tweet, blog, and share on facebook.

I'll also be presenting "Security Attacks, Countermeasures and Protecting Yourself Online!" with Teri Oda, Radia Perlman, Satwant Kaur, and Lindsey Wegrzyn. We've only got a half and hour, so it'll be hard to pack it all in, but I know we'll manage. Better start working on our slides... :-)

Are you coming to the conference? Willing to blog or take notes?

This post syndicated from Thoughts on security, beer, theater and biking!

Palo Alto Players: Nunsense with a Twist!

This weekend, we went to go see Palo Alto Players' production of Nunsense with a Twist. There are quite a few versions of Nunsense out there, but this was the first one I've seen. The twist, in this case, was that Mother Superior (Sister Mary Regina) was played by Chris Blake... and Chris is not short for Christina. :-)

The basic premise is the nuns are short on cash for a very important project and they are doing a fund raiser, which explains why they are all on stage and singing. Hilarity, of course, ensues, as the show goes on and things just keep going wrong.

What I loved most about this production is that there was no mention or issue made of the fact that Mother Superior was being played by a man... Mr. Blake wore the same shoes as the rest of the ladies and the same habit. They didn't tart him up nor did Mr. Blake act like a man in drag. He was, quite simply, just Mother Superior.

Okay, not "just" - Mr. Blake brought wonderful physical comedy to the show, peppered in his priceless expressions throughout, and even sang wonderfully.

All five cast members were a joy to watch and brought something unique to the production, particularly Charlotte Jacobs as Sister Robert Anne, who really shined in "Growing up Catholic" and "I Just Want to Be a Star".

The show also featured great performances from Juanita Harris (Sister Mary Hubert), Jennifer Martinelli (Sister Mary Amnesia) and Jennifer Gregoire (Sister Mary Leo, the ballerina nun).

Of course, these actors did not direct themselves, nor choreograph their own dances! The wonderful staging and delightful dance numbers deserve kudos as well! Mark Drumm directed and Alexandria Kaprielian choreographed.

I loved that the band was behind the performers, as this theater, like so many poorly designed theaters in the bay area, has no pit for the orchestra. Even behind them, none of the cast struggled with tempo or cut-offs. Definitely a well-oiled machine, kudos to band director Matthew Mattei.

Excellent lighting, of course, as Ed Hunter was behind lighting design, as he is for many shows that I've seen, performed in, or merely heard great things about. (When Mr. Hunter is not lighting a show, he may be playing cello in the orchestra. Definitely a love of theater!)

My only complaint would be about the slow start to the show, which had some awkward audience interaction at the top. I believe they were delaying due to late comers for the show, as parking was particularly difficult that night. Once the show actually started, with Sister Robert Anne welcoming us all to the theater, it was a delight.

One other small nit: On the back page of the program, along with the donation envelopes, there was a bizarre lack of apostrophes. For example, they have a "Producers Circle" level of donors. Instead of either "Producer's Circle" or "Producers' Circle" (depending on how many producers own the circle). Hopefully they'll get that cleaned up for the next production. Maybe I've just been reading Cake Wrecks for too long ;-)

This post is syndicated from Thoughts on security, beer, theater and biking!

Mary Ann Davidson on Security Auditors

Mary Ann Davidson, Chief Security Officer at Oracle, has just published an outstanding article, Those Who Can't Do, Audit, on companies that are now offering static code analysis as a service and why Oracle won't be turning over any of our code to them. Here at Oracle, security is a core part of every product.

While I do work in the Oracle Solaris Security team, we work on software that are typically seen as performing a security based services. For example, I work on the Oracle Solaris Cryptographic Framework - we provide hardware optimized cryptographic algorithms to applications and the rest of the operating system. A pretty standard security function. But, secure coding standards, in-house static analysis, and security considerations need to be a part of the development of the entire operating system.

I think Ms. Davidson said it best: "Oracle cannot – does not – outsource security."

This post is syndicated from Thoughts on security, beer, theater and biking!

Bugs in my oatmeal

I made a bowl of oatmeal this morning, threw some fresh black berries on it, and was about to pour milk on top, which I noticed some movement out of the corner of my eye in the clear plastic container we keep the oatmeal in... at first, I thought it was an ant, and wasn't too creeped out. Then I noticed more. I remember getting these things in our flour when I was a kid, though our flour wasn't in an airtight container. All the same, I couldn't eat the oatmeal I had just made (though I did salvage the black berries).

I'm going to pretend that the bugs (and larvae) weren't in there yesterday when I did eat that oatmeal.

Guess we get to clean out our pantry tonight! Ah, so nice to be back from vacation.... ICK!

This post is syndicated from Thoughts on security, beer, theater and biking!

USENIX: Applied Cryptography, Refereed Papers

Differential Privacy Under Fire
Andreas Haeberlen, Benjamin C. Pierce, and Arjun Narayan, University of Pennsylvania.

There is a lot of data out there that is very important that we try to protect. For example, Netflix knows what movies you watch. Users rate movies in Netflix so that Netflix can make recommendations, but they don't necessarily want to share that information with the rest of the world. Simply replacing people's real names with pseudonyms is not enough, because if people know enough about you, then they will still be able to identify you from the available data and learn even more about you.

Even with protections, people can take advantage of timing attacks where they know the data must be in there, just based on how long the system took to reply to the query.

So, how can we avoid leaking information via query completion time? Their suggestion is to make timing predictable - so regardless of how long the query takes, always return at a constant time. That may mean padding on a delay, or aborting part of the query and returning an error.

By aborting the query, that could actually change the result, but the researchers say that's okay, because the default values will be set to what was expected if the lookout had completed (in this case 1, for true).

Their proposed solution, Fuzz, will pad this time in there, which sounds like it will solve the timing attack, but may make your transactions unacceptably slow, in my opinion.

The audio and video of this presentation are now online.

Outsourcing the Decryption of ABE Ciphertexts
Matthew Green and Susan Hohenberger, Johns Hopkins University; Brent Waters, University of Texas at Austin. Presented by Matt Green.

The researchers have been working on protecting medical records. By using cryptographic control on the records, you can encrypt the record for all valid participants, but that is not very flexible - what if you add, or remove, relevant people?

Attribute-based encryption (ABE) is a little more general. For example, you can encrypt data that can be read by "Cardiologist at Johns Hopkins", so if your cardiologist changes, your new doctor can still access your medical record.

The main problem is that the more complex the policy, the larger the ciphertext grows as well as the decryption time. For example, doing a decrypt on a smartphone could take up to 30 seconds - too long for practical use, particularly if you were a doctor that had to do these decrypts all day long.

The naive approach is to leverage the cloud to assist with the decryption, but you really need to trust your cloud....just too many vectors for attack.

Their approach is to have *two* keys - a transform key (TK) and a secure key (SK). The transform key, which can be in the cloud, can't fully decrypt the ciphertext by itself. The cloud would then partially decrypt the data, and the SK on the phone would complete it.

The researchers found that by doing this transform, which allows external assist, the decrypt time on their iPhone went from 28 seconds to under 2 seconds.

This same research can be applied to smartcards, which are very slow little chips.

The audio and video of this presentation are now online.

Faster Secure Two-Party Computation Using Garbled Circuits
Yan Huang and David Evans, University of Virginia; Jonathan Katz, University of Maryland; Lior Malka, Intel. Presented by Yan Huang.

The researches are trying to implement a system for secure 2-party computation using garbled circuits that is much more scalable and significantly faster than prior work.

This is based on prior work by Andrew Yao from the 1980s. While the garbled circuits theory has been around for a long time, prior implementations have been too slow to be used in practice. The researchers used a Yao chaining garbled circuit, and added a method of parallel processing to speed up the processing time.

Their framework doesn't require people to have expert knowledge about cryptography, but users will need to know basic ideas of boolean circuits. You can learn more and try out their Android app at their website, mightbeevil.com.

The audio and video of this presentation are now online.

This article is syndicated from Thoughts on security, beer, theater and biking!

USENIX: Pico: No More Passwords!

Frank Stajano, from the University of Cambridge, talked about the growing password problem Many years ago, when we all only had one or two passwords to remember, memorizing one or two simple 8 character passwords was very simple to do.

Nowadays, we like have 20-30 (or more?) accounts, all with different password policies, and we just can't memorize them all - and the things we're coming up with that we believe have high entropy, are actually very easily cracked - as illustrated by this recent xkcd.

The little shortcuts we take, like reusing our "good" passwords, means that once it is compromised on one site (through no fault of the user), the attacker has access to many more sites. This was demonstrated recently with the Sony password leaks.

Because we forget passwords, all websites have a method for recovering your password - which can be attacked.

Stajano says that passwords are both unusable and insecure, so why on earth are we still using them?

Perhaps we can start over? Let's get rid of passwords! That's where Pico comes in. The goals of Pico are:

• no more passwords, passphrases or PINs
• scalable to thousands of vendors
• no less secure than passwords (trivial)
• usability benefits
• security benefits

He wants to make sure we stay away from trying to make the user remember things, so that eliminates things like remembering pictures, shapes, etc.

Other requirements for Pico are it must be scalable, secure, loss-resistant, theft-resistant, works-for-all, works from anywhere, no search, no typing, continuous.

Pico would have a camera, display, pairing button and main button, as well as radio to communicate. The device could look like a smart phone, a keyfob, watch, etc, but it is a dedicated device. It shouldn't be on multipurpose device, like an actual smart phone, as it would then be opened up to too many forms of attack.

The camera would use a visual code in order to know what it is trying to authenticate. The radio device would be used to communicate to the computer over an encrypted channel. The main button is used to authenticate, and the pairing button would be used for initialization of an authentication pairing. Obviously, this type of system would not just be an extension of existing systems, but would require hardware extensions.

Pico would initialize by scanning the application's visual code, get the full key via radio and check it against the visual code and stores it. Pico would respond, then, with an ephemeral public key, then challenges the application to prove ownership of the application's secret key. Once all of those challenges are passed, then Pico will come up with it's on keypair for that application and share a long term public key with the application. The application will store that and then would know your Pico the next time you try to connect to that application.

While you're connected to the application, your Pico would be continually talking to the application, via the radio interface.

Of course, simply having the Pico cannot be enough - otherwise someone could take your Pico and impersonate you. This is where the concept of "picosiblings" comes into play. Picosiblings would be things like a watch, belt, ring, cellphone, etc (things you often have with you), and the device would only work with those things nearby. [VAF: Personally, I'd hate to think I wouldn't be able to get money out of the ATM simply because I'd forgotten to wear my Java ring that day].

If you lose your Pico, you'd need to use some of your picosiblings to regenerate it - so don't lose all of your picosiblings as well! It seems that you want to have enough picosiblings, but not too many. I'm not sure how you determine that correct level :)

Pico access can't be tortured out of you, as it can't be unlocked by anything that you know (there's no PIN or password).

"Optimization is the process of taking something that works and replacing it with something that almost works, but costs less." - Roger Needham

With that in mind, Stajano notes that if he actually wants people to adopt this, he would likely need to think of a smart phone client.

There were a lot of interesting ideas in this talk, but the thought of carrying around yet another device is not appealing, and the burden of replacement and function (with all the picosiblings) makes this seem untenable to me - but, if it gets people thinking, then it's definitely a step in the right direction!

The audio and video of this presentation are now online.

This article is syndicated from Thoughts on security, beer, theater and biking!