<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="10"><package pkgid="f38c12694473f8fc09345f980c6fa1646953250d9a4780f1a1d90a85b183960c" name="libzypp-plugin-appdata" arch="noarch">
    <version epoch="0" ver="1.0.1" rel="2.1"/>

<changelog author="dimstar@opensuse.org" date="1414584000">- Split out of gnome-software, to be able to easier maintain
  updates.</changelog>
<changelog author="dimstar@opensuse.org" date="1414584001">- Bump version of libzypp-plugin-appdata to 1.0.1:
  + Disable the automatic metadata update mechanism, openSUSE 13.2
    metadata quality is not ready for this.
  + Inject offline generated metadata into the system, so that
    gnome-software has usable metadata.</changelog>

</package>
<package pkgid="b969c7b58ccccf05deef86ccd36a34a65ae0be5345c7320211991982156f3f3e" name="libzypp-plugin-appdata" arch="src">
    <version epoch="0" ver="1.0.1" rel="2.1"/>

<changelog author="dimstar@opensuse.org" date="1414584000">- Split out of gnome-software, to be able to easier maintain
  updates.</changelog>
<changelog author="dimstar@opensuse.org" date="1414584001">- Bump version of libzypp-plugin-appdata to 1.0.1:
  + Disable the automatic metadata update mechanism, openSUSE 13.2
    metadata quality is not ready for this.
  + Inject offline generated metadata into the system, so that
    gnome-software has usable metadata.</changelog>

</package>
<package pkgid="01662bdb6bcab0ad037983b3158dcf2e47b3d7a76c8572c16d2c9da9c128b994" name="pullin-flash-player" arch="i586">
    <version epoch="0" ver="12.3" rel="6.4.1"/>

<changelog author="coolo@suse.de" date="1225108800">- initial package</changelog>
<changelog author="coolo@suse.de" date="1228219200">- fixed typo in version</changelog>
<changelog author="coolo@suse.de" date="1239192000">- don't make it noarch
- recommend nspluginwrapper on x86_64 (bnc#480824)</changelog>
<changelog author="dmueller@suse.de" date="1275998400">- bump version to 11.3</changelog>
<changelog author="dmueller@suse.de" date="1279540800">- bump version to 11.4</changelog>
<changelog author="coolo@suse.com" date="1316520000">- bump version to 12.1</changelog>
<changelog author="coolo@suse.com" date="1320148800">- do not recommend nspluginwrapper</changelog>
<changelog author="coolo@suse.com" date="1346673600">- bump version to 12.2</changelog>
<changelog author="coolo@suse.com" date="1358510400">- bump version to 12.3</changelog>

</package>
<package pkgid="2c38fc0a44134434e71ff5871417675fd2f9bdca99933b61b598170ae24dc53c" name="pullin-flash-player" arch="src">
    <version epoch="0" ver="12.3" rel="6.4.1"/>

<changelog author="coolo@suse.de" date="1225108800">- initial package</changelog>
<changelog author="coolo@suse.de" date="1228219200">- fixed typo in version</changelog>
<changelog author="coolo@suse.de" date="1239192000">- don't make it noarch
- recommend nspluginwrapper on x86_64 (bnc#480824)</changelog>
<changelog author="dmueller@suse.de" date="1275998400">- bump version to 11.3</changelog>
<changelog author="dmueller@suse.de" date="1279540800">- bump version to 11.4</changelog>
<changelog author="coolo@suse.com" date="1316520000">- bump version to 12.1</changelog>
<changelog author="coolo@suse.com" date="1320148800">- do not recommend nspluginwrapper</changelog>
<changelog author="coolo@suse.com" date="1346673600">- bump version to 12.2</changelog>
<changelog author="coolo@suse.com" date="1358510400">- bump version to 12.3</changelog>

</package>
<package pkgid="59edec6f01d80b93c8442cc381025b5d9f903a1eb0501dc646db65fce0246440" name="pullin-flash-player" arch="x86_64">
    <version epoch="0" ver="12.3" rel="6.4.1"/>

<changelog author="coolo@suse.de" date="1225108800">- initial package</changelog>
<changelog author="coolo@suse.de" date="1228219200">- fixed typo in version</changelog>
<changelog author="coolo@suse.de" date="1239192000">- don't make it noarch
- recommend nspluginwrapper on x86_64 (bnc#480824)</changelog>
<changelog author="dmueller@suse.de" date="1275998400">- bump version to 11.3</changelog>
<changelog author="dmueller@suse.de" date="1279540800">- bump version to 11.4</changelog>
<changelog author="coolo@suse.com" date="1316520000">- bump version to 12.1</changelog>
<changelog author="coolo@suse.com" date="1320148800">- do not recommend nspluginwrapper</changelog>
<changelog author="coolo@suse.com" date="1346673600">- bump version to 12.2</changelog>
<changelog author="coolo@suse.com" date="1358510400">- bump version to 12.3</changelog>

</package>
<package pkgid="fca64e922f08d7e9582f102e6fe677c8adca56ff1143f141bbe70d6e58ad8ad0" name="pullin-fluendo-mp3" arch="noarch">
    <version epoch="0" ver="13.2" rel="11.4.1"/>

<changelog author="coolo@suse.de" date="1225108800">- initial package</changelog>
<changelog author="coolo@novell.com" date="1277121600">- bump to 11.3</changelog>
<changelog author="vuntz@opensuse.org" date="1277121601">- Fix a typo in README.</changelog>
<changelog author="vuntz@opensuse.org" date="1277812800">- gst-fluendo-mp3 was renamed to gstreamer-0_10-fluendo-mp3 to
  follow package conventions for gstreamer packages, so update
  Recommends here.</changelog>
<changelog author="coolo@suse.com" date="1316520000">- bump version to 12.1</changelog>
<changelog author="dimstar@opensuse.org" date="1414670400">- Bump version to 13.2.
- Also recommend gstreamer-fluendo-mp3: MP3 support on GStramer 1.0
  based players is also wanted.</changelog>

</package>
<package pkgid="71490674c46240d532c8a3da9dc9c9bbddbb10dd6522d864072ac4917186dd46" name="pullin-fluendo-mp3" arch="src">
    <version epoch="0" ver="13.2" rel="11.4.1"/>

<changelog author="coolo@suse.de" date="1225108800">- initial package</changelog>
<changelog author="coolo@novell.com" date="1277121600">- bump to 11.3</changelog>
<changelog author="vuntz@opensuse.org" date="1277121601">- Fix a typo in README.</changelog>
<changelog author="vuntz@opensuse.org" date="1277812800">- gst-fluendo-mp3 was renamed to gstreamer-0_10-fluendo-mp3 to
  follow package conventions for gstreamer packages, so update
  Recommends here.</changelog>
<changelog author="coolo@suse.com" date="1316520000">- bump version to 12.1</changelog>
<changelog author="dimstar@opensuse.org" date="1414670400">- Bump version to 13.2.
- Also recommend gstreamer-fluendo-mp3: MP3 support on GStramer 1.0
  based players is also wanted.</changelog>

</package>

<package pkgid="7f12670b7ee5b6f23d5c1a3b0f20eb7e57347e3f2d7f2c1f02a5876af727396c" name="tor" arch="i586">
    <version epoch="0" ver="0.2.4.25" rel="4.1"/>

<changelog author="andreas.stieger@gmx.de" date="1339761600">- add tor-0.2.2.37-logrotate.patch : add su option to logrotate to
  fix W: suse-logrotate-user-writable-log-dir in Factory</changelog>
<changelog author="andreas.stieger@gmx.de" date="1345464000">- update to 0.2.2.38 [bnc#776642]
  Changes in version 0.2.2.38 - 2012-08-12
  Tor 0.2.2.38 fixes a rare race condition that can crash exit relays;
  fixes a remotely triggerable crash bug; and fixes a timing attack that
  could in theory leak path information.
  o Security fixes:
  - Avoid read-from-freed-memory and double-free bugs that could occur
    when a DNS request fails while launching it.
    CVE-2012-3517
  - Avoid an uninitialized memory read when reading a vote or consensus
    document that has an unrecognized flavor name. This read could
    lead to a remote crash bug.
    CVE-2012-3518
  - Try to leak less information about what relays a client is
    choosing to a side-channel attacker. Previously, a Tor client would
    stop iterating through the list of available relays as soon as it
    had chosen one, thus finishing a little earlier when it picked
    a router earlier in the list. If an attacker can recover this
    timing information (nontrivial but not proven to be impossible),
    they could learn some coarse-grained information about which relays
    a client was picking (middle nodes in particular are likelier to
    be affected than exits). The timing attack might be mitigated by
    other factors, but it's best not to take chances.
    CVE-2012-3519</changelog>
<changelog author="andreas.stieger@gmx.de" date="1347710400">- update to 0.2.2.39 [bnc#780620]
  Changes in version 0.2.2.39 - 2012-09-11
  Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
  assertions.
  o Security fixes:
  - Fix an assertion failure in tor_timegm() that could be triggered
    by a badly formatted directory object.
    CVE-2012-4922
  - Do not crash when comparing an address with port value 0 to an
    address policy. This bug could have been used to cause a remote
    assertion failure by or against directory authorities, or to
    allow some applications to crash clients.
    CVE-2012-4419</changelog>
<changelog author="dimstar@opensuse.org" date="1353412800">- Fix useradd invocation: -o is useless without -u and newer
  versions of pwdutils/shadowutils fail on this now.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1354017600">- update to 0.2.3.25, the first stable release in the 0.2.3 branch
  + significantly reduced directory overhead (via microdescriptors)
  + enormous crypto performance improvements for fast relays on new
    enough hardware
  + new v3 TLS handshake protocol that can better resist
    fingerprinting
  + support for protocol obfuscation plugins (pluggable transports)
  + better scalability for hidden services
  + IPv6 support for bridges
  + performance improvements
  + new "stream isolation" design to isolate different applications
    on different circuits
  + many stability, security, and privacy fixes
  + Complete list of changes enumerated in:
    https://lists.torproject.org/pipermail/tor-talk/2012-November/026554.html
    https://gitweb.torproject.org/tor.git/blob/267c0e5aa14deeb2ca0d7997b4ef5a5c2bbf5fd4:/ReleaseNotes
  + Tear down the circuit when receiving an unexpected SENDME cell.
    [bnc#791374] CVE-2012-5573
- build using --enable-bufferevents provided by Libevent 2.0.13</changelog>
<changelog author="andreas.stieger@gmx.de" date="1369396800">- add systemd support
- verify source tarball signature</changelog>
<changelog author="andreas.stieger@gmx.de" date="1380974400">- tor-0.2.4.17-rc
- major features in 0.2.4.x:
  - improved client resilience
  - support better link encryption with forward secrecy
  - new NTor circuit handshake
  - change relay queue for circuit create requests from size-based
    limit to time-based limit
  - many bug fixes and minor features</changelog>
<changelog author="andreas.stieger@gmx.de" date="1386417600">- tor-0.2.4.18-rc, improves stability, performance, and better
  handling of edge cases.
- Major features:
  - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
- Major bugfixes:
  - No longer stop reading or writing on cpuworker connections when
    our rate limiting buckets go empty.
  - If we are unable to save a microdescriptor to the journal, do not
    drop it from memory and then reattempt downloading it.
  - Stop trying to bootstrap all our directory information from
    only our first guard.
  - The new channel code sometimes lost track of in-progress circuits,
    causing long-running clients to stop building new circuits.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1387022400">- Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
  a new circuit handshake and link encryption that use ECC to provide
  better security and efficiency; makes relays better manage circuit
  creation requests; uses "directory guards" to reduce client enumeration
  risks; makes bridges collect and report statistics about the pluggable
  transports they support; cleans up and improves our geoip database;
  gets much closer to IPv6 support for clients, bridges, and relays; makes
  directory authorities use measured bandwidths rather than advertised
  ones when computing flags and thresholds; disables client-side DNS
  caching to reduce tracking risks; and fixes a big bug in bridge
  reachability testing. This release introduces two new design
  abstractions in the code: a new "channel" abstraction between circuits
  and or_connections to allow for implementing alternate relay-to-relay
  transports, and a new "circuitmux" abstraction storing the queue of
  circuits for a channel. The release also includes many stability,
  security, and privacy fixes.
- full changelog relative to 0.2.3.x and 0.2.4.x RC series:
  https://gitweb.torproject.org/tor.git?a=blob_plain;hb=release-0.2.4;f=ReleaseNotes</changelog>
<changelog author="andreas.stieger@gmx.de" date="1388145600">- tor 0.2.4.20
  fixes potentially poor random number generation for users who
  1) use OpenSSL 1.0.0 or later,
  2) set "HardwareAccel 1" in their torrc file,
  3) have "Sandy Bridge" or "Ivy Bridge" Intel processors
  and
  4) have no state file in their DataDirectory (as would happen on
  first start).
  Users who generated relay or hidden service identity keys in such
  a situation should discard them and generate new ones.
  No 2 is not the default configuration for openSUSE.
  [bnc#859421] [CVE-2013-7295]
  This release also fixes a logic error that caused Tor clients to build
  many more preemptive circuits than they actually need.
- Major bugfixes:
  - Do not allow OpenSSL engines to replace the PRNG, even when
    HardwareAccel is set. The only default builtin PRNG engine uses
    the Intel RDRAND instruction to replace the entire PRNG, and
    ignores all attempts to seed it with more entropy. That's
    cryptographically stupid: the right response to a new alleged
    entropy source is never to discard all previously used entropy
    sources. Fixes bug 10402; works around behavior introduced in
    OpenSSL 1.0.0.
  - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
    address.
  - Avoid launching spurious extra circuits when a stream is pending.
    This fixes a bug where any circuit that _wasn't_ unusable for new
    streams would be treated as if it were, causing extra circuits to
    be launched.
- Minor bugfixes:
  - Avoid a crash bug when starting with a corrupted microdescriptor
    cache file.
  - If we fail to dump a previously cached microdescriptor to disk, avoid
    freeing duplicate data later on.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1390219200">- redaction of 0.2.4.20 changelog to include bug and CVE references</changelog>
<changelog author="andreas.stieger@gmx.de" date="1394107200">- tor 0.2.4.21
  Further improves security against potential adversaries who find
  breaking 1024-bit crypto doable, and backports several stability
  and robustness patches from the 0.2.5 branch.
- Major features (client security):
  - When we choose a path for a 3-hop circuit, make sure it contains
    at least one relay that supports the NTor circuit extension
    handshake. Otherwise, there is a chance that we're building
    a circuit that's worth attacking by an adversary who finds
    breaking 1024-bit crypto doable, and that chance changes the game
    theory.
- Major bugfixes:
  - Do not treat streams that fail with reason
    END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
    since it could also indicate an ENETUNREACH connection error
- packaging changes:
  - remove init script shadowing systemd unit
  - general cleanup</changelog>
<changelog author="mook.moz+com.novell@gmail.com" date="1397908800">- Add tor-fw-helper for UPnP port forwarding; not used by default</changelog>
<changelog author="andreas.stieger@gmx.de" date="1400328000">- tor 0.2.4.22:
  Backports numerous high-priority fixes. These include blocking
  all authority signing keys that may have been affected by the
  OpenSSL "heartbleed" bug, choosing a far more secure set of TLS
  ciphersuites by default, closing a couple of memory leaks that
  could be used to run a target relay out of RAM.
- Major features (security)
  - Block authority signing keys that were used on authorities
    vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160).
- Major bugfixes (security, OOM):
  - Fix a memory leak that could occur if a microdescriptor parse
    fails during the tokenizing step.
- Major bugfixes (TLS cipher selection):
  - The relay ciphersuite list is now generated automatically based
    on uniform criteria, and includes all OpenSSL ciphersuites with
    acceptable strength and forward secrecy.
  - Relays now trust themselves to have a better view than clients
    of which TLS ciphersuites are better than others.
  - Clients now try to advertise the same list of ciphersuites as
    Firefox 28.
- further minor bug fixes, see ChangeLog
- fix logrotate on systemd-only setups without init scripts,
  work tor-0.2.2.37-logrotate.patch to tor-0.2.4.x-logrotate.patch</changelog>
<changelog author="andreas.stieger@gmx.de" date="1402056000">- do not own /var/run/tor for pid file, fixing Factory build</changelog>
<changelog author="andreas.stieger@gmx.de" date="1406721600">- Tor 0.2.4.23 [bnc#889688] [CVE-2014-5117]
  Slows down the risk from guard rotation and backports several
  important fixes from the Tor 0.2.5 alpha release series.
- Major features:
  - Clients now look at the "usecreatefast" consensus parameter to
    decide whether to use CREATE_FAST or CREATE cells for the first hop
    of their circuit. This approach can improve security on connections
    where Tor's circuit handshake is stronger than the available TLS
    connection security levels, but the tradeoff is more computational
    load on guard relays.
  - Make the number of entry guards configurable via a new
    NumEntryGuards consensus parameter, and the number of directory
    guards configurable via a new NumDirectoryGuards consensus
    parameter.
- Major bugfixes:
  - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
    implementation that caused incorrect results on 32-bit
    implementations when certain malformed inputs were used along with
    a small class of private ntor keys.
- Minor bugfixes:
  - Warn and drop the circuit if we receive an inbound 'relay early'
    cell.
  - Correct a confusing error message when trying to extend a circuit
    via the control protocol but we don't know a descriptor or
    microdescriptor for one of the specified relays.
  - Avoid an illegal read from stack when initializing the TLS module
    using a version of OpenSSL without all of the ciphers used by the
    v2 link handshake.</changelog>
<changelog author="wagner-thomas@gmx.at" date="1408363200">- Added config file for firewall</changelog>
<changelog author="andreas.stieger@gmx.de" date="1411214400">- disable build with experimental feature bufferevents [bnc#897113]</changelog>
<changelog author="andreas.stieger@gmx.de" date="1411560000">- tor 0.2.4.24 [bnc#898268]
  Fixes a bug that affects consistency and speed when connecting to
  hidden services, and it updates the location of one of the
  directory authorities.
- Major bugfixes:
  * Clients now send the correct address for their chosen rendezvous
    point when trying to access a hidden service.
- Directory authority changes:
  * Change IP address for gabelmoo (v3 directory authority).
- Minor features (geoip):
  * Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
    Country database.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1414065600">- tor 0.2.4.25 [boo#902476]
  Disables SSL3 in response to the recent "POODLE" attack (even
  though POODLE does not affect Tor).
  It also works around a crash bug caused by some operating systems'
  response to the "POODLE" attack (which does affect Tor).
  - Disable support for SSLv3.
  - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
    1.0.1j, built with the 'no-ssl3' configuration option.</changelog>

</package>

<package pkgid="b636369fbc56b7c9fc22b6847a8ebcf7e0823b073cb40ada5f416ef857476a82" name="tor" arch="src">
    <version epoch="0" ver="0.2.4.25" rel="4.1"/>

<changelog author="andreas.stieger@gmx.de" date="1339761600">- add tor-0.2.2.37-logrotate.patch : add su option to logrotate to
  fix W: suse-logrotate-user-writable-log-dir in Factory</changelog>
<changelog author="andreas.stieger@gmx.de" date="1345464000">- update to 0.2.2.38 [bnc#776642]
  Changes in version 0.2.2.38 - 2012-08-12
  Tor 0.2.2.38 fixes a rare race condition that can crash exit relays;
  fixes a remotely triggerable crash bug; and fixes a timing attack that
  could in theory leak path information.
  o Security fixes:
  - Avoid read-from-freed-memory and double-free bugs that could occur
    when a DNS request fails while launching it.
    CVE-2012-3517
  - Avoid an uninitialized memory read when reading a vote or consensus
    document that has an unrecognized flavor name. This read could
    lead to a remote crash bug.
    CVE-2012-3518
  - Try to leak less information about what relays a client is
    choosing to a side-channel attacker. Previously, a Tor client would
    stop iterating through the list of available relays as soon as it
    had chosen one, thus finishing a little earlier when it picked
    a router earlier in the list. If an attacker can recover this
    timing information (nontrivial but not proven to be impossible),
    they could learn some coarse-grained information about which relays
    a client was picking (middle nodes in particular are likelier to
    be affected than exits). The timing attack might be mitigated by
    other factors, but it's best not to take chances.
    CVE-2012-3519</changelog>
<changelog author="andreas.stieger@gmx.de" date="1347710400">- update to 0.2.2.39 [bnc#780620]
  Changes in version 0.2.2.39 - 2012-09-11
  Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
  assertions.
  o Security fixes:
  - Fix an assertion failure in tor_timegm() that could be triggered
    by a badly formatted directory object.
    CVE-2012-4922
  - Do not crash when comparing an address with port value 0 to an
    address policy. This bug could have been used to cause a remote
    assertion failure by or against directory authorities, or to
    allow some applications to crash clients.
    CVE-2012-4419</changelog>
<changelog author="dimstar@opensuse.org" date="1353412800">- Fix useradd invocation: -o is useless without -u and newer
  versions of pwdutils/shadowutils fail on this now.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1354017600">- update to 0.2.3.25, the first stable release in the 0.2.3 branch
  + significantly reduced directory overhead (via microdescriptors)
  + enormous crypto performance improvements for fast relays on new
    enough hardware
  + new v3 TLS handshake protocol that can better resist
    fingerprinting
  + support for protocol obfuscation plugins (pluggable transports)
  + better scalability for hidden services
  + IPv6 support for bridges
  + performance improvements
  + new "stream isolation" design to isolate different applications
    on different circuits
  + many stability, security, and privacy fixes
  + Complete list of changes enumerated in:
    https://lists.torproject.org/pipermail/tor-talk/2012-November/026554.html
    https://gitweb.torproject.org/tor.git/blob/267c0e5aa14deeb2ca0d7997b4ef5a5c2bbf5fd4:/ReleaseNotes
  + Tear down the circuit when receiving an unexpected SENDME cell.
    [bnc#791374] CVE-2012-5573
- build using --enable-bufferevents provided by Libevent 2.0.13</changelog>
<changelog author="andreas.stieger@gmx.de" date="1369396800">- add systemd support
- verify source tarball signature</changelog>
<changelog author="andreas.stieger@gmx.de" date="1380974400">- tor-0.2.4.17-rc
- major features in 0.2.4.x:
  - improved client resilience
  - support better link encryption with forward secrecy
  - new NTor circuit handshake
  - change relay queue for circuit create requests from size-based
    limit to time-based limit
  - many bug fixes and minor features</changelog>
<changelog author="andreas.stieger@gmx.de" date="1386417600">- tor-0.2.4.18-rc, improves stability, performance, and better
  handling of edge cases.
- Major features:
  - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
- Major bugfixes:
  - No longer stop reading or writing on cpuworker connections when
    our rate limiting buckets go empty.
  - If we are unable to save a microdescriptor to the journal, do not
    drop it from memory and then reattempt downloading it.
  - Stop trying to bootstrap all our directory information from
    only our first guard.
  - The new channel code sometimes lost track of in-progress circuits,
    causing long-running clients to stop building new circuits.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1387022400">- Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
  a new circuit handshake and link encryption that use ECC to provide
  better security and efficiency; makes relays better manage circuit
  creation requests; uses "directory guards" to reduce client enumeration
  risks; makes bridges collect and report statistics about the pluggable
  transports they support; cleans up and improves our geoip database;
  gets much closer to IPv6 support for clients, bridges, and relays; makes
  directory authorities use measured bandwidths rather than advertised
  ones when computing flags and thresholds; disables client-side DNS
  caching to reduce tracking risks; and fixes a big bug in bridge
  reachability testing. This release introduces two new design
  abstractions in the code: a new "channel" abstraction between circuits
  and or_connections to allow for implementing alternate relay-to-relay
  transports, and a new "circuitmux" abstraction storing the queue of
  circuits for a channel. The release also includes many stability,
  security, and privacy fixes.
- full changelog relative to 0.2.3.x and 0.2.4.x RC series:
  https://gitweb.torproject.org/tor.git?a=blob_plain;hb=release-0.2.4;f=ReleaseNotes</changelog>
<changelog author="andreas.stieger@gmx.de" date="1388145600">- tor 0.2.4.20
  fixes potentially poor random number generation for users who
  1) use OpenSSL 1.0.0 or later,
  2) set "HardwareAccel 1" in their torrc file,
  3) have "Sandy Bridge" or "Ivy Bridge" Intel processors
  and
  4) have no state file in their DataDirectory (as would happen on
  first start).
  Users who generated relay or hidden service identity keys in such
  a situation should discard them and generate new ones.
  No 2 is not the default configuration for openSUSE.
  [bnc#859421] [CVE-2013-7295]
  This release also fixes a logic error that caused Tor clients to build
  many more preemptive circuits than they actually need.
- Major bugfixes:
  - Do not allow OpenSSL engines to replace the PRNG, even when
    HardwareAccel is set. The only default builtin PRNG engine uses
    the Intel RDRAND instruction to replace the entire PRNG, and
    ignores all attempts to seed it with more entropy. That's
    cryptographically stupid: the right response to a new alleged
    entropy source is never to discard all previously used entropy
    sources. Fixes bug 10402; works around behavior introduced in
    OpenSSL 1.0.0.
  - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
    address.
  - Avoid launching spurious extra circuits when a stream is pending.
    This fixes a bug where any circuit that _wasn't_ unusable for new
    streams would be treated as if it were, causing extra circuits to
    be launched.
- Minor bugfixes:
  - Avoid a crash bug when starting with a corrupted microdescriptor
    cache file.
  - If we fail to dump a previously cached microdescriptor to disk, avoid
    freeing duplicate data later on.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1390219200">- redaction of 0.2.4.20 changelog to include bug and CVE references</changelog>
<changelog author="andreas.stieger@gmx.de" date="1394107200">- tor 0.2.4.21
  Further improves security against potential adversaries who find
  breaking 1024-bit crypto doable, and backports several stability
  and robustness patches from the 0.2.5 branch.
- Major features (client security):
  - When we choose a path for a 3-hop circuit, make sure it contains
    at least one relay that supports the NTor circuit extension
    handshake. Otherwise, there is a chance that we're building
    a circuit that's worth attacking by an adversary who finds
    breaking 1024-bit crypto doable, and that chance changes the game
    theory.
- Major bugfixes:
  - Do not treat streams that fail with reason
    END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
    since it could also indicate an ENETUNREACH connection error
- packaging changes:
  - remove init script shadowing systemd unit
  - general cleanup</changelog>
<changelog author="mook.moz+com.novell@gmail.com" date="1397908800">- Add tor-fw-helper for UPnP port forwarding; not used by default</changelog>
<changelog author="andreas.stieger@gmx.de" date="1400328000">- tor 0.2.4.22:
  Backports numerous high-priority fixes. These include blocking
  all authority signing keys that may have been affected by the
  OpenSSL "heartbleed" bug, choosing a far more secure set of TLS
  ciphersuites by default, closing a couple of memory leaks that
  could be used to run a target relay out of RAM.
- Major features (security)
  - Block authority signing keys that were used on authorities
    vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160).
- Major bugfixes (security, OOM):
  - Fix a memory leak that could occur if a microdescriptor parse
    fails during the tokenizing step.
- Major bugfixes (TLS cipher selection):
  - The relay ciphersuite list is now generated automatically based
    on uniform criteria, and includes all OpenSSL ciphersuites with
    acceptable strength and forward secrecy.
  - Relays now trust themselves to have a better view than clients
    of which TLS ciphersuites are better than others.
  - Clients now try to advertise the same list of ciphersuites as
    Firefox 28.
- further minor bug fixes, see ChangeLog
- fix logrotate on systemd-only setups without init scripts,
  work tor-0.2.2.37-logrotate.patch to tor-0.2.4.x-logrotate.patch</changelog>
<changelog author="andreas.stieger@gmx.de" date="1402056000">- do not own /var/run/tor for pid file, fixing Factory build</changelog>
<changelog author="andreas.stieger@gmx.de" date="1406721600">- Tor 0.2.4.23 [bnc#889688] [CVE-2014-5117]
  Slows down the risk from guard rotation and backports several
  important fixes from the Tor 0.2.5 alpha release series.
- Major features:
  - Clients now look at the "usecreatefast" consensus parameter to
    decide whether to use CREATE_FAST or CREATE cells for the first hop
    of their circuit. This approach can improve security on connections
    where Tor's circuit handshake is stronger than the available TLS
    connection security levels, but the tradeoff is more computational
    load on guard relays.
  - Make the number of entry guards configurable via a new
    NumEntryGuards consensus parameter, and the number of directory
    guards configurable via a new NumDirectoryGuards consensus
    parameter.
- Major bugfixes:
  - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
    implementation that caused incorrect results on 32-bit
    implementations when certain malformed inputs were used along with
    a small class of private ntor keys.
- Minor bugfixes:
  - Warn and drop the circuit if we receive an inbound 'relay early'
    cell.
  - Correct a confusing error message when trying to extend a circuit
    via the control protocol but we don't know a descriptor or
    microdescriptor for one of the specified relays.
  - Avoid an illegal read from stack when initializing the TLS module
    using a version of OpenSSL without all of the ciphers used by the
    v2 link handshake.</changelog>
<changelog author="wagner-thomas@gmx.at" date="1408363200">- Added config file for firewall</changelog>
<changelog author="andreas.stieger@gmx.de" date="1411214400">- disable build with experimental feature bufferevents [bnc#897113]</changelog>
<changelog author="andreas.stieger@gmx.de" date="1411560000">- tor 0.2.4.24 [bnc#898268]
  Fixes a bug that affects consistency and speed when connecting to
  hidden services, and it updates the location of one of the
  directory authorities.
- Major bugfixes:
  * Clients now send the correct address for their chosen rendezvous
    point when trying to access a hidden service.
- Directory authority changes:
  * Change IP address for gabelmoo (v3 directory authority).
- Minor features (geoip):
  * Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
    Country database.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1414065600">- tor 0.2.4.25 [boo#902476]
  Disables SSL3 in response to the recent "POODLE" attack (even
  though POODLE does not affect Tor).
  It also works around a crash bug caused by some operating systems'
  response to the "POODLE" attack (which does affect Tor).
  - Disable support for SSLv3.
  - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
    1.0.1j, built with the 'no-ssl3' configuration option.</changelog>

</package>

<package pkgid="198be5fa3411101b8a15125bd5028da65de10e8e15a812fba2ceff2216f9224a" name="tor" arch="x86_64">
    <version epoch="0" ver="0.2.4.25" rel="4.1"/>

<changelog author="andreas.stieger@gmx.de" date="1339761600">- add tor-0.2.2.37-logrotate.patch : add su option to logrotate to
  fix W: suse-logrotate-user-writable-log-dir in Factory</changelog>
<changelog author="andreas.stieger@gmx.de" date="1345464000">- update to 0.2.2.38 [bnc#776642]
  Changes in version 0.2.2.38 - 2012-08-12
  Tor 0.2.2.38 fixes a rare race condition that can crash exit relays;
  fixes a remotely triggerable crash bug; and fixes a timing attack that
  could in theory leak path information.
  o Security fixes:
  - Avoid read-from-freed-memory and double-free bugs that could occur
    when a DNS request fails while launching it.
    CVE-2012-3517
  - Avoid an uninitialized memory read when reading a vote or consensus
    document that has an unrecognized flavor name. This read could
    lead to a remote crash bug.
    CVE-2012-3518
  - Try to leak less information about what relays a client is
    choosing to a side-channel attacker. Previously, a Tor client would
    stop iterating through the list of available relays as soon as it
    had chosen one, thus finishing a little earlier when it picked
    a router earlier in the list. If an attacker can recover this
    timing information (nontrivial but not proven to be impossible),
    they could learn some coarse-grained information about which relays
    a client was picking (middle nodes in particular are likelier to
    be affected than exits). The timing attack might be mitigated by
    other factors, but it's best not to take chances.
    CVE-2012-3519</changelog>
<changelog author="andreas.stieger@gmx.de" date="1347710400">- update to 0.2.2.39 [bnc#780620]
  Changes in version 0.2.2.39 - 2012-09-11
  Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
  assertions.
  o Security fixes:
  - Fix an assertion failure in tor_timegm() that could be triggered
    by a badly formatted directory object.
    CVE-2012-4922
  - Do not crash when comparing an address with port value 0 to an
    address policy. This bug could have been used to cause a remote
    assertion failure by or against directory authorities, or to
    allow some applications to crash clients.
    CVE-2012-4419</changelog>
<changelog author="dimstar@opensuse.org" date="1353412800">- Fix useradd invocation: -o is useless without -u and newer
  versions of pwdutils/shadowutils fail on this now.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1354017600">- update to 0.2.3.25, the first stable release in the 0.2.3 branch
  + significantly reduced directory overhead (via microdescriptors)
  + enormous crypto performance improvements for fast relays on new
    enough hardware
  + new v3 TLS handshake protocol that can better resist
    fingerprinting
  + support for protocol obfuscation plugins (pluggable transports)
  + better scalability for hidden services
  + IPv6 support for bridges
  + performance improvements
  + new "stream isolation" design to isolate different applications
    on different circuits
  + many stability, security, and privacy fixes
  + Complete list of changes enumerated in:
    https://lists.torproject.org/pipermail/tor-talk/2012-November/026554.html
    https://gitweb.torproject.org/tor.git/blob/267c0e5aa14deeb2ca0d7997b4ef5a5c2bbf5fd4:/ReleaseNotes
  + Tear down the circuit when receiving an unexpected SENDME cell.
    [bnc#791374] CVE-2012-5573
- build using --enable-bufferevents provided by Libevent 2.0.13</changelog>
<changelog author="andreas.stieger@gmx.de" date="1369396800">- add systemd support
- verify source tarball signature</changelog>
<changelog author="andreas.stieger@gmx.de" date="1380974400">- tor-0.2.4.17-rc
- major features in 0.2.4.x:
  - improved client resilience
  - support better link encryption with forward secrecy
  - new NTor circuit handshake
  - change relay queue for circuit create requests from size-based
    limit to time-based limit
  - many bug fixes and minor features</changelog>
<changelog author="andreas.stieger@gmx.de" date="1386417600">- tor-0.2.4.18-rc, improves stability, performance, and better
  handling of edge cases.
- Major features:
  - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
- Major bugfixes:
  - No longer stop reading or writing on cpuworker connections when
    our rate limiting buckets go empty.
  - If we are unable to save a microdescriptor to the journal, do not
    drop it from memory and then reattempt downloading it.
  - Stop trying to bootstrap all our directory information from
    only our first guard.
  - The new channel code sometimes lost track of in-progress circuits,
    causing long-running clients to stop building new circuits.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1387022400">- Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
  a new circuit handshake and link encryption that use ECC to provide
  better security and efficiency; makes relays better manage circuit
  creation requests; uses "directory guards" to reduce client enumeration
  risks; makes bridges collect and report statistics about the pluggable
  transports they support; cleans up and improves our geoip database;
  gets much closer to IPv6 support for clients, bridges, and relays; makes
  directory authorities use measured bandwidths rather than advertised
  ones when computing flags and thresholds; disables client-side DNS
  caching to reduce tracking risks; and fixes a big bug in bridge
  reachability testing. This release introduces two new design
  abstractions in the code: a new "channel" abstraction between circuits
  and or_connections to allow for implementing alternate relay-to-relay
  transports, and a new "circuitmux" abstraction storing the queue of
  circuits for a channel. The release also includes many stability,
  security, and privacy fixes.
- full changelog relative to 0.2.3.x and 0.2.4.x RC series:
  https://gitweb.torproject.org/tor.git?a=blob_plain;hb=release-0.2.4;f=ReleaseNotes</changelog>
<changelog author="andreas.stieger@gmx.de" date="1388145600">- tor 0.2.4.20
  fixes potentially poor random number generation for users who
  1) use OpenSSL 1.0.0 or later,
  2) set "HardwareAccel 1" in their torrc file,
  3) have "Sandy Bridge" or "Ivy Bridge" Intel processors
  and
  4) have no state file in their DataDirectory (as would happen on
  first start).
  Users who generated relay or hidden service identity keys in such
  a situation should discard them and generate new ones.
  No 2 is not the default configuration for openSUSE.
  [bnc#859421] [CVE-2013-7295]
  This release also fixes a logic error that caused Tor clients to build
  many more preemptive circuits than they actually need.
- Major bugfixes:
  - Do not allow OpenSSL engines to replace the PRNG, even when
    HardwareAccel is set. The only default builtin PRNG engine uses
    the Intel RDRAND instruction to replace the entire PRNG, and
    ignores all attempts to seed it with more entropy. That's
    cryptographically stupid: the right response to a new alleged
    entropy source is never to discard all previously used entropy
    sources. Fixes bug 10402; works around behavior introduced in
    OpenSSL 1.0.0.
  - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
    address.
  - Avoid launching spurious extra circuits when a stream is pending.
    This fixes a bug where any circuit that _wasn't_ unusable for new
    streams would be treated as if it were, causing extra circuits to
    be launched.
- Minor bugfixes:
  - Avoid a crash bug when starting with a corrupted microdescriptor
    cache file.
  - If we fail to dump a previously cached microdescriptor to disk, avoid
    freeing duplicate data later on.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1390219200">- redaction of 0.2.4.20 changelog to include bug and CVE references</changelog>
<changelog author="andreas.stieger@gmx.de" date="1394107200">- tor 0.2.4.21
  Further improves security against potential adversaries who find
  breaking 1024-bit crypto doable, and backports several stability
  and robustness patches from the 0.2.5 branch.
- Major features (client security):
  - When we choose a path for a 3-hop circuit, make sure it contains
    at least one relay that supports the NTor circuit extension
    handshake. Otherwise, there is a chance that we're building
    a circuit that's worth attacking by an adversary who finds
    breaking 1024-bit crypto doable, and that chance changes the game
    theory.
- Major bugfixes:
  - Do not treat streams that fail with reason
    END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
    since it could also indicate an ENETUNREACH connection error
- packaging changes:
  - remove init script shadowing systemd unit
  - general cleanup</changelog>
<changelog author="mook.moz+com.novell@gmail.com" date="1397908800">- Add tor-fw-helper for UPnP port forwarding; not used by default</changelog>
<changelog author="andreas.stieger@gmx.de" date="1400328000">- tor 0.2.4.22:
  Backports numerous high-priority fixes. These include blocking
  all authority signing keys that may have been affected by the
  OpenSSL "heartbleed" bug, choosing a far more secure set of TLS
  ciphersuites by default, closing a couple of memory leaks that
  could be used to run a target relay out of RAM.
- Major features (security)
  - Block authority signing keys that were used on authorities
    vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160).
- Major bugfixes (security, OOM):
  - Fix a memory leak that could occur if a microdescriptor parse
    fails during the tokenizing step.
- Major bugfixes (TLS cipher selection):
  - The relay ciphersuite list is now generated automatically based
    on uniform criteria, and includes all OpenSSL ciphersuites with
    acceptable strength and forward secrecy.
  - Relays now trust themselves to have a better view than clients
    of which TLS ciphersuites are better than others.
  - Clients now try to advertise the same list of ciphersuites as
    Firefox 28.
- further minor bug fixes, see ChangeLog
- fix logrotate on systemd-only setups without init scripts,
  work tor-0.2.2.37-logrotate.patch to tor-0.2.4.x-logrotate.patch</changelog>
<changelog author="andreas.stieger@gmx.de" date="1402056000">- do not own /var/run/tor for pid file, fixing Factory build</changelog>
<changelog author="andreas.stieger@gmx.de" date="1406721600">- Tor 0.2.4.23 [bnc#889688] [CVE-2014-5117]
  Slows down the risk from guard rotation and backports several
  important fixes from the Tor 0.2.5 alpha release series.
- Major features:
  - Clients now look at the "usecreatefast" consensus parameter to
    decide whether to use CREATE_FAST or CREATE cells for the first hop
    of their circuit. This approach can improve security on connections
    where Tor's circuit handshake is stronger than the available TLS
    connection security levels, but the tradeoff is more computational
    load on guard relays.
  - Make the number of entry guards configurable via a new
    NumEntryGuards consensus parameter, and the number of directory
    guards configurable via a new NumDirectoryGuards consensus
    parameter.
- Major bugfixes:
  - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
    implementation that caused incorrect results on 32-bit
    implementations when certain malformed inputs were used along with
    a small class of private ntor keys.
- Minor bugfixes:
  - Warn and drop the circuit if we receive an inbound 'relay early'
    cell.
  - Correct a confusing error message when trying to extend a circuit
    via the control protocol but we don't know a descriptor or
    microdescriptor for one of the specified relays.
  - Avoid an illegal read from stack when initializing the TLS module
    using a version of OpenSSL without all of the ciphers used by the
    v2 link handshake.</changelog>
<changelog author="wagner-thomas@gmx.at" date="1408363200">- Added config file for firewall</changelog>
<changelog author="andreas.stieger@gmx.de" date="1411214400">- disable build with experimental feature bufferevents [bnc#897113]</changelog>
<changelog author="andreas.stieger@gmx.de" date="1411560000">- tor 0.2.4.24 [bnc#898268]
  Fixes a bug that affects consistency and speed when connecting to
  hidden services, and it updates the location of one of the
  directory authorities.
- Major bugfixes:
  * Clients now send the correct address for their chosen rendezvous
    point when trying to access a hidden service.
- Directory authority changes:
  * Change IP address for gabelmoo (v3 directory authority).
- Minor features (geoip):
  * Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
    Country database.</changelog>
<changelog author="andreas.stieger@gmx.de" date="1414065600">- tor 0.2.4.25 [boo#902476]
  Disables SSL3 in response to the recent "POODLE" attack (even
  though POODLE does not affect Tor).
  It also works around a crash bug caused by some operating systems'
  response to the "POODLE" attack (which does affect Tor).
  - Disable support for SSLv3.
  - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
    1.0.1j, built with the 'no-ssl3' configuration option.</changelog>

</package>

</otherdata>