I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Rename to 'banlist'.

Browse Source
This commit is contained in:
dg2-new
2013-10-30 13:02:57 +00:00
parent 5171064fcd
commit b81c882575
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
www.i2p2/pages/i2cp_spec.html
View File

@@ -789,7 +789,7 @@ As of release 0.7.1.
Tell the other party (client or router) that they are under attack, potentially with reference to a Tell the other party (client or router) that they are under attack, potentially with reference to a
particular messageId. If the router is under attack, the client may decide to particular messageId. If the router is under attack, the client may decide to
migrate to another router, and if a client is under attack, the router may rebuild migrate to another router, and if a client is under attack, the router may rebuild
its routers or shitlist some of the peers that sent it messages delivering the attack. its routers or banlist some of the peers that sent it messages delivering the attack.
Sent either from router to client or from client to router. Sent either from router to client or from client to router.
</p> </p>
<h4>Contents</h4> <h4>Contents</h4>

2
www.i2p2/pages/performance-history.html
View File

@@ -54,7 +54,7 @@ going through the full (expensive) Diffie-Hellman handshaking to negotiate a
private session key. This means that if someone's clock is really wrong, or private session key. This means that if someone's clock is really wrong, or
their NAT/firewall/etc is improperly configured (or they're just running an their NAT/firewall/etc is improperly configured (or they're just running an
incompatible version of the router), they're going to consistently (though not incompatible version of the router), they're going to consistently (though not
constantly, thanks to the shitlist) cause a futile expensive cryptographic constantly, thanks to the banlist) cause a futile expensive cryptographic
operation on all the peers they know about. While we will want to keep some operation on all the peers they know about. While we will want to keep some
verification/validation within the encryption boundary, we'll want to update the verification/validation within the encryption boundary, we'll want to update the
protocol to do some of it first, so that we can reject them cleanly protocol to do some of it first, so that we can reject them cleanly

6
www.i2p2/pages/ratestats.html
View File

@@ -135,7 +135,7 @@ netDb.writeOut
netDb.writePending netDb.writePending
netDb.writeTime netDb.writeTime
ntcp.accept ntcp.accept
ntcp.attemptShitlistedPeer ntcp.attemptBanlistedPeer
ntcp.attemptUnreachablePeer ntcp.attemptUnreachablePeer
ntcp.bidRejectedLocalAddress ntcp.bidRejectedLocalAddress
ntcp.bidRejectedNoNTCPAddress ntcp.bidRejectedNoNTCPAddress
@@ -288,7 +288,7 @@ swarm." + getConnectionId() + ".totalReceived
transport.bidFailAllTransports transport.bidFailAllTransports
transport.bidFailNoTransports transport.bidFailNoTransports
transport.bidFailSelf transport.bidFailSelf
transport.bidFailShitlisted transport.bidFailBanlisted
transport.expiredOnQueueLifetime transport.expiredOnQueueLifetime
transport.getBidsJobTime transport.getBidsJobTime
transport.noBidsYetNotAllUnreachable transport.noBidsYetNotAllUnreachable
@@ -304,7 +304,7 @@ transport.sendMessageMedium
transport.sendMessageSize transport.sendMessageSize
transport.sendMessageSmall transport.sendMessageSmall
transport.sendProcessingTime transport.sendProcessingTime
transport.shitlistOnUnreachable transport.banlistOnUnreachable
tunnel.acceptLoad tunnel.acceptLoad
tunnel.batchCount tunnel.batchCount
tunnel.batchDelay tunnel.batchDelay