xstream-parent-1.4.18-lp152.2.12.1<>,%؉ao/=„r Jye_ojPzn1PS>D?4d % <TXdh{      <\(Q8X 9 : FG(H4I@XDYL\h]t^bcd5e:f=l?uTv`wxyz0Cxstream-parent1.4.18lp152.2.12.1Parent POM for xstreamParent POM for xstream.aocloud126openSUSE Leap 15.2openSUSEBSD-3-Clausehttp://bugs.opensuse.orgDevelopment/Libraries/Javahttps://x-stream.github.io/linuxnoarch?ЁA큤aoaoao997cf51aa56c148b35c2f2b8c0ac95060fb24889b2c6226828094615fcf562e89b9966b2b6a2f4d5ed9eca187de5f71f17f7c9a6d1f3f9dee2588a6d1ba65029rootrootrootrootrootrootxstream-1.4.18-lp152.2.12.1.src.rpmmvn(com.thoughtworks.xstream:xstream-parent:pom:)xstream-parent@@@    java-headlessjavapackages-filesystemmvn(org.codehaus.mojo:build-helper-maven-plugin)rpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)xstream3.0.4-14.6.0-14.0-15.2-11.4.18-lp152.2.12.14.14.1aS``x*`Gc@\~d\Yz\Z!D@Z@WVn@VA@Fridrich Strba Fridrich Strba Fridrich Strba Johannes Renner Frantisek Kobzik michele.bologna@suse.commoio@suse.commc@suse.comjgonzalez@suse.commoio@suse.commoio@suse.commoio@suse.com- Upgrade to 1.4.18 * Security fixes + This maintenance release addresses following security vulnerabilities, when unmarshalling with an XStream instance using the default blacklist of an uninitialized security framework. XStream is therefore now using a whitelist by default. (CVE-2021-39139, CVE-2021-39140, CVE-2021-39141, CVE-2021-39144, CVE-2021-39145, CVE-2021-39146, CVE-2021-39147, CVE-2021-39148, CVE-2021-39149, CVE-2021-39150, CVE-2021-39151, CVE-2021-39152, CVE-2021-39153, CVE-2021-39154, bsc#1189798) * Minor changes + Support serializable types with non-serializable parent with PureJavaReflectionConverter. * Stream compatibility + Starting with version 1.14.12 nine years ago, XStream contains a Security Framework to implement a black- or whitelist for the allowed types at deserialization time. Until version 1.4.17, XStream kept a default blacklist in order to deny all types of the Java runtime, which are used for all kinds of security attacks, in order to guarantee optimal runtime compatibility for existing users. However, this approach has failed. The last months have shown, that the Java runtime alone contains dozens of types that can be used for an attack, not even looking at the 3rd party libraries on a classpath. The new version of XStream uses therefore now by default a whitelist, which is recommended since nine years. It also has been complaining on the console for a long time about an uninitialized security framework the first time it was run. Anyone who has followed the advice and initialized the security framework for their own scenario can easily update to the new version without any problem. Everyone else will have to do a proper initialization now, otherwise the new version will fail with certainty at deserialization time. - Modified patch: * Revert-MXParser-changes.patch + rediff to changed context- Upgrade to 1.4.17 * Security fix: * bsc#1186651, CVE-2021-29505: potential code execution when unmarshalling with XStream instances using an uninitialized security framework- Upgrade to 1.4.16 * Security fixes: + bsc#1184796, CVE-2021-21351: remote attacker to load and execute arbitrary code + bsc#1184797, CVE-2021-21349: SSRF can lead to a remote attacker to request data from internal resources + bsc#1184380, CVE-2021-21350: arbitrary code execution + bsc#1184374, CVE-2021-21348: remote attacker could cause denial of service by consuming maximum CPU time + bsc#1184378, CVE-2021-21347: remote attacker to load and execute arbitrary code from a remote host + bsc#1184375, CVE-2021-21344: remote attacker could load and execute arbitrary code from a remote host + bsc#1184379, CVE-2021-21342: server-side forgery + bsc#1184377, CVE-2021-21341: remote attacker could cause a denial of service by allocating 100% CPU time + bsc#1184373, CVE-2021-21346: remote attacker could load and execute arbitrary code + bsc#1184372, CVE-2021-21345: remote attacker with sufficient rights could execute commands + bsc#1184376, CVE-2021-21343: replace or inject objects, that result in the deletion of files on the local host - Add patch: * Revert-MXParser-changes.patch + revert changes that would force us to add new dependency- Upgrade to 1.4.15 * fixes bsc#1180146, CVE-2020-26258 and bsc#1180145, CVE-2020-26259 - Upgrade to 1.4.14 * fixes bsc#1180994, CVE-2020-26217 - Update xstream to 1.4.15~susemanager Removed: * xstream_1_4_10-jdk11.patch * xstream_1_4_10-buildsh-sle12.patch * build.sh- Update xstream to 1.4.10 Added: * xstream_1_4_10-jdk11.patch * xstream_1_4_10-buildsh-sle12.patch * xstream-XSTREAM_1_4_10.tar.gz Removed: * 0001-Prevent-deserialization-of-void.patch * xstream-XSTREAM_1_4_9.tar.gz * xstream-XSTREAM_1_4_9-jdk11.patch - Major changes: - New XStream artifact with -java7 appended as version suffix for a library explicitly without the Java 8 stuff (lambda expression support, converters for java.time.* package). - Fix PrimitiveTypePermission to reject type void to prevent CVE-2017-7957 with an initialized security framework. - Improve performance by minimizing call stack of mapper chain. - XSTR-774: Add converters for types of java.time, java.time.chrono, and java.time.temporal packages (converters for LocalDate, LocalDateTime, LocalTime, OffsetDateTime, and ZonedDateTime by Matej Cimbora). - JavaBeanConverter does not respect ignored unknown elements. - Add XStream.setupDefaultSecurity to initialize security framework with defaults of XStream 1.5.x. - Emit error warning if security framework has not been initialized and the XStream instance is vulnerable to known exploits.- Feat: modify patch to be compatible with JDK 11 building Added: * xstream-XSTREAM_1_4_9-jdk11.patch Removed: * xstream-XSTREAM_1_4_9-jdk9.patch- fixes for SLE 15 compatibility- fix possible Denial of Service when unmarshalling void. (CVE-2017-7957, bsc#1070731) Added: * 0001-Prevent-deserialization-of-void.patch- Fix build for JDK9 - Disable javadoc generation (broken for SLE15 and Tumbleweed) - Add: * xstream-XSTREAM_1_4_9-jdk9.patch - Changed: * build.sh- Require building on Java 8, otherwise the LambdaMapper class is skipped (issue 30)- Upgrade to version 1.4.9, which fixes CVE-2016-3674 (bsc#972950)- Initial versioncloud126 16347176951.4.181.4.18-lp152.2.12.1xstream-xstream-parent.xmlxstreamxstream-parent.pom/usr/share/maven-metadata//usr/share/maven-poms//usr/share/maven-poms/xstream/-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -gobs://build.opensuse.org/openSUSE:Maintenance:17071/openSUSE_Leap_15.2_Update/1ac10c4a3ee1c623af3a4d55fa651d7b-xstream.openSUSE_Leap_15.2_Updatedrpmxz5noarch-suse-linuxXML 1.0 document, ASCII textdirectoryexported SGML document, ASCII textPRRR b0&utf-82e4858e463570d6b865309ef59b0ba2525e8fb738788bca0285afeeeec0cf271? 7zXZ !t/L]"k%]סd!fHa6+kEFCc4KF+RHxLns4$N 8[WՓG!$oHpsbYyZI?P,RI$ZbE+#$@8x3V<.lFbH@/(jW, AS݆5l6ָ N5Y"{k9h -f.pc SڄMѠ]+GQ>W'7~{Ke%{@TL͂WACºMZTxwȝ'%ODj[<(n,aŠmS"ٯ8Aqfbhf\Z4-5М>_k|9tp~9g>k'Rs։%`t0R]+(.^2jkKFBr)ޥ۝|'ZP,Est8PFa+=b(K=[^ bEoPsHN ||S{6cvOL5 D?ܷr`I?1bo5oc? rX)";it" j ; iblXM~h`|U.R~.7<M˃.PsG^!RUS'T7|B}!B"l.L}cw_LK̟gTd="f