| 11 Dec 2024 |
 lowac | I think only the peers you are directly connected to can see your ip, and not any other nodes since they wouldn’t be connected directly to you. That assumes the peer you connect to doesn’t share your ip with those other nodes, but I don’t see why it would do that since from what I know about the protocol that isn’t necessary for routing. And if it was necessary that would only make Yggdrasil dependent on an underlying internet which would kind of defeat its purpose a bit.
TLDR: The multi hop stuff should prevent other nodes from seeing your ip.
| 20:26:59 |
 dinosaurdynasty | afaik there's no ygg API to get your IP (other than the people you connect to, they need your IP to, well, connect with you) it's still possible to find your real IP using various methods if an attacker was determined enough | 20:33:50 |
 xmpp:zayd@telepath.im | In reply to @lowac:matrix.org
I think only the peers you are directly connected to can see your ip, and not any other nodes since they wouldn’t be connected directly to you. That assumes the peer you connect to doesn’t share your ip with those other nodes, but I don’t see why it would do that since from what I know about the protocol that isn’t necessary for routing. And if it was necessary that would only make Yggdrasil dependent on an underlying internet which would kind of defeat its purpose a bit.
TLDR: The multi hop stuff should prevent other nodes from seeing your ip.
Alright, just wanted to make sure before I accidentally make false claims about Yggdrasil while trying to introduce it to others | 20:42:56 |
| 12 Dec 2024 |
|  @lucidlynx:envs.net left the room. | 06:55:16 |
 speedi3 | https://yggdrasil-network.github.io/2018/07/15/remote-access.html
This is ancient . But I wonder does it picture ygg correctly ? | 17:21:09 |
 neilalexander | It still pretty much applies today | 17:35:56 |
 GitHub | ✳ neilalexander merged PR yggdrasil-network/yggdrasil-go#1194: "Use unveil(2) on OpenBSD" | 18:37:04 |
| GitHub | 🔵 dependabot[bot] opened a new PR yggdrasil-network/yggdrasil-go#1213: "Bump golang.org/x/crypto from 0.29.0 to 0.31.0" with labels external dependency | 18:38:01 |
| dinosaurdynasty | My big use case for yggdrasil is ssh'ing into my router when my wireguard setup isn't working away from home | 18:39:14 |
| dinosaurdynasty | (like when I had MTU issues at a hotel) | 18:39:25 |
| GitHub | ⚫ dependabot[bot] closed PR yggdrasil-network/yggdrasil-go#1213: "Bump golang.org/x/crypto from 0.29.0 to 0.31.0" with comment "Looks like golang.org/x/crypto is up-to-date now, so this is no longer needed." | 18:44:02 |
| GitHub | ✳ neilalexander merged PR yggdrasil-network/yggdrasil-go#1193: "genkeys, yggdrasilctl: Use pledge(2) on OpenBSD" | 18:48:26 |
| speedi3 | I use it to ssh to my home machine. I need some advanced setup now (owncloud), and I was thinking about making a VPN for my guys. But if the encryption on ygg works as advertised,I guess I don't need VPN.
Not to mention it would be a hassle on Android,since android already sees ygg as VPN. | 19:00:15 |
| GitHub | 🔵 neilalexander opened a new PR yggdrasil-network/yggdrasil-go#1214: "Yggdrasil 0.5.11" | 19:01:43 |
| speedi3 | So as I understood,you're upgrading debian version ? | 19:05:19 |
| GitHub | ⬛ neilalexander closed issue yggdrasil-network/yggdrasil-go#1208: "wss:// peering now requires TLS1.3 and has no default port" | 19:08:22 |
| GitHub | ✳ neilalexander merged PR yggdrasil-network/yggdrasil-go#1214: "Yggdrasil 0.5.11" | 19:26:56 |
| neilalexander | @room Yggdrasil 0.5.11 has been released! This release contains important fixes that should improve the stability of the network, so please upgrade your nodes as soon as possible. Please also pass on this message if you know any Yggdrasil users who may not see this notification. | 19:40:15 |
| GitHub | 🔵 klemensn opened a new PR yggdrasil-network/yggdrasil-go#1215: "Use pledge(2) on OpenBSD" | 19:52:30 |
| neilalexander | My S3 apt repo & Fedora COPR have both been updated, FreeBSD port update submitted | 20:39:18 |
| neilalexander | I've also updated yggmail, yggdrasilckr and yggquic too | 20:41:54 |
 Tristan B. Velloza Kildaire | Based | 20:49:44 |
 Arceliar | It's probably worth highlighting that v0.5.11 fixes a memory leak, for anyone who had been having issues with that (if you noticed your ygg sometimes crashes and restarts, that's likely the reason why) | 20:56:33 |
| Arceliar | By memory leak, I mean I forgot to delete something from a map | 20:57:20 |
| GitHub | 📥 terminaldweller created new issue yggdrasil-network/yggdrasil-go#1216: "Test fails when run as root" | 21:56:05 |
|  @biklarbik:matrix.org joined the room. | 22:33:48 |
| @biklarbik:matrix.org left the room. | 22:35:12 |
| 13 Dec 2024 |
| Arceliar | In reply to @neilalexander:matrix.org
@room Yggdrasil 0.5.11 has been released! This release contains important fixes that should improve the stability of the network, so please upgrade your nodes as soon as possible. Please also pass on this message if you know any Yggdrasil users who may not see this notification. PSA, now that the release is out, of course I've found a bug. v0.5.11 is using quite a bit more idle bandwidth than intended, so if that's more of a problem for you than the occasional out-of-memory crash, then you may want to delay updating until we can figure out what's causing the issue and release a fix | 00:58:59 |
 jgoerzen | In reply to @Arceliar:matrix.org
PSA, now that the release is out, of course I've found a bug. v0.5.11 is using quite a bit more idle bandwidth than intended, so if that's more of a problem for you than the occasional out-of-memory crash, then you may want to delay updating until we can figure out what's causing the issue and release a fix Thanks for keeping us all updated! BTW, if I might make a small ask - it would be helpful if bugfix releases didn't make changes to go.mod. 0.5.11 introduces a dependency on a package not already in Debian, which will lead to delays getting it through. Thanks! | 04:12:51 |
| jgoerzen | If it's a big hassle, just ignore me and I'll work with it as usual | 04:23:45 |
