Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

Re: pike docker images
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 14 Feb '24

14 Feb '24

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the 3 month mark from the latest conference is coming up soon, it seems time to announce the first such meeting for 2024: Pike Meet-up 2024-Q1 Date: 2024-02-17 (Sat) Time: 10:00 - afternoon/evening Place: Roxen IS AB S:t Larsgatan 22A Linköping Welcome! /grubba

3 4

Debian Pike packaging and GTK2
by Chris Angelico 04 Feb '24

04 Feb '24

The latest releases of Debian don't include a pike8.0-gtk package any more. Apparently it's because it depends on old libraries: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885673 But all of those are optional dependencies. I just tested a fresh Debian 12 installation and was able to build Pike from source fairly easily. As long as libgtk2.0-dev is installed, the majority of the GTK2 module exists, and it's only GTK2.SourceView etc that are missing. How would we go about getting Pike GTK back into Debian? ChrisA

1 0

Re: Client certificate support in Sql.pgsql?
by william＠welliver.org 12 Jan '24

12 Jan '24

Hi Chris, the SSL module supports passing client certificates, and the Sql.pgsql module uses SSL.File, however it doesn't directly provide any hooks for configuring the client certs. I think it would be easy to add, basically you just need a way to pass a properly configured SSL.Context object to the SSL.File object in (I think the relevant place is in Sql.pgsql_util.pmod). Once that's done, the handshake process should see the client certs and then pass them when requested by the server. As a side note, I think anything that offers TLS support should provide a means for passing a Context, as that's where all of the configuration is done. I don't think that is currently the case, and might be a worthwhile side project. I'm a bit swamped here, otherwise I'd offer some tested code, but I think it be fairly straightforward to add a constructor variant to Sql.pgsql and the associated wiring below it. If you've got specific questions, I'm happy to try to answer them (I wrote the initial client cert support many, many years ago). Bill On 2023-12-03 19:51, Chris Angelico wrote: > Is it possible to use client SSL certificates for authentication with > the Sql.pgsql or (the deprecated) Sql.postgres driver? I've been > setting up a multihomed Pike program and would ideally like to be able > to have all nodes connect to the same database, using their SSL > certificates as proof of identity. In theory, this should work, but > I've had no success. Anyone done this and if so, how? > > The connection works in the command line psql interface, but not in > Pike. > > ChrisA

3 14

None
by None 08 Mar '22

08 Mar '22

| If the result is a BLOB then the sqlite3_column_bytes() routine | returns the number of bytes in that BLOB. No type conversions | occur. If the result is a string (or a number since a number can be | converted into a string) then sqlite3_column_bytes() converts the | value into a UTF-8 string and returns the number of bytes in the | resulting string. The value returned does not include the \000 | terminator at the end of the string. The sqlite3_column_bytes16() | routine converts the value into a UTF-16 encoding and returns the ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | number of bytes (not characters) in the resulting string. The \u0000 | terminator is not included in this count. As far as I can see, it does perform conversions internally, and they will most likely fail if the inserted data isn't properly encoded. >Regards, >/Al

1 0

None
by None 08 Mar '22

08 Mar '22

/* Macros for aggregating results built on the stack into an array, * while maintaining a bound on stack consumption. Use like this: * * check_stack(120); * BEGIN_AGGREGATE_ARRAY(estimated_size_of_final_array) { * for (...) { * ... stuff that produces a value on the stack ... * DO_AGGREGATE_ARRAY(120); * ... * } * } END_AGGREGATE_ARRAY; * * The array is left on top of the stack. */

1 0

None
by None 08 Mar '22

08 Mar '22

error prone to me :) Just to be sure: > Stdio.File("/tmp/foo", "r")->mode(); (2) Result: 4099 -- Bertrand LUPART Linkeo.com - R&D | http://www.linkeo.com/ +33 1 72 71 71 82 | 17, rue de la Banque - F75002 Paris Systèmes de gestion d'email entrant | Email management systems

1 0

None
by None 08 Mar '22

08 Mar '22

xenofarm_result.tar file could be gzipped: ----8<----8<----8<----8<---- cd xenofarm_result && tar cf - . > ../xenofarm_result.tar gzip -f9 xenofarm_result.tar ---->8---->8---->8---->8---- $ pwd ~/Code/Pike/xenoclient/pike-7.7/nutella/buildtmp/Pike-v7.7-snapshot $ cd xenofarm_result $ pwd ~/Code/Pike/xenoclient/pike-7.7/nutella/buildtmp/Pike-v7.7-snapshot/xenofarm_result $ tar cf - . > ../xenofarm_result.tar $ ls buildid.txt configcache.txt _core.txt compilelog.txt configlogs.txt mainlog.txt $ gzip -f9 xenofarm_result.tar gzip: xenofarm_result.tar: No such file or directory Shouldn't the last line be "gzip -f9 ../xenofarm_result.tar" instead? -- Bertrand LUPART Linkeo.com - R&D | http://www.linkeo.com/ +33 1 72 71 71 82 | 17, rue de la Banque - F75002 Paris Systèmes de gestion d'email entrant | Email management systems

1 0

None
by None 08 Mar '22

08 Mar '22

attributes to UNIX protection mode flags. / Henrik Grubbström (Lysator) Previous text: >2004-04-06 15:17: >Subject: WINAPI >-------------------------------------------------------------------- >My guess is that dtox means "DOS to UNIX" and sets line end conversion. > > / Martin Nilsson (provokatör) >

1 0

None
by None 08 Mar '22

08 Mar '22

/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-02-07 17:02: >Subject: sscanf and Gmp.mpq >-------------------------------------------------------------------- >Would it hurt much to feed the constructor the remainder of the string >and have the genereated object remember how much of it that it wanted? > > / Johan Sundström (Achtung Liebe!) >

1 0

None
by None 08 Mar '22

08 Mar '22

over the past days (and I may be off by a mile here), the current set of Caudium/PExt modules (ab)use some or other pike aclocal.m4 macros in an aclocal/automake context, somehow leading to the uncomfortable situation with the debian packages' redistribution of those internals to an overly exposed location. Is that the case (leading to the small skirmish conflict of whether the bug is in pike, or in those modules), or is there no particular rational argument behind keeping "pike -x module" in its current broken state (except for "I am not familiar with this, do not use it myself and haven't had the time to look at it closely yet", as I believe Marek has almost said) for the benefit of those modules? (I've really been trying to understand Marek's point of view, despite not being fully educated on automake and friends.) / Johan Sundström (Achtung Liebe!) Previous text: >2004-01-27 16:54: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >The one and only way to compile Pike modules that should be endorsed >and/or developed is "pike -x module". That's it. If it doesn't work >it. If it requires the entirety of Pike, deal with it. > >That's about all I have to say. > > / David Hedbor >

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel