I2P Address: [http://git.idk.i2p]

Skip to content
Snippets Groups Projects
  1. Jan 23, 2022
  2. Jan 22, 2022
  3. Jan 16, 2022
    • zzz's avatar
      i2psnark: Add UDPTrackerClient · 0b058c0f
      zzz authored
      WIP - not hooked in, untested - target 1.8.0 / 0.9.54
      Requires significant changes to TrackerClient
      Adapted from mtn branch i2p.i2p.zzz.udpsnark (2014)
      Ref: Proposal 160
      Unverified
      0b058c0f
  4. Jan 15, 2022
  5. Jan 10, 2022
  6. Jan 07, 2022
  7. Jan 05, 2022
  8. Jan 04, 2022
  9. Jan 03, 2022
  10. Jan 02, 2022
  11. Dec 30, 2021
  12. Dec 28, 2021
  13. Dec 27, 2021
  14. Dec 23, 2021
  15. Dec 21, 2021
  16. Dec 18, 2021
  17. Dec 11, 2021
    • idk's avatar
      disable any chance of JNDI lookups in log4j.properties file by setting... · c4cfe420
      idk authored
      disable any chance of JNDI lookups in log4j.properties file by setting %m{nolookups}. I don't think we're actually vulnerable to CVE-2021-44228 if I'm understanding correctly, by default it doesn't seem like we actually use log4j for much of anything and we don't do much logging of arbitrarily crafted remote inputs, but also it seems like this JNDI lookups thing is way more trouble than it could possibly be worth to us. Maybe it's a good idea to make sure it's turned off by default.
      Verified
      c4cfe420
  18. Dec 08, 2021
    • zzz's avatar
      i2ptunnel: Refactor UDPTunnel, Streamr, and SOCKS UDP for I2CP ports · b1a4a851
      zzz authored
      - Add fromPort and toPort to Sink interface (breaking API change)
      - Change cache maps from Destination to I2PSocketAddress to include port
      - Accept host:port for destination in Streamr Client, use port
        as toPort in pinger
      - Change to muxed listener in I2PSource, only listen for
        specified protocols
      - Eliminate thread and queue in I2PSource, process messages inline
        in the listener
      - Add support for handling both repliable and raw datagrams in
        a single I2PSource instance
      - Remove verify option from I2PSource and I2PTunnelUDPServerBase,
        always verify repliable datagrams
      - Add getPort() method to UDPSource
      - Add a constructor to UDPSink to pass in an existing DatagramSocket
      - Change I2PTunnelUDPClientBase to receive both repliable and raw
      - Change SOCKSUDPTunnel reply handling strategy to key on I2CP toPort;
        remove ReplyTracker; the tunnel would not have worked before, because
        it expected raw replies only but MultiSink required a destination
        to look up where to forward the reply.
      - Mark SOCKSUDPTunnel as preliminary; note lack of support
        for raw replies; untested
      - Change Streamr Client Pinger to support fromPort
      - Change Streamr Server to remember fromPort in subscriptions
        and use it as toPort in data stream
      - Move fields to top of classes for sanity
      - Cleanups and log tweaks
      Unverified
      b1a4a851
  19. Dec 07, 2021
Loading