Thank you that was useful
On 07/12/17 03:41, Matthieu Boutier wrote:
> Hi,
>
> A first step could be to remove the "-g" from CFLAGS. Default is "-Os -g".
>
> On my desktop computer (debian 64bits, gcc), commit 9be552feda7f:
>
> $ make clean > /dev/null; make CFLAGS="-Os -g" > /dev/null; du -h
Hello, i've been compiling babeld and modified versions of it using make
and to cross compile; make CC=mipsel-linux-gcc
PLATFORM_DEFINES='-march=mips32'
Using gcc the size of the executable file is 361K and about the same
size when cross compiling.
Now in the babeld.ipk on LEDE:
I see, however the project has already been accepted so i will have to
do it anyway :(
Maybe i can think not to use random numbers but something to make it
more difficult that a false ciphertext be accepted by other nodes.
Thanks, i will use the references to point out the vulnerabilities.
El
El 08/09/17 a las 07:37, Toke Høiland-Jørgensen escribió:
>> Hi, i wanted to reduce the risk of ip spoofing as an academic excercise.
>
> I'm all for academic exercises, I'm just suggesting that it'll be
> helpful to define (on the protocol level) what you are trying to protect
> against. I.e.,
El 08/09/17 a las 05:28, Toke Høiland-Jørgensen escribió:
> Rodrigo Garcia <str...@riseup.net> writes:
>
>> Hello, i've been working on an extension to the babel protocol to
>> authenticate updates using RSA. It's mostly an academic excercise and i
>> have planned
Hello, i've been working on an extension to the babel protocol to
authenticate updates using RSA. It's mostly an academic excercise and i
have planned the first functional versions in a month or so.
The main idea is to make that a *central entity* generates a set of
encrypted tokens using a RSA
6 matches
Mail list logo
