Oleg Girko

> So order-wise, the main issue is that it's if A sends a switch message (spanning tree stuff) to B, and then forwards a packet to B, it's not safe...

> It's worth noting that there are a number of additional considerations in v0.4 with regards to preventing races in path setups/teardowns etc which are not covered in the earlier...

Please don't use `/etc` subdirectory for the socket. Use `/run` instead. The `RuntimeDirectory=yggdrasil` directive in `systemd` service file will cause `/run/yggdrasil` directory to be created automatically on service startup. Also,...

Thank you @Conan-Kudo for starting this process. I have some remarks about this PR. * You've lost prefixes with square brackets for some of my commits' subjects (did you use...

No, `git am` is not very good idea. `git rebase` is much better. Porting gem changes is straightforward: 1. rebase, 2. resolve conflicts. There will definitely be conflicts in `Gemfile.lock`,...

> Why not just submit pull requests to update the gems in Fedora? Look [here](https://obs.infoserver.lv/project/monitor/obs:server:fedora:2.9) and see how many packages are in this project. Most of them are Ruby gems....

@M0ses: > I also started packaging missing packages here I already have all missing packages for OBS 2.9 in my [OBS project](https://obs.infoserver.lv/project/show/obs:server:fedora:2.9). It works pretty well: the OBS server itself...

@Conan-Kudo: > > Also, gpg2 in Fedora is 2.2, and it's incompatible with 2.1 in the way it stores private keys. It uses its own private key storage and doesn't...

> No, it's not compatible with gpg2 2.2. Attempt to create a private key results in error `gpg did not create private key`. This happens because `signd` creates params file...

I mean, I was using old version of `signd` when I encountered the problem with missing secring. I've just checked and found that current version in Fedora (although, not the...