Fedora/34 v0.9.9 upgrade #1947
Fedora/34 v0.9.9 upgrade #1947
Conversation
…t in publishing introsets and intro selection
* split up configure step and build step so that build steps goes all at once * update ci to use new build structure for android
…021-11-23 parallelize android build much better
…-28-2021 demote log statement levels
add notice to file as very out of date.
… only use ip6 after such an event. as a result dns queries stop working because we blackhole ip6 routes if exit mode is on. this prevents this case from being hit.
…dns-2021-12-03 disable ip6 upstream dns in libunbound
* document doxygen
fix readme, do not use static deps.
remove note in readme
correct cmake flag
remove pedantic separation in readme
remove old parts about macos from readme
on win32/apple reading packets from the interface does not count as an io operation. manually trigger pump on win32/apple to pretend that it is an io event. add platform quark function MaybeWakeUpperLayers on vpn::Interface to manaully wake up the other components on platforms that need that (ones on which packet io is not done via io events). on non linux platforms, use uv_prepare_t instead of uv_check_t as the former triggers before blocking for io, instead of after. this better matches linux's order of operations in libuv.
… a named constant.
…in-2021-12-07 Make windows work again
…n address range. mappings per ip stick to the same exit, each new ip is mapped to a random exit in the specified pool. make exit-auth multi value
client side exit node pooling
this allows you to use exit nodes without forcing routes over the interface, useful for using lokinet with an exit and selectively routing over the lokinet interface using an external socks proxy or binding to device explicitly. * make route poker configurable, defaults to enabled but allows disabling it on runtime if desired * add config option [network]:auto-routing to enable/disable route poker
Also rename the arg from loki_repo to oxen_repo
…erison-macros-2022-05-26 final fixups before 0.9.9 tag
…into rpm/patch
This reverts commit cdad3e7.
|
can we get @jagerman to do a once down of this to update it to 0.9.12 tag when we put that out? |
|
How far back in distros do you want to continue to support? We also didn't build for OpenSUSE or CentOS on v.0.9.11 and I didn't hear a public cry out for demand. I don't know if those are a "if you build it they will come" objective or just wait until people start asking for it. They build similarly to F35 but lack systemd-resolved F35 has thus presently require some manual post installation DNS tweaking to work. |
|
for debian we support back to old stable, not sure what fedora's release cycles are bound by but i know centos is even more long term than debian. |
|
Fedora has 2 releases / year. 13 months of support for each release. I'd argue if Fedora no longer supports it themselves it's time to move on. OpenSUSE and CentOS appear to be considerably longer between releases. |
Yup, that's our same policy for the short-lived Ubuntu releases (20.10, 21.04, 21.10, 22.10, etc.): we support them for the same 9 months that Ubuntu does. |
Merged to v0.9.9 upstream/stable
changes to versioning and deletion of associated patch.
revised dns patch.
revised SPEC file - SPEC for changes.