Fix German date parsing.

CLDR changed German from having a mix of 3- and 4-character abbreviated month
names (such as "Juli" and "Aug"[ust]) to having only 4-character names by
adding periods to the end of abbreviated names (giving "Juli" and "Aug.").
This means that a date formatted with the old data (by jb-mr1, say) can't
be parsed with the new data (in jb-mr2, say). Work around this by doing what
icu4c's SimpleDateFormat::parse does --- accepting "xxx" as a match for "xxx.".

Bug: https://code.google.com/p/android/issues/detail?id=59383
Bug: 10511599
Change-Id: I021ea8ffeea37ea2cae943a84cdd2babb337301d
Apply a variation of the suggested app-level patch to SecureRandom

http://android-developers.blogspot.pt/2013/08/some-securerandom-thoughts.html
for more details. This isn't an ideal solution, but until a proper patch
comes up it'll do

Change-Id: Ib6bf4478fc1ae3d16eefa4eb2ad90f1f3e9de021
Merge "Fix German date parsing." into cm-10.2
Do not apply the PRNG workarounds if an explicit seed is given

If the caller seeds the engine, do NOT override that seed with another
from urandom.

This is a companion change to Ib6bf4478fc1ae3d16eefa4eb2ad90f1f3e9de021,
and should be reverted along with it when the proper fix appears.

Change-Id: I0a9ba35d74af89c91b6aafa35cc94001372794e1
Merge tag 'android-4.3_r3.1' of https://android.googlesource.com/platform/libcore into cm-10.2

Android 4.3 Release 3.1
workaround an armv6 gcc 4.7 bug

this fixes com.android.phone getting a SIGBUS on startup due to mmap'd
tzdata reads that always crash in this libcore code.
gcc 4.8 works without issue and 4.6 worked fine with cm10.1, so this
workaround has been made specific to just gcc 4.7.

Change-Id: Ide3b33dd8bdbb1e0f1a91b65ba21c7aa8e276af5
jsse: Use TLS 1.2 and AES as the default cipher.

Don't use the weak RC4 MD5 as the default cipher and by default allow
TLS 1.2.

http://op-co.de/blog/posts/android_ssl_downgrade/

Change-Id: I8ff3bd50b40a75c54e94f18e78ea54690bee3f87
Revert "jsse: Use TLS 1.2 and AES as the default cipher."

This reverts commit a3fd3e33d3cc469d9d9c10e3f23c658983360b66.

Change-Id: I13737b6cb0e31f0e6a49b5b736d54c665850d7b1
jsse: Make sure we use TLSv1.2 as the default protocol.

We should at least try to use TLSv1.2 if the server supports it and do
not use error prone versions of the protocol.

https://community.qualys.com/blogs/securitylabs/2013/09/10/is-beast-still-a-threat

Change-Id: Ic1faad2bb1dd526930c4c5280d0851cbc8087047
Merge remote-tracking branch 'cm/cm-10.2' into jb3