[13:26:32]
<lapineige> Mike: Also it would be really great if you shared that "recipe" (how you did it) on the forum, so other people could reproduce it, and discover the app or tutorial (things get lost almost instantly here).
[13:29:31]
<marcus> Hello, I would like to publish certain yunohost applications on the TOR network, but also on the clear-web, so I would like to set up a mirror on TOR for certain applications. What is the most suitable method with yunohost?
[13:31:39]
<Tag> It's not really safe to use YunoHost as a hidden service. A lot of YunoHost behavior will leak to clearweb.
[13:33:13]
<Tag> But there's this : https://yunohost.org/en/administer/tutorials/tor marcus
[13:33:54]
<marcus> > <@tag:lostpod.me> It's not really safe to use YunoHost as a hidden service. A lot of YunoHost behavior will leak to clearweb.
This is not for anonymity, but simply to avoid censorship in the event that the ClearWEB domain name is blacklisted by operators. In this case the Tor mirror would still allow access to the applications
[13:34:50]
<Tag> Well I guess using Tor browser is enough to bypass this kind of censorship. You don't need a hidden service.
[13:35:04]
<marcus> If the domain name in the clear web gets blacklisted, this means that I will have to change it and replace it with another one, so the old one will not work under TOR. What I would like is a permanent onion domain name and parallel to the clearweb domain names which will follow one after the other
[13:36:37]
<Tag> I would just register a noho.st domain and use it as the "permanent domain"
[13:36:50]
<Tag> But anyway with yunohost you can't have two domains pointing on the same app. You'll have to tinker with nginx conf somehow I guess
[13:37:54]
<Tag> Maybe the redirect\_ynh app can help ? But I never tried it like this
[13:37:59]
<marcus> Even noho.st domains are easily censorable, and what's more, they are managed directly by yunohost and not by the owner!
The uncensorable and truly permanent domain names are the DarkWEB domain names.
[13:38:00]
<Tag> Ok hackerman
[13:42:30]
<marcus> I will try to tinker to point the onion domain name and the domain name configured in the yunohost interface to the same application!
[13:43:40]
<Tag> Cool! Feel free to report your findings on the forum :) This room is more suited for beginner-level support.
[21:36:35]
<aaron> Hey everyone, I would like to share the presentation about yunohost that I had today on the Datenspuren in Dresden: https://media.ccc.de/v/ds23-249-heimserver-aufsetzen-und-verwalten-mit-yunohost - I was doing it in german, but maybe for the bigger CCC-Congress in Hamburg this year, someone from the development team would like to present it to a bigger audience in english :)
There were definitely some difficult questions, that I was not able to answer, since I don't have enough knowledge yet, but I was happy that there were some people who studied IT in the audience that helped me :)
[21:38:29]
<aaron> keep up the great work and maybe I will be able to contribute to it in the future and maintain some packages :)
[21:41:20]
<Aleks (he/him/il/lui)> ooh CCC congress is in hamburg this year, not leipzig ?
[21:42:30]
<Aleks (he/him/il/lui)> thanks a lot for the talk and sharing the video <3
[22:18:51]
<aaron> > <@Alekswag:matrix.org> thanks a lot for the talk and sharing the video <3
thank you for all this incredible work!
[22:29:31]
<aaron> As far as I know. There will be more information soon I guess :)
[22:45:22]
<Paprika> Hi,
We have thoroughly inspected our network - whether routes are set and proper, firewall filter rules, NAT, interfaces and whatnot, but we cannot find out why for the love of god, when a client connects to the router that has a WG instance running, why can’t they interact with YNH. The packets reach the server, but nothing is ever returned. Pinging the WG interface or the client on the WG interface from YNH returns “sendmsg: required key not available”.
Can anybody shed some light?
[23:17:12]
<@err404:matrix.org> Paprika: we need logs or more details
[23:19:43]
<@err404:matrix.org> Ping is not enough to determine somes issues, you should use traceroute instead
[23:20:38]
<Paprika> Traceroute produces the same message, forgot to mention
[23:21:14]
<Paprika> > <@err404:matrix.org> Paprika: we need logs or more details
I’ll try to see if anything comes up in logs, but where can I see rejected traffic or anything of the sort in YNH?
[23:21:48]
<Paprika> Because at this point all I can do is assume packets are dropped for some reason
[23:23:25]
<@err404:matrix.org> They can be dropped by fail2ban, please check that if you are banned.
[23:25:12]
<@err404:matrix.org> And eventually search for command line to remove the ban