Me and grubba have destilled the CHANGES to these two remaining:
o SSL
FIXME: client certificates: examples?
No release before Bill provides some.
o Kerberos
FIXME
No release before mast writes this.
Mast does not really have any hand in the Kerberos module. It should not be confused with the GSSAPI module. *Points at Grubba*
Besides, it provides so puny Kerberos support I think it would be better to leave it undocumented, or else people looking for Kerberos glue would just be disappointed.
On 11/8/08, Martin Stjernholm, Roxen IS @ Pike developers forum 10353@lyskom.lysator.liu.se wrote:
Mast does not really have any hand in the Kerberos module. It should not be confused with the GSSAPI module. *Points at Grubba*
Make that mast should provide gssapi changes then.
Besides, it provides so puny Kerberos support I think it would be better to leave it undocumented, or else people looking for Kerberos glue would just be disappointed.
Almost fair enough, but it should be documented as experimental/unstable then.
I've already made an entry for GSSAPI. It is just a couple of lines above that Kerberos FIXME..
Well, it [the use of client certificates] doesn't really work any differently than server certificates; they're only used if the server requests/requires them. I can dig up example code, but it's really nothing earth-shattering.
Bill
On Nov 8, 2008, at 11:40 AM, Peter Bortas @ Pike developers forum wrote:
Me and grubba have destilled the CHANGES to these two remaining:
o SSL
FIXME: client certificates: examples?
No release before Bill provides some.
o Kerberos
FIXME
No release before mast writes this.
Not sure if I want to add to the blocker list at this time, but I'm curious to hear if someone else has seen this? For some time I've experienced random crashes on OS X (PPC only so far) during startup of Roxen:
Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000038 Crashed Thread: 0
Thread 0 Crashed: 0 ??? 0x023f8a80 0 + 37718656 1 pike 0x0001654c opcode_F_ARROW + 100 (interpret_functions.h:1843) 2 pike 0x0001f3d4 apply_low_safe_and_stupid + 816 (interpret.c:2391) 3 pike 0x0014ca98 eval_low + 252 (las.c:5268) 4 pike 0x001568cc optimize + 1952 (las.c:1987) 5 pike 0x0015d664 dooptcode + 128 (las.c:5194) 6 pike 0x000063c8 yyparse + 9408 (language.yacc:1080) 7 pike 0x00103824 run_pass2 + 732 (program.c:8042) 8 pike 0x001054d8 f_compilation_compile + 820 (program.c:8505)
[...]
Thread 0 crashed with PPC Thread State 32: srr0: 0x023f8a80 srr1: 0x0200f030 dar: 0x00000038 dsisr: 0x40000000 r0: 0x0001c178 r1: 0xbfff8450 r2: 0x002372e4 r3: 0x023f8a74 r4: 0x00000122 r5: 0x000186a0 r6: 0x00000006 r7: 0x023f8a74 r8: 0x002372e4 r9: 0x002372e4 r10: 0x00000013 r11: 0x00000008 r12: 0x00000012 r13: 0x0000011a r14: 0x00000000 r15: 0x002372e4 r16: 0x002b1518 r17: 0x00000018 r18: 0xffffffff r19: 0x0092bcb0 r20: 0x00000000 r21: 0x00000000 r22: 0x00000449 r23: 0x00e6ea80 r24: 0x00000008 r25: 0x00000000 r26: 0x00000016 r27: 0x00ce83c8 r28: 0xbfff85b0 r29: 0x002372e4 r30: 0x023f8a74 r31: 0x0000f63c cr: 0x42004244 xer: 0x00000000 lr: 0x023f8a78 ctr: 0x023f8a74 vrsave: 0x00000000
A disassembly of F_ARROW follows below, and F_ARROW + 100 equals 0x1652c, i.e. the _index_no_free call. (Disregard the 0x1654c address in the trace earlier since this is a slightly newer build.)
_opcode_F_ARROW: 000164c8 mfspr r0,lr 000164cc bcl 20,31,0x164d0 000164d0 stw r31,0xfffc(r1) 000164d4 rlwinm r3,r3,2,0,29 000164d8 mfspr r31,lr 000164dc stw r30,0xfff8(r1) 000164e0 stw r29,0xfff4(r1) 000164e4 stw r0,0x8(r1) 000164e8 li r0,0x6 000164ec addis r30,r31,0x22 000164f0 stwu r1,0xffa0(r1) 000164f4 lwz r29,0xec94(r30) 000164f8 addi r5,r1,0x38 000164fc sth r0,0x38(r1) 00016500 li r0,0x1 00016504 lwz r9,0x10(r29) 00016508 lwz r4,0x0(r29) 0001650c lwz r2,0x40(r9) 00016510 addi r4,r4,0xfff8 00016514 lwz r9,0x14(r2) 00016518 lwz r2,0x4c(r9) 0001651c lwzx r9,r3,r2 00016520 addi r3,r1,0x40 00016524 sth r0,0x3a(r1) 00016528 stw r9,0x3c(r1) 0001652c bl _index_no_free 00016530 lwz r2,0x0(r29) 00016534 lhz r0,0xfff8(r2) 00016538 addi r3,r2,0xfff8 0001653c cmplwi cr7,r0,0x7 00016540 bgt cr7,0x16560 00016544 lwz r2,0x4(r3) 00016548 lwz r9,0x0(r2) 0001654c addi r9,r9,0xffff 00016550 cmpwi cr7,r9,0x0 00016554 stw r9,0x0(r2) 00016558 bgt+ cr7,0x16560 0001655c bl _really_free_svalue 00016560 lwz r2,0xec94(r30) 00016564 lwz r0,0x40(r1) 00016568 lwz r11,0x44(r1) 0001656c addi r1,r1,0x60 00016570 lwz r9,0x0(r2) 00016574 stw r0,0xfff8(r9) 00016578 stw r11,0xfffc(r9) 0001657c lwz r0,0x8(r1) 00016580 lwz r29,0xfff4(r1) 00016584 mtspr lr,r0 00016588 lwz r30,0xfff8(r1) 0001658c lwz r31,0xfffc(r1) 00016590 blr
On Sat, 8 Nov 2008, Peter Bortas @ Pike developers forum wrote:
Hi I could help with client certificates, what do you need ? (I'm a PKI-consultant at day time and the debian package maintainer of caudium at nighttime so here my two personas cross way :-)
Me and grubba have destilled the CHANGES to these two remaining:
o SSL
FIXME: client certificates: examples?
No release before Bill provides some.
o Kerberos
FIXME
No release before mast writes this.
I need a short example on how to use them in Pike. Preferably with a intelligent and tought provoking description than I can edit down to one line and shove into CHANGES.
pike-devel@lists.lysator.liu.se