https://redmine.openinfosecfoundation.org/https://redmine.openinfosecfoundation.org/favicon.ico?17011170022015-04-28T14:27:32ZOpen Information Security FoundationSuricata - Bug #1457: Non-standard prefixes used for file size indicationhttps://redmine.openinfosecfoundation.org/issues/1457?journal_id=51322015-04-28T14:27:32ZAndreas Moemoe.andreas@gmail.com
<ul></ul><p>Firstly standards are not laws, so no need for a system to follow it. But it might lower potential missunderstandings for newcommers to suri. Personally i (and a quick survey of a handfull coworkers) do not relly on the case of a unit suffix in our work to identify the unit of measure.</p>
<p>If this is a change we should do i am for it though, seems simple to implement, changing old configs should not be difficult eithet, and it would as mentioned lower the potential misunderstandigns for new users.</p>
<p>Also, not sure if this should be a bug or a feature request for suri to follow a given standard?</p> Suricata - Bug #1457: Non-standard prefixes used for file size indicationhttps://redmine.openinfosecfoundation.org/issues/1457?journal_id=51332015-04-28T16:40:30ZJames Moejimoe@sohnen-moe.com
<ul></ul><p>Andreas Moe wrote:</p>
<blockquote>
<p>Firstly standards are not laws, so no need for a system to follow it.</p>
</blockquote>
W3C's standards, for instance HTML, are not law either. Life is much easier, though, when we conform to them.
<blockquote>
<p>Also, not sure if this should be a bug or a feature request for suri to follow a given standard?</p>
</blockquote>
It is bit of both.<br />bug: Correct the misuse of standard prefixes<br />feature: Conform to international standards regarding numeric prefixes Suricata - Bug #1457: Non-standard prefixes used for file size indicationhttps://redmine.openinfosecfoundation.org/issues/1457?journal_id=51352015-04-29T08:24:35ZAndreas Moemoe.andreas@gmail.com
<ul></ul><p>Well, after thinking about this for a while, the correct suffixes would probably be ex MebiByte (MiB) and so on. This would be following the IEEE 1541-2002 standard. So i think using kilo and mega are wrong (since they are 10^n, and since this is "computer science" it should base itself on 2^n).</p> Suricata - Bug #1457: Non-standard prefixes used for file size indicationhttps://redmine.openinfosecfoundation.org/issues/1457?journal_id=73312016-09-08T14:41:28ZAndreas Herzoisf@herzandreas.de
<ul><li><strong>Assignee</strong> set to <i>OISF Dev</i></li><li><strong>Target version</strong> set to <i>TBD</i></li></ul> Suricata - Bug #1457: Non-standard prefixes used for file size indicationhttps://redmine.openinfosecfoundation.org/issues/1457?journal_id=100072018-07-17T10:52:39ZVictor Julienvictor@inliniac.net
<ul><li><strong>Assignee</strong> changed from <i>OISF Dev</i> to <i>Anonymous</i></li><li><strong>Effort</strong> set to <i>low</i></li><li><strong>Difficulty</strong> set to <i>low</i></li></ul> Suricata - Bug #1457: Non-standard prefixes used for file size indicationhttps://redmine.openinfosecfoundation.org/issues/1457?journal_id=112192019-02-23T22:16:49ZAndreas Herzoisf@herzandreas.de
<ul><li><strong>Assignee</strong> set to <i>Community Ticket</i></li></ul> Suricata - Bug #1457: Non-standard prefixes used for file size indicationhttps://redmine.openinfosecfoundation.org/issues/1457?journal_id=131432019-07-27T22:32:49ZAndreas Herzoisf@herzandreas.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> changed from <i>Community Ticket</i> to <i>OISF Dev</i></li></ul><p>Do we have any thoughts/decision about that?</p>