pike issueshttps://git.lysator.liu.se/pikelang/pike/-/issues2020-03-05T17:23:49Zhttps://git.lysator.liu.se/pikelang/pike/-/issues/8065register_path() doesn't reschedule the backend_check() call_out.2020-03-05T17:23:49ZPeter Bortasregister_path() doesn't reschedule the backend_check() call_out.Imported from https://youtrack.roxen.com/issue/PIKE-65
Reported by @grubba
If the newly added monitor ends up at the head of the `monitor_queue`, the `backend_check()` call_out likely needs to be rescheduled.Imported from https://youtrack.roxen.com/issue/PIKE-65
Reported by @grubba
If the newly added monitor ends up at the head of the `monitor_queue`, the `backend_check()` call_out likely needs to be rescheduled.https://git.lysator.liu.se/pikelang/pike/-/issues/8064backend_check() call_out not rescheduled properly by adjust_monitor().2018-02-07T16:26:12ZPeter Bortasbackend_check() call_out not rescheduled properly by adjust_monitor().Imported from https://youtrack.roxen.com/issue/PIKE-64
Reported by @grubba
The `backend_check()` call_out doesn't get rescheduled if the adjusted monitor already is at the head of the `monitor_queue`.Imported from https://youtrack.roxen.com/issue/PIKE-64
Reported by @grubba
The `backend_check()` call_out doesn't get rescheduled if the adjusted monitor already is at the head of the `monitor_queue`.https://git.lysator.liu.se/pikelang/pike/-/issues/8063Thread.Thread->id_number() sometimes returns same value for different threads2020-03-05T17:26:11ZPeter BortasThread.Thread->id_number() sometimes returns same value for different threadsImported from https://youtrack.roxen.com/issue/PIKE-63
Reported by KG Sterneberg <kg@roxen.com>
Encountered this problem when writing and running tests for the new Edition Purger.
Tried to reproduce the problem in an isolated test but ...Imported from https://youtrack.roxen.com/issue/PIKE-63
Reported by KG Sterneberg <kg@roxen.com>
Encountered this problem when writing and running tests for the new Edition Purger.
Tried to reproduce the problem in an isolated test but failed.
In order to reproduce, checkout branch kg/PIKE-X-thread-id-number-issue in Print and Roxen repos. Then run the the PurgerTest by executing:
`TEST_SUITE=PurgerTest ./start --self-test --tests=rep_archive -DARCHIVE_DEBUG`
NB: You need to have Elasticsearch installed and configured on localhost:9200 and test-indices created. Go to the directory `scripts` in the Archive repo and execute `sh create_indices.sh test` (NB: You must stand in directory 'scripts').
In the debug-log you will see stuff like this:
TRACE: Clearing cache. thread id: 140735632249664, Thread: Thread.Thread(0x70000c65a000)
TRACE: Clearing cache. thread id: 140735632249664, Thread: Thread.Thread(0x70000c14b000)
TRACE: Clearing cache. thread id: 140735632249664, Thread: Thread.Thread(0x70000c351000)
TRACE: Clearing cache. thread id: 140735632249664, Thread: Thread.Thread(0x70000c24e000)https://git.lysator.liu.se/pikelang/pike/-/issues/8062Locking of mutexes while threads disabled.2020-03-05T17:26:59ZPeter BortasLocking of mutexes while threads disabled.Imported from https://youtrack.roxen.com/issue/PIKE-62
Reported by @grubba
Blocked by [PIKE-78](#8078)
Attempting to lock mutexes (like lock_compiler()) ought to throw errors when threads are disabled.Imported from https://youtrack.roxen.com/issue/PIKE-62
Reported by @grubba
Blocked by [PIKE-78](#8078)
Attempting to lock mutexes (like lock_compiler()) ought to throw errors when threads are disabled.https://git.lysator.liu.se/pikelang/pike/-/issues/8061`== on Calendar.Events triggers compilation of Geography.Countries.2018-02-06T16:12:50ZPeter Bortas`== on Calendar.Events triggers compilation of Geography.Countries.Imported from https://youtrack.roxen.com/issue/PIKE-61
Reported by @grubbaImported from https://youtrack.roxen.com/issue/PIKE-61
Reported by @grubbahttps://git.lysator.liu.se/pikelang/pike/-/issues/8060Leak of types when getters or setters in some circumstances.2018-01-25T11:15:28ZPeter BortasLeak of types when getters or setters in some circumstances.Imported from https://youtrack.roxen.com/issue/PIKE-60
Reported by @grubba
The following leak appeared after commit `cc5e92a5b5c109f6e225101d94fa35e1ba00c0dd`:
```
Pike v8.1 release 11 running Hilfe v3.5 (Incremental Pike Frontend)
> ...Imported from https://youtrack.roxen.com/issue/PIKE-60
Reported by @grubba
The following leak appeared after commit `cc5e92a5b5c109f6e225101d94fa35e1ba00c0dd`:
```
Pike v8.1 release 11 running Hilfe v3.5 (Incremental Pike Frontend)
> Nettle;
(1) Result: Nettle
Terminal closed.
Leak(s) found at exit:
Type at 0x555557488e30 got 1 unaccounted refs (and 0 accounted): int(1..2147483647)
Type at 0x55555748a370 got 1 unaccounted refs (and 0 accounted): { Gmp.mpz = object(implements 32) }
Free of leaked type 0x555557488e30 from /home/grubba/src/Pike/8.1/src/pike_modules.c:318, 0 refs remaining
Free of leaked type 0x55555748a370 from /home/grubba/src/Pike/8.1/src/pike_modules.c:318, 0 refs remaining
```https://git.lysator.liu.se/pikelang/pike/-/issues/8058Fix censoring of Crypto.SHA256.crypt_hash() in Pike/Nettle.2020-03-06T09:40:01ZPeter BortasFix censoring of Crypto.SHA256.crypt_hash() in Pike/Nettle.Imported from https://youtrack.roxen.com/issue/PIKE-58
Reported by @grubba
The parameter marked as ****** below is not censored in the thread backtrace:
```
14:38:41 : >> pike/lib/modules/Nettle.so:1: Crypto.SHA256.crypt_ha...Imported from https://youtrack.roxen.com/issue/PIKE-58
Reported by @grubba
The parameter marked as ****** below is not censored in the thread backtrace:
```
14:38:41 : >> pike/lib/modules/Nettle.so:1: Crypto.SHA256.crypt_hash("******","sTo30/QP7k99DSc3",UNDEFINED)
```https://git.lysator.liu.se/pikelang/pike/-/issues/8057Former QA task of PIKE-55 (#8055). See it for details.2018-01-22T13:43:52ZPeter BortasFormer QA task of PIKE-55 (#8055). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-57
Reported by @grubba
Blocking [PIKE-55](#8055)Imported from https://youtrack.roxen.com/issue/PIKE-57
Reported by @grubba
Blocking [PIKE-55](#8055)https://git.lysator.liu.se/pikelang/pike/-/issues/8055Segmentation fault in backend_find_call_out_info2022-11-06T12:19:26ZPeter BortasSegmentation fault in backend_find_call_out_infoImported from https://youtrack.roxen.com/issue/PIKE-55
Reported by Marcus Wellhardh <wellhard@roxen.com>
Got the following segmentation fault using roxen-6.2.77-test-ep-rhel7_x86_64.sh which in reality is version 6.2.78.
Server versio...Imported from https://youtrack.roxen.com/issue/PIKE-55
Reported by Marcus Wellhardh <wellhard@roxen.com>
Got the following segmentation fault using roxen-6.2.77-test-ep-rhel7_x86_64.sh which in reality is version 6.2.78.
Server version:
```
: Server start command:
: /usr/local/roxen/server-6.2.78/bin/roxen
: -DLOG_GC_TIMESTAMPS
: -DLOG_GC_CYCLES
: -DLOG_GC_HISTOGRAM
: -DREP_DEBUG_DEF_CACHING
: -DRAM_CACHE
: -DHTTP_COMPRESSION
: -M/usr/local/roxen/server-6.2.78/etc/modules
: -M/usr/local/roxen/local/pike_modules
: -I/usr/local/roxen/server-6.2.78/etc/include
: -I/usr/local/roxen/server-6.2.78/base_server
: -P/usr/local/roxen/server-6.2.78/base_server
: -P/usr/local/roxen/server-6.2.78
: base_server/roxenloader.pike
: --pid-file=../configurations/_roxen_pid
```
GDB:
```
(gdb) bt
#0 0x000000000044b2fa in backend_find_call_out_info (me# me@entry
0x8d6758, fun=0x7ffff7e631f0) at /home/dist/tmp/build/pike.srcbuild/../pike/src/backend.cmod:1138
#1 0x000000000044c465 in f_Backend_remove_call_out (args=<optimized out>) at /home/dist/tmp/build/pike.srcbuild/../pike/src/backend.cmod:1289
#2 0x0000000000429fd9 in low_mega_apply (type# APPLY_SVALUE, type@entry
APPLY_SVALUE_STRICT, args# 1, arg1
<optimized out>, arg2# arg2@entry
0x0) at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/apply_low.h:221
#3 0x000000000042a74d in jump_opcode_F_APPLY_AND_POP (arg1=<optimized out>) at /home/dist/tmp/build/pike.srcbuild/../pike/src/interpret_functions.h:2449
#4 0x00007fffe95507d9 in ?? ()
#5 0x00000000011ed2f0 in ?? ()
#6 0x0000000000b28f90 in ?? ()
#7 0x00007ffff0236000 in ?? ()
#8 0x00007ffff7e631c0 in ?? ()
#9 0x0000000000b1e848 in ?? ()
#10 0x00000000008e3820 in ?? ()
#11 0x00007fffeb5fe593 in ?? ()
#12 0x000000000041d636 in eval_instruction (pc=0x7fffeb5fe593 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213VpI\213v`L\211\357H\017\267R\002\307\300\200\371K")
at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:1711
#13 catching_eval_instruction (pc# 0x7fffeb5fe593 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213VpI\213v`L\211\357H\017\267R\002\307\300\200\371K", pc@entry
0x7fffffffd040 "\223\345_\353\377\177")
at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:2754
#14 0x000000000041fc50 in inter_return_opcode_F_CATCH (addr=0x7fffffffd040 "\223\345_\353\377\177") at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:1295
#15 0x00007fffeb5fe57b in ?? ()
#16 0x0000000007245820 in ?? ()
#17 0xfffffffffffffff0 in ?? ()
#18 0x000000005a65d8e6 in ?? ()
#19 0x000000005a65d8e5 in ?? ()
#20 0x0000000000000001 in ?? ()
#21 0x0000000000000001 in ?? ()
#22 0x00000000008d6758 in ?? ()
#23 0x000000000042df96 in eval_instruction (pc=<optimized out>) at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:1711
#24 mega_apply (arg2# 0x0, arg1
0x0, args# args@entry
9320480, type=APPLY_STACK) at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:2695
#25 f_call_function (args# args@entry
9320480) at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:2775
#26 0x000000000044c244 in backend_do_call_outs (me# 0x7ffff7e63180, me@entry
0x8d6758) at /home/dist/tmp/build/pike.srcbuild/../pike/src/backend.cmod:1048
#27 0x000000000044ff39 in pdb_low_backend_once (pdb# 0x8d6740, timeout
timeout@entry=0x7fffffffd4f0) at /home/dist/tmp/build/pike.srcbuild/../pike/src/backend.cmod:4177
#28 0x00000000004501b0 in f_PollDeviceBackend_cq__backtick_28_29 (args=<optimized out>) at /home/dist/tmp/build/pike.srcbuild/../pike/src/backend.cmod:4310
#29 0x0000000000429fd9 in low_mega_apply (type# APPLY_SVALUE, type@entry
APPLY_STACK, args# 1, arg1
<optimized out>, arg1@entry# 0x0, arg2
arg2@entry=0x0) at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/apply_low.h:221
#30 0x000000000042a99e in jump_opcode_F_CALL_FUNCTION_AND_POP () at /home/dist/tmp/build/pike.srcbuild/../pike/src/interpret_functions.h:2452
#31 0x00007ffff000e47c in ?? ()
#32 0x000000000000005f in ?? ()
#33 0x0000000000965ba0 in ?? ()
#34 0x00007ffff0236000 in ?? ()
#35 0x00007ffff7e63120 in ?? ()
#36 0x00000000008caef8 in ?? ()
#37 0x00000000008e3820 in ?? ()
#38 0x00007ffff000c2a4 in ?? ()
#39 0x000000000041d636 in eval_instruction (pc=0x7ffff000c2a4 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213NpH\213I H\213\211\230") at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:1711
#40 catching_eval_instruction (pc# 0x7ffff000c2a4 "UH\211\345AWAVAUATSH\203\354\bI\211\377M\213w H\215\005\365\377\377\377I\211F(M\213/I\213NpH\213I H\213\211\230", pc@entry
0x7ffff7e63240 "") at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:2754
#41 0x000000000041fc50 in inter_return_opcode_F_CATCH (addr=0x7ffff7e63240 "") at /tmp/dist/6.0/pike.rhel7_x86_64/pike/src/interpret.c:1295
#42 0x00007ffff000c28c in ?? ()
#43 0x00007fffffffda14 in ?? ()
#44 0x0000000000000001 in ?? ()
#45 0x00000000005d460d in __dso_handle ()
#46 0x00007fffffffda50 in ?? ()
#47 0x0000000000000000 in ?? ()
(gdb) disassemble 0x000000000044b2fa
Dump of assembler code for function backend_find_call_out_info:
0x000000000044b270 <+0>: push %r12
0x000000000044b272 <+2>: mov 0x403d57(%rip),%rax # 0x84efd0 <Pike_interpreter_pointer>
0x000000000044b279 <+9>: mov %rdi,%r12
0x000000000044b27c <+12>: push %rbp
0x000000000044b27d <+13>: push %rbx
0x000000000044b27e <+14>: mov (%rax),%rbp
0x000000000044b281 <+17>: mov 0x100(%rdi),%eax
0x000000000044b287 <+23>: test %eax,%eax
0x000000000044b289 <+25>: je 0x44b34f <backend_find_call_out_info+223>
0x000000000044b28f <+31>: cmpw $0x8,(%rsi)
0x000000000044b293 <+35>: mov %rsi,%rbx
0x000000000044b296 <+38>: je 0x44b360 <backend_find_call_out_info+240>
0x000000000044b29c <+44>: mov %rbx,%rdi
0x000000000044b29f <+47>: callq 0x540640 <hash_svalue>
0x000000000044b2a4 <+52>: mov 0x114(%r12),%ecx
0x000000000044b2ac <+60>: mov %eax,%esi
0x000000000044b2ae <+62>: xor %edx,%edx
0x000000000044b2b0 <+64>: mov %rsi,%rax
0x000000000044b2b3 <+67>: div %rcx
0x000000000044b2b6 <+70>: shl $0x4,%rdx
0x000000000044b2ba <+74>: add 0x120(%r12),%rdx
0x000000000044b2c2 <+82>: mov 0x8(%rdx),%rcx
0x000000000044b2c6 <+86>: test %rcx,%rcx
0x000000000044b2c9 <+89>: je 0x44b43b <backend_find_call_out_info+459>
0x000000000044b2cf <+95>: mov 0x403cfa(%rip),%r8 # 0x84efd0 <Pike_interpreter_pointer>
0x000000000044b2d6 <+102>: mov (%r8),%rdx
0x000000000044b2d9 <+105>: jmp 0x44b2e9 <backend_find_call_out_info+121>
0x000000000044b2db <+107>: nopl 0x0(%rax,%rax,1)
0x000000000044b2e0 <+112>: mov 0x20(%rcx),%rcx
0x000000000044b2e4 <+116>: test %rcx,%rcx
0x000000000044b2e7 <+119>: je 0x44b34a <backend_find_call_out_info+218>
0x000000000044b2e9 <+121>: cmp %rsi,0x8(%rcx)
0x000000000044b2ed <+125>: jne 0x44b2e0 <backend_find_call_out_info+112>
0x000000000044b2ef <+127>: mov 0x40(%rcx),%rax
0x000000000044b2f3 <+131>: lea 0x10(%rdx),%rdi
0x000000000044b2f7 <+135>: mov %rdi,(%r8)
=> 0x000000000044b2fa <+138>: addl $0x1,(%rax)
0x000000000044b2fd <+141>: movq $0x8,(%rdx)
0x000000000044b304 <+148>: mov %rax,0x8(%rdx)
0x000000000044b308 <+152>: mov %rdi,%rdx
0x000000000044b30b <+155>: jmp 0x44b2e0 <backend_find_call_out_info+112>
0x000000000044b30d <+157>: nopl (%rax)
0x000000000044b310 <+160>: mov -0x8(%rdx),%r12
0x000000000044b314 <+164>: mov %rbx,%rdi
0x000000000044b317 <+167>: mov 0x28(%r12),%rsi
0x000000000044b31c <+172>: callq 0x541370 <is_eq>
0x000000000044b321 <+177>: test %eax,%eax
0x000000000044b323 <+179>: jne 0x44b3b0 <backend_find_call_out_info+320>
0x000000000044b329 <+185>: mov 0x403ca0(%rip),%rax # 0x84efd0 <Pike_interpreter_pointer>
0x000000000044b330 <+192>: mov (%rax),%rcx
0x000000000044b333 <+195>: lea -0x10(%rcx),%rdx
0x000000000044b337 <+199>: mov %rdx,(%rax)
0x000000000044b33a <+202>: movzwl -0x10(%rcx),%eax
0x000000000044b33e <+206>: and $0xfffffff8,%eax
0x000000000044b341 <+209>: cmp $0x8,%eax
0x000000000044b344 <+212>: je 0x44b420 <backend_find_call_out_info+432>
0x000000000044b34a <+218>: cmp %rdx,%rbp
0x000000000044b34d <+221>: jb 0x44b310 <backend_find_call_out_info+160>
0x000000000044b34f <+223>: xor %eax,%eax
0x000000000044b351 <+225>: pop %rbx
0x000000000044b352 <+226>: pop %rbp
0x000000000044b353 <+227>: pop %r12
0x000000000044b355 <+229>: retq
0x000000000044b356 <+230>: nopw %cs:0x0(%rax,%rax,1)
---Type <return> to continue, or q <return> to quit---
(gdb) info reg
rax 0x0 0
rbx 0x7ffff7e631f0 140737352446448
rcx 0x14ef0a80 351210112
rdx 0x7ffff7e63200 140737352446464
rsi 0x459954 4561236
rdi 0x7ffff7e63210 140737352446480
rbp 0x7ffff7e63200 0x7ffff7e63200
rsp 0x7fffffffcec0 0x7fffffffcec0
r8 0x8e3820 9320480
r9 0x186a0 100000
r10 0x8e3820 9320480
r11 0x293 659
r12 0x8d6758 9267032
r13 0x7ffff7e631f0 140737352446448
r14 0x8e3380 9319296
r15 0xb1c5c8 11650504
rip 0x44b2fa 0x44b2fa <backend_find_call_out_info+138>
eflags 0x10246 [ PF ZF IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
(gdb)
```https://git.lysator.liu.se/pikelang/pike/-/issues/8052Search engine can not add more blobs2018-01-17T13:30:45ZPeter BortasSearch engine can not add more blobsImported from https://youtrack.roxen.com/issue/PIKE-52
Reported by Marcus Wellhardh <wellhard@roxen.com>
Doing a re-index on a large REP site, the search blobs is filled but new blobs are not created.
Example that show the problem 6.1...Imported from https://youtrack.roxen.com/issue/PIKE-52
Reported by Marcus Wellhardh <wellhard@roxen.com>
Doing a re-index on a large REP site, the search blobs is filled but new blobs are not created.
Example that show the problem 6.1.215 :
```
SELECT word, SUM(used_len) AS total_used_len, COUNT(*) as split_count FROM word_hit GROUP BY word ORDER BY total_used_len DESC LIMIT 15
word total_used_len split_count
with 524288 1
is 524288 1
and 524288 1
a 524288 1
of 524287 1
it 524287 1
the 524287 1
said 524285 1
be 524285 1
at 524285 1
he 524284 1
to 524284 1
that 524284 1
was 524283 1
by 524283 1
```
Example of an old and working site
```
SELECT word, SUM(used_len) AS total_used_len, COUNT(*) as split_count FROM word_hit GROUP BY word ORDER BY total_used_len DESC LIMIT 15
word total_used_len split_count
i 7353934 16
och 6831648 15
att 6447934 14
det 6062410 13
paÌŠ 5526636 12
är 4928844 10
som 4630262 10
en 4429867 9
för 3955365 8
har 3509380 7
med 3427574 8
till 3301339 7
av 2889272 6
de 2771811 6
vi 2561151 5
```
It is probably something in the following commits that introduced the problem:
Pike/8.0: 1ca24ae337, 5294c3b78 och 2a156066https://git.lysator.liu.se/pikelang/pike/-/issues/8050Update the SSL module to support TLS 1.3.2022-08-28T22:32:58ZPeter BortasUpdate the SSL module to support TLS 1.3.Imported from https://youtrack.roxen.com/issue/PIKE-50
Reported by @grubba
TLS 1.3 is starting to stabilize, and various drafts of it are already supported by browsers.Imported from https://youtrack.roxen.com/issue/PIKE-50
Reported by @grubba
TLS 1.3 is starting to stabilize, and various drafts of it are already supported by browsers.https://git.lysator.liu.se/pikelang/pike/-/issues/8049Fix Stdio.sendfile() to not close TLS connections before handshaking has comp...2017-11-23T14:36:56ZPeter BortasFix Stdio.sendfile() to not close TLS connections before handshaking has completed.Imported from https://youtrack.roxen.com/issue/PIKE-49
Reported by @grubbaImported from https://youtrack.roxen.com/issue/PIKE-49
Reported by @grubbahttps://git.lysator.liu.se/pikelang/pike/-/issues/8046Former QA task of PIKE-44 (#8044). See it for details.2017-11-16T12:43:35ZPeter BortasFormer QA task of PIKE-44 (#8044). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-46
Reported by @grubba
Blocking [PIKE-44](#8044)Imported from https://youtrack.roxen.com/issue/PIKE-46
Reported by @grubba
Blocking [PIKE-44](#8044)https://git.lysator.liu.se/pikelang/pike/-/issues/8045Former Fix task of PIKE-44 (#8044). See it for details.2017-11-16T11:34:04ZPeter BortasFormer Fix task of PIKE-44 (#8044). See it for details.Imported from https://youtrack.roxen.com/issue/PIKE-45
Reported by @grubba
Blocking [PIKE-44](#8044)Imported from https://youtrack.roxen.com/issue/PIKE-45
Reported by @grubba
Blocking [PIKE-44](#8044)https://git.lysator.liu.se/pikelang/pike/-/issues/8044Option to allow redirects in check_http2020-03-05T17:19:33ZPeter BortasOption to allow redirects in check_httpImported from https://youtrack.roxen.com/issue/PIKE-44
Reported by Marcus Wellhardh <wellhard@roxen.com>
Is it possible to add an option to check_http to allow redirects as valid response?
```
[root@nagios ~]1. /usr/local/bin/pike -x ...Imported from https://youtrack.roxen.com/issue/PIKE-44
Reported by Marcus Wellhardh <wellhard@roxen.com>
Is it possible to add an option to check_http to allow redirects as valid response?
```
[root@nagios ~]1. /usr/local/bin/pike -x check_http "https://magazin24.se"
WARNING: Bad status code: Moved Permanently(301). | code# 301;runtime
0.191268;ssl# TLS1.2;suite
TLS_ecdhe_rsa_with_camellia_256_gcm_sha384
[root@nagios ~]1. /usr/local/bin/pike -x check_http --version
Check HTTP/Pike v8.0.136
```https://git.lysator.liu.se/pikelang/pike/-/issues/8042System Inotify attempts to call destructed functions2020-03-22T16:59:46ZPeter BortasSystem Inotify attempts to call destructed functionsImported from https://youtrack.roxen.com/issue/PIKE-42
Reported by KG Sterneberg <kg@roxen.com>
```
Unknown program: destructed object->function(1,32768,0,"")
pike/lib/modules/System.pmod/_Inotify.so:1: System._Inotify._Instance()->po...Imported from https://youtrack.roxen.com/issue/PIKE-42
Reported by KG Sterneberg <kg@roxen.com>
```
Unknown program: destructed object->function(1,32768,0,"")
pike/lib/modules/System.pmod/_Inotify.so:1: System._Inotify._Instance()->poll()
-:1: Pike.Backend(0)->`()(3600.0)
```Pike 8.0https://git.lysator.liu.se/pikelang/pike/-/issues/8041Search compactor crashes with double free or corruption error2017-10-20T07:42:39ZPeter BortasSearch compactor crashes with double free or corruption errorImported from https://youtrack.roxen.com/issue/PIKE-41
Reported by Marcus Wellhardh <wellhard@roxen.com>
```
: Search: Notice: Starting database compactor with Pike v8.0 release 408
*** Error in `/usr/local/roxen/server-6.1.2...Imported from https://youtrack.roxen.com/issue/PIKE-41
Reported by Marcus Wellhardh <wellhard@roxen.com>
```
: Search: Notice: Starting database compactor with Pike v8.0 release 408
*** Error in `/usr/local/roxen/server-6.1.200/bin/roxen': double free or corruption (!prev): 0x0000000001361da0 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7d053)[0x7f16c0b04053]
/usr/local/roxen/server-6.1.200/pike/lib/modules/_WhiteFish.so(+0x7fc9)[0x7f16b6554fc9]
/usr/local/roxen/server-6.1.200/pike/lib/modules/_WhiteFish.so(+0x71c5)[0x7f16b65541c5]
/usr/local/roxen/server-6.1.200/bin/roxen[0x42d6f2]
/usr/local/roxen/server-6.1.200/bin/roxen[0x42df68]
[0x7f16b64f1aff]
======= Memory map: ========
00400000-00690000 r-xp 00000000 fd:02 65931137 /usr/local/roxen/server-6.1.200/bin/roxen
00890000-00891000 r--p 00290000 fd:02 65931137 /usr/local/roxen/server-6.1.200/bin/roxen
00891000-00893000 rw-p 00291000 fd:02 65931137 /usr/local/roxen/server-6.1.200/bin/roxen
00893000-008f3000 rw-p 00000000 00:00 0
01246000-070af000 rw-p 00000000 00:00 0 [heap]
```https://git.lysator.liu.se/pikelang/pike/-/issues/8040The install script generated by mkpackage doesn't propagate the error code fr...2017-10-02T07:30:02ZPeter BortasThe install script generated by mkpackage doesn't propagate the error code from extra platform tests.Imported from https://youtrack.roxen.com/issue/PIKE-40
Reported by @grubba
See [PS-127] for details.Imported from https://youtrack.roxen.com/issue/PIKE-40
Reported by @grubba
See [PS-127] for details.https://git.lysator.liu.se/pikelang/pike/-/issues/8039Implement support for encoding of keys to JWK.2017-09-29T09:31:59ZPeter BortasImplement support for encoding of keys to JWK.Imported from https://youtrack.roxen.com/issue/PIKE-39
Reported by @grubba
When using ACME the client needs to be able to send its public API key to the server as a JWK.
Currently Pike only has support for decoding of JWK.Imported from https://youtrack.roxen.com/issue/PIKE-39
Reported by @grubba
When using ACME the client needs to be able to send its public API key to the server as a JWK.
Currently Pike only has support for decoding of JWK.https://git.lysator.liu.se/pikelang/pike/-/issues/8037Extend JWS to support Key ID.2020-03-05T17:17:55ZPeter BortasExtend JWS to support Key ID.Imported from https://youtrack.roxen.com/issue/PIKE-37
Reported by @grubba
Blocked by [PIKE-38](#8038)
ACME draft 7 6.2:
```
JWS objects sent in ACME requests MUST meet the following additional
criteria:
o The JWS MUST NOT hav...Imported from https://youtrack.roxen.com/issue/PIKE-37
Reported by @grubba
Blocked by [PIKE-38](#8038)
ACME draft 7 6.2:
```
JWS objects sent in ACME requests MUST meet the following additional
criteria:
o The JWS MUST NOT have the value "none" in its "alg" field
o The JWS MUST NOT have a Message Authentication Code (MAC)-based
algorithm in its "alg" field
o The JWS Protected Header MUST include the following fields:
Barnes, et al. Expires December 23, 2017 [Page 9]
Internet-Draft ACME June 2017
* "alg" (Algorithm)
* "jwk" (JSON Web Key, only for requests to new-account and
revoke-cert resources)
* "kid" (Key ID, for all other requests)
* "nonce" (defined in Section 6.4 below)
* "url" (defined in Section 6.3 below)
The "jwk" and "kid" fields are mutually exclusive. Servers MUST
reject requests that contain both.
For new-account requests, and for revoke-cert requests authenticated
by certificate key, there MUST be a "jwk" field.
For all other requests, there MUST be a "kid" field. This field must
contain the account URL received by POSTing to the new-account
resource.
```