OnionCat Mailinglist

After a long time living without mailing list, it is back up again. To subscribe to the OnionCat list send an email to onioncat-subscribe@onioncat.org or register at the following URL http://mx01.services.blackmesa.at/cgi-bin/mailman/listinfo/onioncat.


15 pings

Skip to comment form

    • tester on January 15, 2014 at 10:46 pm

    Welcome back ! 🙂

    • wormhole-420 on January 29, 2014 at 7:14 am

    the deepnet and all the hidden stuff in it is way cool and knowledge is freedom we all have the right to knowledge we are told what we can and can not read.We live in a world were we are told lies from the people who govern the world how has lie and hidden things from use all the time trust no one trust ur self only.To survive in this world you need to adapt quickly. Fall off the grid completely use all other resource cause we are all watched one way or the other from the sky to the ground to electronicaly none of use are safe or free .We have no freedom.


      • eagle on January 29, 2014 at 9:16 am

      But resignation would mean to admit that the’ve won. Never ever!

    • Name on February 24, 2014 at 8:38 pm

    Never surrender! (but be paronoid as hell)


    • Anonymous on June 16, 2014 at 10:49 pm

    Hello,any updates or lists archive? Thanks

    • Renne on June 22, 2014 at 10:40 am

    Dead Link: “http://mx01.services.blackmesa.at/cgi-bin/mailman/listinfo/onioncat” -> “No such list onioncat”!

    Is it possible to route an OnionCat IPv6-address into the LAN?

    My idea is to use OnionCat as a secure public overlay network for SIP-phones (SIP-phone as Tor Hidden Service). Because OnionCat cannot be installed on SIP-phones, I’m looking for a solution to run OnionCat on a gateway and route IPv6 traffic to the phones. A SIP-proxy (Tor -> Hidden Service -> OnionCat -> SIP-proxy -> SIP-phone) is an option but is limited to the SIP-protocol. IPv6-routing into the LAN would allow a generic overlay network.

      • eagle on June 23, 2014 at 1:24 pm

      Sorry, mailing list will be repaired asap!

      OnionCat basically is completely transparent, i.e. you can route as you can do with a router. In respect to your scenario: do you run one OC for each SIP phone? And don’t you need some kind of central service (such as Asterisk) that these phones will find each other? If you give me a little bit more information I could make some suggestions/solutions.

      You may read this article:

      and probably also this article (IPv4 might make your life easier 😉 ):

    • yonailo on July 20, 2015 at 11:16 am


    I have successfully set up an hidden ocat service, I can ping6 and all stuff, but why not set up a public directory of ocat enabled services ? I even imagine we could use DNS or another similar service to provide a kind of easy-to-remember alias for .onion urls…. what do you think ?

      • B347 on January 6, 2016 at 4:17 pm

      I found a Services page at
      But I couldn’t connect to anything listed 🙁

        • eagle on January 6, 2016 at 10:16 pm

        Those services are outdated, sorry. By design, there is no centralized database of services.

    • B347 on January 6, 2016 at 4:21 pm

    Just starting out with OnionCat.
    Is it still and active project, and still relevent?
    Where is the best place to find up to date information and maybe some more support/howto imformation?
    So far I have to linux boxes able to ping each other, but no joy with android or windows (w7/cygwin).
    My current goal is to connect syncthing across ocat to all of the above. Each device is running tor ok so far.

      • eagle on January 6, 2016 at 10:11 pm

      Since governments tend to more and more surveillance, networks such as OnionCat are more relevant than ever. There is an article about OnionCat on Android (here is a precompiled ARM-binary) and it works on Win7 for sure. Please have a look at the FAQ and the debugging page.

      If you have troubles, please don’t hesitate to contact us on the mailing list.

  1. hello i am looking for the ocat mailinglist but it looks broken as below.
    please help.
    thanks 🙂

    Bug in Mailman version 2.1.18

    We’re sorry, we hit a bug!

    Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.

    • zoobab on May 15, 2017 at 6:09 pm

    The URL to the mailing list is still broken.

      • eagle on December 7, 2017 at 9:28 am

      I’ll move the whole project to Github soon, thus getting better community support.

Leave a Reply

Your email address will not be published.