[
https://issues.apache.org/jira/browse/CASSANDRA-11518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15229131#comment-15229131
]
Ariel Weisberg commented on CASSANDRA-11518:
--------------------------------------------
|[trunk
code|https://github.com/apache/cassandra/compare/trunk...aweisberg:CASSANDRA-11518-trunk?expand=1]|[utests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-11518-trunk-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-11518-trunk-dtest/]|
|[3.0
code|https://github.com/apache/cassandra/compare/cassandra-3.0...aweisberg:CASSANDRA-11518-3.0?expand=1]|[utests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-11518-3.0-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/aweisberg/job/aweisberg-CASSANDRA-11518-3.0-dtest/]|
> o.a.c.utils.UUIDGen clock generation is not very high in entropy
> ----------------------------------------------------------------
>
> Key: CASSANDRA-11518
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11518
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Priority: Trivial
> Fix For: 3.0.x, 3.x
>
>
> makeClockSeqAndNode uses {{java.util.Random}} to generate the clock.
> {{Random}} only has 48-bits of internal state so it's not going to generate
> the best bits for clock and in addition to that it uses a collision prone
> seed that sort of defeats the purpose of clock sequence.
> A better approach to get the most out of those 14-bits would be to use
> {{SecureRandom}} with something like SHA1PRNG.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
