The way DNS works in i2p makes it unreliable and vulnerable to attacks. It wouldn’t be to hard for an adversary to do a man in the middle or even do a fake version of a site. Also resolving DNS names is hard and takes a lot of effort.

Honestly the entire system needs to be rethought.

  • shortwavesurfer@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    I think my big gripe with I2P is the speed. I expected it to be much faster than accessing a tor hit in service. And it just absolutely completely disappointed me. Connecting to a monero node on tor got me 500KiB/s, on i2p i got 40KiB/s at best. Very disappointed.

    I was under the impression that I2P was built with hidden services in mind. And I’ve been disabused of that notion.

  • henfredemars@infosec.pub
    link
    fedilink
    English
    arrow-up
    0
    ·
    6 months ago

    Are I referring to name resolution on the network or for when you’re trying to access open Internet webpages via an out proxy?

      • henfredemars@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        6 months ago

        I still am not sure what your question is asking. Typically, name resolution is handled by your local I2P router using an address book. You trust whatever subscriptions are dumping into your address book. There isn’t really a central naming authority. Names can be set by whatever authority you choose.

        Are you concerned about getting a bad address book subscription? What, concretely, do you mean by DNS?