nickfelt 0405a427f1 Remove unnecessary SecureRandom from UrlFetchUtils ... We're only using it for generating multiparty boundaries, and there's no real need for the random boundary values to be cryptographically secure. The point of the randomness is just to make collisions with content in the payload sufficiently unlikely. The app itself controls the payload contents, and while it might be derived from user-submitted content, in practice it would be nearly infeasible to get the payload to contain arbitrary boundary values even if the RNG-produced boundaries could be determined in advance. To further insulate against this, I've increased the boundary size (from 40 bits to 192) and added an actual check that the boundary isn't present in the input data, so that in the extremely unlikely event of a collision, we fail rather than producing an invalid multipart request. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=142784289		2016-12-22 16:10:44 -05:00
..
com/google	Add missing dependency on Jackson2 library	2016-12-19 11:09:20 -05:00
google/registry	Remove unnecessary SecureRandom from UrlFetchUtils	2016-12-22 16:10:44 -05:00