On Tuesday 23 Jul 2013 19:56:43 Robert Hailey wrote:
On 2013/07/23 (Jul), at 11:54 AM, Matthew Toseland wrote:
We haven't quantified this. Maybe we should, but it doesn't seem a good use
of scarce resources to implement a toolkit for an attack that we're not
sure how to beat! At least
At present once you are connected to a peer, it can change its name. So it can
e.g. impersonate your other peers. This is not easily detectable because of
character set issues (there are lots of characters that look like o with
different unicode code points, for example).
IMHO we need to
On Wednesday 24 Jul 2013 20:20:57 Nitesh Bharadwaj wrote:
Improvements from previous update:
1) Improved and a stable UI for mobile application
2) A dedicated TCP server on a different port on home node instead of using
fproxy for handling connection to mobiles (on the lines of
On Wednesday 24 Jul 2013 22:42:58 Robert Hailey wrote:
On 2013/07/24 (Jul), at 3:21 PM, Matthew Toseland wrote:
At present once you are connected to a peer, it can change its name. So it
can e.g. impersonate your other peers. This is not easily detectable
because of character set
On 2013/07/24 (Jul), at 3:21 PM, Matthew Toseland wrote:
> At present once you are connected to a peer, it can change its name. So it
> can e.g. impersonate your other peers. This is not easily detectable because
> of character set issues (there are lots of characters that look like "o" with
