| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Lookup node-id for specifying with "netcrypto" command-line.
|
|
|
|
This isn't really completely correct; there should be some possibility for
denial of service. The call to setContactAddr is destructive of whatever
information was there previously, but we haven't verified that we're talking to
the real contact at the time it is called.
This problem exists even in the ordinary path where the nodeinfocallback isn't
really requiring proof of anything before throwing out data.
|
|
|
|
|
|
|
|
|
|
session 0 interval
-- shows the values of intervals on session 0
session 0 interval 0.5
-- half all the intervals on session 0
|
|
|
|
|
|
|
|
|
|
|
|
The handshake code would flood the network with interminable handshakes.
|
|
|
|
|
|
|
|
|
|
--enable-profiling enables -prof in cabal
--profile enables -prof in stack
Also added:
ghc-prof-options: -g
I think the above will be enabled when cabal is used
to build profiling versions. This probably does not apply
to stack builds.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the cookie is reused until it gets too old
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(The same type is used for both relative and absolute times, which isn't
ideal.)
|
|
|
