Skip to main content
deleted 39 characters in body
Source Link
Henrick Hellström
  • 10.5k
  • 1
  • 30
  • 58

I came across this article, which describes a method, developed by UCLA CS professor Amit Sahai et al, for using functional encryption in order to achieve software obfuscation. The paper that the article refers to doesn't seem to beis available online yet, but doeshere. Has anyone heredigested the paper and have more information to share? Are the results as ground breaking as the article suggests?

In particular, does anyone know if the researchers have managed to fuse functional encryption with software obfuscation, in such way that you could feasibly implement the method, in such way that you would get encrypted executables that would run on existing common platforms, with a negligible performance penalty and with a negligible growth of the footprintclear idea regarding exactly what aspect of an implementation the executablemethod will potentially obfuscate? WouldDoes it only apply to hardware implementations at the method meet such performance requirementsintegrated circuit level? Does it apply even if, say, the algorithm you wantadversary is able to protecttrack and map signals once the chip is originally implemented in an optimized form using at most 100turned on? Does it apply to software implementations for generic platforms, even if the adversary has full control over the CPU instructionsand internal memory (e.g. in case of emulators)?

I came across this article, which describes a method, developed by UCLA CS professor Amit Sahai, for using functional encryption in order to achieve software obfuscation. The paper that the article refers to doesn't seem to be available online yet, but does anyone here have more information to share? Are the results as ground breaking as the article suggests?

In particular, does anyone know if the researchers have managed to fuse functional encryption with software obfuscation, in such way that you could feasibly implement the method, in such way that you would get encrypted executables that would run on existing common platforms, with a negligible performance penalty and with a negligible growth of the footprint of the executable? Would the method meet such performance requirements even if, say, the algorithm you want to protect is originally implemented in an optimized form using at most 100 CPU instructions?

I came across this article, which describes a method, developed by UCLA CS professor Amit Sahai et al, for using functional encryption in order to achieve software obfuscation. The paper that the article refers to is available here. Has anyone digested the paper and have more information to share? Are the results as ground breaking as the article suggests?

In particular, does anyone have a clear idea regarding exactly what aspect of an implementation the method will potentially obfuscate? Does it only apply to hardware implementations at the integrated circuit level? Does it apply even if the adversary is able to track and map signals once the chip is turned on? Does it apply to software implementations for generic platforms, even if the adversary has full control over the CPU and internal memory (e.g. in case of emulators)?

Tweeted twitter.com/#!/StackCrypto/status/362403627274469376
Source Link
Henrick Hellström
  • 10.5k
  • 1
  • 30
  • 58

Practical consequences of using functional encryption for software obfuscation

I came across this article, which describes a method, developed by UCLA CS professor Amit Sahai, for using functional encryption in order to achieve software obfuscation. The paper that the article refers to doesn't seem to be available online yet, but does anyone here have more information to share? Are the results as ground breaking as the article suggests?

In particular, does anyone know if the researchers have managed to fuse functional encryption with software obfuscation, in such way that you could feasibly implement the method, in such way that you would get encrypted executables that would run on existing common platforms, with a negligible performance penalty and with a negligible growth of the footprint of the executable? Would the method meet such performance requirements even if, say, the algorithm you want to protect is originally implemented in an optimized form using at most 100 CPU instructions?