netdev - Re: [iproute2-next 0/2] tipc: changes to addressing structure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 29 Mar 2018 11:58:55 -0600
From:   David Ahern <dsahern@...il.com>
To:     Jon Maloy <jon.maloy@...csson.com>, davem@...emloft.net,
        netdev@...r.kernel.org
Cc:     mohan.krishna.ghanta.krishnamurthy@...csson.com,
        tung.q.nguyen@...tech.com.au, hoang.h.le@...tech.com.au,
        canh.d.luu@...tech.com.au, ying.xue@...driver.com,
        tipc-discussion@...ts.sourceforge.net
Subject: Re: [iproute2-next 0/2] tipc: changes to addressing structure

On 3/29/18 11:52 AM, David Ahern wrote:
> On 3/28/18 10:52 AM, Jon Maloy wrote:
>> 1: We introduce ability to set/get 128-bit node identities
>> 2: We rename 'net id' to 'cluster id' in the command API, 
>>    of course in a compatible way.
>> 3: We print out all 32-bit node addresses as an integer in hex format,
>>    i.e., we remove the assumption about an internal structure.
>>
> 
> Applied to iproute2-next. Thanks,
> 

BTW, please consider adding json support to tipc. It will make tipc
command more robust to changes in output format.