libpcreposix0-32bit-8.41-6.4.2 >
A `@p9|t6 ՞
OuIwg;\~GT_z=Aم`̮ 'sW !7 Ĺ8Fl߆m~k'M=Q,a%ʗY.ImɘB(2mbr·Wi}Z:YB Dۗ= ègfs7F +SkDUvZA{ q$g#DI1f={+xNbt
RGrM85b73d487d2b517ff53b962118e62118b749d653 dbac06f4dee5adec238030baf66d32b5d9ba6ee44c78e8acd50ce24dd20c3e79 /D `@p9| /jڽ?p1(vo~4
L!\
Hs*4( h 0eU^c S2TIܑdtߢWt;)SzPSқ:
!ӆn
&F}T8+,1Ѧez,ci֭yth ,)ŗ VMn !}[©݅c%g)~\-ˡLiՊ3P xλ$
cE9n 'h > p > ? x d ! S ( , E f s
&
@ H R \ t | ( 8
9 $
:
> G H I X Y \ ] ^ b c d C e H f K l M u ` v h w x y ( , 2 t C libpcreposix0-32bit 8.41 6.4.2 A library for Perl-compatible regular expressions The 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. `@sheep93 %SUSE Linux Enterprise 15 SUSE LLC BSD-3-Clause https://www.suse.com/ System/Libraries http://www.pcre.org/ linux x86_64 /sbin/ldconfig % `@`@ 450c944433f9c170f81b6764745d32849672b6c73c0ea36c534c8785155efcdb libpcreposix.so.0.0.5 root root root root pcre-8.41-6.4.2.src.rpm libpcreposix.so.0 libpcreposix0-32bit libpcreposix0-32bit(x86-32) @ @ @ @ @ @
/bin/sh libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.3.4) libc.so.6(GLIBC_2.4) libpcre.so.1 rpmlib(CompressedFileNames) rpmlib(FileDigests) rpmlib(PayloadFilesHavePrefix) rpmlib(PayloadIsXz) 3.0.4-1 4.6.0-1 4.0-1 5.2-1 4.14.1 `qZY@Y@Yw2Y1S@XYXW9WaC@VV@UB@T@bwiedemann@suse.com fvogt@suse.com kstreitova@suse.com matz@suse.com astieger@suse.com mpluskal@suse.com astieger@suse.com dimstar@opensuse.org astieger@suse.com mpluskal@suse.com astieger@suse.com astieger@suse.com p.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 /bin/sh 8.41-6.4.2 8.41-6.4.2 libpcreposix.so.0 libpcreposix.so.0.0.5 /usr/lib/ -fomit-frame-pointer -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g obs://build.suse.de/SUSE:Maintenance:19625/SUSE_SLE-15_Update/c29fd075853c9c65f9f8c8afbfdf250e-pcre.SUSE_SLE-15_Update cpio xz 5 x86_64-suse-linux ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=f9b3c9dc19485b6494e5514111283569844eecae, stripped P R R R R R R utf-8 a7fa2fdf64a30cd9688c2f08edbd3bfb2cc90d34a7f52f3dfb9aa7fe511f001c ? 7zXZ
! t/'gs]
cr$x#D@o0͠ s]*4Ѐ upx1l&I!@ƙGE.kws$9 fELi1\Q\(h [
qڨ4&gQisVc"rG!Jל5(ZO\` 0NDLdfYCaxb$Gڬ`^y/}@Уxr
mZ0| A{h5XzƍxRY^OKE1Zesb/Z2oݧ~? r*9!敟J^ s
Q=Y)ʵU/D,;IՂv|6yCB2`~s;(C]Z,^P|+Fᡦ
N'QBbu\>|3^jrL#N~s-G-"6n %AVk
pȈ ͅ;>,. hA@TWI+3C~yۀkPdo ތѢ$"W%嫙[ 2{({,P#p4|
D1h4IypmÍܭ;_EP6Η L oی'\tRmӊ$#duKQ0g\#RcM*fD涞qotH佺. cj)ŋI{l=Z]|:_RS5v#Q9g#;Y0){"`_n!' Ngx6;QF͖٢%T ʊ<+@ig.Wh26akb990# dA?]N4
X&ZCб Llt"zE>p _q5:E`A a|ɱyۏP
9̍J,/ޡ m7> ޟy1C1-)+x}ԋ`(/)=+*d]6!֛Oё,S?#7M@U1(Vތ'#LPk^sGUk䑔 V~ug9D; jW%%풕k 6z~Bk,4ƵO~𲄋&oݝCijY%~6OOg?rI D?4}1gjDS(ќ\Z> 뙩8 'Nu2~RU`I*k`A4"v]jM
f /y 3*P]8aVSa{ 삝[>\7,nWMB
(!pf oP( "j*m u*/ayِW圲ɄYKnjɔδSv{0îMe6e("]Q:D&'STZ+;2DD3z.Ykb y@d * e Dr;TL)O;D Sj=֮'WuXl 04eܹ8vUo?;
x)_
G M ß[Pb"W_j-=(%*ٲ"-5oDh2g.aiF ml1ܜ 40'Gސ&cv!& bimIUJ'\ )#܇M2o"BE=qR@F~wptHtqɈ;;ץ MyU]w!& 2h5Z * m3&St7\zxC-EtU ] DE}mk3v۟;_:~/>d :0H̸Jn{hTRά6xiqG j(%Ls wц#B7ѼIT|^uBu140? eUMYM:>4ش"x qc $Dʙ
/e)t5}5`o+: N o6
YZ