Releases: iCepa/Tor.framework
Releases · iCepa/Tor.framework
v400.6.1
Contains
- Tor 0.4.0.6
- libevent 2.1.11
- OpenSSL 1.1.1d
- liblzma 5.2.4
v400.5.2
Contains
- tor 0.4.0.5
- libevent 2.1.8
- OpenSSL 1.1.0k
- liblzma 5.2.3
Finally the MacOS build is fixed and this version contains one again!
v400.5.1
Contains
- tor 0.4.0.5
- libevent 2.1.8
- OpenSSL 1.1.0k
- liblzma 5.2.3
! iOS only !
v305.8.1
Contains
- tor 0.3.5.8
- libevent 2.1.8
- OpenSSL 1.1.0i
- liblzma 5.2.3
! iOS only !
v305.7.2
Contains
- tor 0.3.5.7
- libevent 2.1.8
- OpenSSL 1.1.0i
- liblzma 5.2.3
! iOS only !
v305.7.1
Contains
- tor 0.3.5.7
- libevent 2.1.8
- OpenSSL 1.1.0i
- liblzma 5.2.3
! iOS only !
v305.2.1
tor 0.3.1.8, libvent 2.1.8, openssl 1.1.0f, liblzma 5.2.3
v31.8.3 tor 0.3.1.8, build 3: now includes liblzma
tor 0.3.1.8, libvent 2.1.8, openssl 1.1.0f
r2 containing setconf methods
v31.8.1 --- tor 0.3.1.8, libvent 2.1.8, openssl 1.1.0f
need to tag releases since i want to try assembling pre-built copies of the framework. https://github.com/Carthage/Carthage#archive-prebuilt-frameworks-into-one-zip-file anyway. carthage needs semantic versions <https://github.com/Carthage/Carthage#tag-stable-releases> but does *not* support extra characters inside versions. Tor.framework will get a version tag based on tor's version where "0.3.1.8" becomes "v31.8.X", where X is a serial build number or somethin like that. dirty, but works for now.