Open Merge Requests
===
IDComponentReporterAssignee Updated For Version
PrioritySummary
--- -- - -- -
--
BIT-1068 [1] BroControl
Bernhard Amann created BIT-1069:
---
Summary: merge topic/bernhard/hexstr
Key: BIT-1069
URL: https://bro-tracker.atlassian.net/browse/BIT-1069
Project: Bro Issue Tracker
Issue Type: New Feature
[
https://bro-tracker.atlassian.net/browse/BIT-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernhard Amann updated BIT-1069:
Status: Merge Request (was: Open)
merge topic/bernhard/hexstr
---
[
https://bro-tracker.atlassian.net/browse/BIT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805#comment-13805
]
Adam Slagell commented on BIT-1016:
---
C-hex probably doesn't matter. They could treat it as
[
https://bro-tracker.atlassian.net/browse/BIT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer updated BIT-1016:
--
Status: Open (was: Merge Request)
Option to extend uids to 128 bit
[
https://bro-tracker.atlassian.net/browse/BIT-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807#comment-13807
]
Daniel Thayer commented on BIT-1068:
Yes, it was intentional. Without that check, then if
[
https://bro-tracker.atlassian.net/browse/BIT-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806#comment-13806
]
Robin Sommer commented on BIT-1068:
---
Is the true here intentional?
{code}
[…]
#
[
https://bro-tracker.atlassian.net/browse/BIT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808#comment-13808
]
Robin Sommer commented on BIT-1016:
---
Good point.
Robin
--
Robin Sommer * Phone +1
On Tue, Aug 27, 2013 at 20:35 +, you wrote:
FWIW, I prefer Chex for the simple reason that if I double-click it,
it selects the whole uid (including the C), and I can then copy the
whole thing.
Good point.
Robin
--
Robin Sommer * Phone +1 (510) 722-6541 * ro...@icir.org
ICSI/LBNL
On Aug 27, 2013, at 3:50 PM, Robin Sommer (JIRA)
j...@bro-tracker.atlassian.net wrote:
- We could use C-hex instead of Chex to make it more obvious that the
first character is special. But not sure if it's worth it.
FWIW, I prefer Chex for the simple reason that if I double-click it, it
[
https://bro-tracker.atlassian.net/browse/BIT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809#comment-13809
]
Jon Siwek commented on BIT-1016:
{quote}while I generally like the bits_per_uid option, I'm
[
https://bro-tracker.atlassian.net/browse/BIT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810#comment-13810
]
Matthias Vallentin commented on BIT-1016:
-
Regarding performance: another option would
I like that idea. Storage-wise it's 2x64 bit anyways.
Robin
On Tue, Aug 27, 2013 at 16:04 -0500, you wrote:
Regarding performance: another option would be to use 128-bit UUIDs
internally and just chop of 32 bytes if a 96-bit UUID is desired,
assuming the bits in the UUID are distributed
[
https://bro-tracker.atlassian.net/browse/BIT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811#comment-13811
]
Robin Sommer commented on BIT-1016:
---
I like that idea. Storage-wise it's 2x64 bit anyways.
[
https://bro-tracker.atlassian.net/browse/BIT-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13812#comment-13812
]
Jon Siwek commented on BIT-1016:
{quote}
Regarding performance: another option would be to use
15 matches
Mail list logo
