Yes, I could, but I worried about doing so outside of AOSP, since the external/openssl changes were only part of the work, changes were also made to users of openssl to deal with issues surrounding TLSv1.1 and TLSv1.2 interoperability.
I don't understand this rush to 1.0.1. this is not a minor upgrade. we've had to push new patches back to OpenSSL upstream for almost every release. I think 1.0.1c might the the first one where we didn't need build fixes patches for upstream. they've continued to fix interoperability issues as well. Why does everyone seem so eager to have this? Security patches continue to be made on the 1.0.0 (and even 0.9.8) lines -bri On Mon, May 14, 2012 at 5:21 AM, jumper <[email protected]> wrote: > Hi Brian - > > Can you please share the Android.mk files and patch files / steps that you > had executed for compiling OpenSSL1.0.1b? > > -br > > > On Saturday, April 28, 2012 9:27:41 AM UTC+5:30, Brian Carlstrom wrote: >> >> Sure, I was able to update 1.0.1, 1.0.1a, and am now looking at 1.0.1b. >> There weren't any real conflicts, just us adding things adjacent to their >> add things. They did have a few compile issues along the way that I had to >> work around (such as build issue for non-x86 hosts in 1.0.1a) >> >> -bri >> >> On Fri, Apr 27, 2012 at 12:24 AM, vkasirajan <[email protected]>wrote: >> >>> Hi Adam, >>> >>> Any updates on this? Were you able to integrate openssl 1.0.1? >>> >>> Thanks and best regards, >>> >>> On Wednesday, March 7, 2012 5:21:32 AM UTC+5:30, Adam wrote: >>> >>>> Hi, >>>> >>>> I'm wondering if anyone has tried to compile OpenSSL 1.0.1-beta2 or >>>> beta3 for Android. I tried to incorporate beta2 into the ICS source >>>> using the patches in the [SRC]/external/openssl directory with no >>>> luck. If anyone has any experience with this I would appreciate the >>>> advice. >>>> >>>> Thanks, >>>> >>>> Adam >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Android Security Discussions" group. >>> To view this discussion on the web visit https://groups.google.com/d/** >>> msg/android-security-discuss/-**/26HTrQ46rooJ<https://groups.google.com/d/msg/android-security-discuss/-/26HTrQ46rooJ> >>> . >>> >>> To post to this group, send email to android-security-discuss@** >>> googlegroups.com <[email protected]>. >>> To unsubscribe from this group, send email to android-security-discuss+* >>> *[email protected]<android-security-discuss%[email protected]> >>> . >>> For more options, visit this group at http://groups.google.com/** >>> group/android-security-**discuss?hl=en<http://groups.google.com/group/android-security-discuss?hl=en> >>> . >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Android Security Discussions" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/android-security-discuss/-/Xi_47o8LmM0J. > > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/android-security-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-security-discuss?hl=en.
