libpcreposix0-8.41-6.4.2 >  A `Ip9|4L(ELѝ[+}o+=T UP9<9&pI{Y}J& PaQwN]7;6 n3Ęnwpw^>h6jF6QzHzFAOX#} ZM|:WQQB +!K8 zs=E?~iҋ+5:Dnnr9L2{|ab}#̈́B+?8K$5y~ac6a354438b14f5e972ae16a975e99e9a062c621f30a937bbb222f1976833b2f190dd61cde7e5faca57a375d89bdc374f1c25aa8/`Ip9|H.G^sG:ۮRO+Rƃp@?d  M$(Abo      ,4>H`h   (8 94 : >@FGHIXY\ ]^<bHcdhemfplruvwx$y,zDTX^Clibpcreposix08.416.4.2A library for Perl-compatible regular expressionsThe PCRE library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5. pcreposix provides a POSIX-compatible API to the PCRE engine.`IZsheep11(SUSE Linux Enterprise 15SUSE LLC BSD-3-Clausehttps://www.suse.com/System/Librarieshttp://www.pcre.org/linuxx86_64(`IP`IQ86f17c96ecb0054cab99e22089781fea23a8ca517a938f7beddf92ed0b92f2falibpcreposix.so.0.0.5rootrootrootrootpcre-8.41-6.4.2.src.rpmlibpcreposix.so.0()(64bit)libpcreposix0libpcreposix0(x86-64)@@@@@    /sbin/ldconfig/sbin/ldconfiglibc.so.6()(64bit)libc.so.6(GLIBC_2.2.5)(64bit)libc.so.6(GLIBC_2.3.4)(64bit)libc.so.6(GLIBC_2.4)(64bit)libpcre.so.1()(64bit)rpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)3.0.4-14.6.0-14.0-15.2-14.14.1`qZY@Y@Yw2Y1S@XYXW9WaC@VV@UB@T@bwiedemann@suse.comfvogt@suse.comkstreitova@suse.commatz@suse.comastieger@suse.commpluskal@suse.comastieger@suse.comdimstar@opensuse.orgastieger@suse.commpluskal@suse.comastieger@suse.comastieger@suse.comp.drouand@gmail.com- Do not run profiling 'check' in parallel to make package build reproducible (boo#1040589)- Use %license (boo#1082318)- add pcre-8.41-stack_frame_size_detection.patch to fix pcre stack frame size detection because modern compilers broke it by cloning and inlining pcre match() function [bsc#1058722]- RunTest needs much stack, on s390x more than the default 8 MB. [bnc#1046102]- pcre 8.41: * If pcregrep in multiline mode with --only-matching matched several lines, it restarted scanning at the next line instead of moving on to the end of the matched string, which can be several lines after the start. * Fix a missing else in the JIT compiler reported by 'idaifish'. CVE-2017-6004 bsc#1025709 * A (?# style comment is now ignored between a basic quantifier and a following '+' or '?' (example: /X+(?#comment)?Y/. * Avoid use of a potentially overflowing buffer in pcregrep * Fix issues reported by fuzzers in pcretest: - Check for values < 256 when calling isprint() in pcretest. - Give an error for too big a number after \O. * In the 32-bit library in non-UTF mode, an attempt to find a Unicode property for a character with a code point greater than 0x10ffff (the Unicode maximum) caused a crash. CVE-2017-7186 bsc#1030066, CVE-2017-7244 bsc#1030807 * The alternative matching function, pcre_dfa_exec() misbehaved if it encountered a character class with a possessive repeat, for example [a-f]{3}+. * When pcretest called pcre_copy_substring() in 32-bit mode, it set the buffer length incorrectly, which could result in buffer overflow. CVE-2017-7245 bsc#1030805, CVE-2017-7246 bsc#1030803- Enable jit on aarch64 - Enable profiled building- pcre 8.40: * Using -o with -M in pcregrep could cause unnecessary repeated output when the match extended over a line boundary. * Fix register overwite in JIT when SSE2 acceleration is enabled. * Ignore "show all captures" (/=) for DFA matching. * Fix JIT unaligned accesses on x86 * In any wide-character mode (8-bit UTF or any 16-bit or 32-bit mode), without PCRE_UCP set, a negative character type such as \D in a positive class should cause all characters greater than 255 to match, whatever else is in the class. There was a bug that caused this not to happen if a Unicode property item was added to such a class, for example [\D\P{Nd}] or [\W\pL]. * When pcretest was outputing information from a callout, the caret indicator for the current position in the subject line was incorrect if it was after an escape sequence for a character whose code point was greater than \x{ff}. * A pattern such as (?abc)(?(R)xyz) was incorrectly compiled such that the conditional was interpreted as a reference to capturing group 1 instead of a test for recursion. Any group whose name began with R was misinterpreted in this way. (The reference interpretation should only happen if the group's name is precisely "R".) * A number of bugs have been mended relating to match start-up optimizations when the first thing in a pattern is a positive lookahead. These all applied only when PCRE_NO_START_OPTIMIZE was *not* set: + A pattern such as (?=.*X)X$ was incorrectly optimized as if it needed both an initial 'X' and a following 'X'. + Some patterns starting with an assertion that started with .* were incorrectly optimized as having to match at the start of the subject or after a newline. There are cases where this is not true, for example, (?=.*[A-Z])(?=.{8,16})(?!.*[\s]) matches after the start in lines that start with spaces. Starting .* in an assertion is no longer taken as an indication of matching at the start (or after a newline).- Explicitly package %{_docdir}/%{name} to fix build with RPM 4.13.- record minor vulnerabilities fixed in 8.39- Update to version 8.39: * Some appropriate PCRE2 JIT improvements have been retro-fitted to PCRE1. * CVE-2016-3191: workspace overflow for (*ACCEPT) with deeply nested parentheses (boo#971741) * CVE-2016-1283: Heap buffer overflow DoS (boo#960837) * Apart from that, this is another bug-fix release.- pcre 8.38: * CVE-2015-3217: Call Stack Overflow Vulnerability in match() bsc#933878 * Other fixes to assertions, crashes, buffer overflows and performance issues found by fuzzer, affecting applications accepting regular expression from untrusted sources- pcre 8.37: * CVE-2015-2325: Patterns with certain groups specifying a zero minimum quantifier caused incorrect code to be compiled, leading to an incorrect memory read. [boo#924960] * CVE-2015-2326: Specific patterns containing a forward reference with subroutine calls caused incorrect code to be compiled [boo#924961] * CVE-2014-8964: If an assertion condition was quantified with a minimum of zero, SIGSEGV or other misbehaviour could occur. [boo#906574] * further bug fixes as listed in ChangeLog- Update to version 3.16 * This is primarily a bug-fix release. * The Unicode data tables have been updated to Unicode 7.0.0. - Remove pcre-commit1472.patch; fixed on upstream release - Remove obsolete "Obsoletes" tag/sbin/ldconfig/sbin/ldconfigsheep11 16245251468.41-6.4.28.41-6.4.2libpcreposix.so.0libpcreposix.so.0.0.5/usr/lib64/-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.suse.de/SUSE:Maintenance:19625/SUSE_SLE-15_Update/c29fd075853c9c65f9f8c8afbfdf250e-pcre.SUSE_SLE-15_Updatecpioxz5x86_64-suse-linuxELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=2e19023c74dbe618b4f2eb3947f020e8109e9871, strippedPRRRRRaz,4b(ʫKutf-8dbc10cb99a8c51a9807ed28f5785072593ae970a8d3c8f104cb2f651be81cd9f?7zXZ !t/*? ] cr$x#D@! f덦SUk+{)xr٧2tƃ]g]@ub>i=[}]\/D2u}c)ť7Hg LS-,%C'$Ϧsm9ށcrvuiP<\~U'6%D*6C ۤyV9PhElgkF)%ZמWG^?ՔfK,[p%R}xs"?m8ZLdٖuYC~DBa4TzSb쁛v&A9+mG2Y8Eus 1?dbivit_vHx^3d#D#} J?%r~ۻτҒSSfB5q#ד-^M\7<).3aG2^p31!¤!3ieN7R,*գbIV%[ImL 717RJ2K$~VMvϭ?bժN08sr]Q٨]ܬy]:r8\RP $MZS2B"2]Hhǂw-Ҽ͹* caכ^?edeXamkD[3Gc/b'c(S99dƖ_{_R)Wiq%wO}km @D2\ Ωdݟ" @QeN,hse;K}Y3\X m$aoh~8H~ ONބ@Xx=j72<wDΞ24֮C7FӣlPBqp$ELUJq;gY?"[-nU-%͚(Kk)j}~5biq{D (‚a+X,І6,glRP߉5yg+IBf0'|8&ޘ:BIV};*搾QRsXsbAN ]!m.+ D5ݡxGlDW=u hw[;d˾:wjMw4"rL<ړiзœXD^Rq + C 'Іt[TqBY+\qDr$x) @ *2 ` ?EdP=Fl~ωoş"Z>رCu|!@zgodMM(-G>߃^S|dzIP74qNyN\!3&x@u,͗(єzRO\"1 zmn~߽KOM=Lx~xQ)]䌅qcazdhԕtAJҴbO1qq| }2e(>BY7^u&JR*0>wwß`7 l鷣u1=ZA(2 n5Ù\YmK[X?y+.k::!2|܆"2C<‰?a^j#5*45AB9%N0ߎwԛnw+X^A Œh_1T*2f??A{1K<wA>r+K;qo؎9D $=(3oH.4 ]i]Ƚzi9 iN 7st5V `hb_l-0xvڹ,篏Us0(M#|gNײ18^*c!Sa)bʰbX/) x0SCWT8LM6$|@B7eqvqUa`eȖG/6ĥ͕̕5 sTmE m )p (ZۦQ,25KO  ]Y>QTj3 YZ