Pike-devel December 2021

pike-devel@lists.lysator.liu.se

3 participants
4 discussions

Pike debugger update
by H William Welliver 23 Dec '21

23 Dec '21

Hello all- I’ve got a little free time on my hands again and am planning on spending a bit of time working on the pike debugger prototype. My first effort will be to merge the existing support into the development branch so that it gets a little more exposure. I plan on doing this as a series of commits: the C-level changes, the low-level Pike code and finally the Debug Adapter Protocol support. I don’t expect this to cause any problems for people not using the debugger, but hopefully merging it will make it a lower effort to test. There should be a more complete message about this proposal (and I didn’t get any pushback) so assume it’s still okay to proceed. Please do get in touch if there are any reservations. The second effort that I’d like to tackle is figuring out a way to perform code evaluation at a particular stack frame. I think this is the major missing “base function” that’s currently missing. I’d be pleased to hear any suggestions you might have for how best to accomplish this. I was thinking that the hilfe code might provide a way, with global/local variable resolution via the live stack frame object that the debugger will have access to. Is there possibly a better way? Bill

1 0

New Pike stable release
by H William Welliver 23 Dec '21

23 Dec '21

Hello all- After a bit of a delay, I’m getting ready to cut a new 8.0 release candidate. If anyone still has any remaining commits bound for 8.0, let me know they’re coming (I know it’s a busy time of year, so a quick note is all I’d need right now). If I don’t hear anything by Sunday 1200UTC, I’ll start working on the release. Any comments or questions are welcome! Many thanks for everyone’s contribution this year and I hope you have a wonderful festive season! Bill

1 0

Redis protocol
by Ignasi Cavero 06 Dec '21

06 Dec '21

Hello, I've written a Pike module that implements the Redis protocol (https://redis.io) Licensed under LGPLv3, but if you need another license, please contact me. https://glog.org/Pike/Redis.tar.gz -- *Ignasi Cavero* Técnico de I+D+i | R&D Technician ignasi(a)lleida.net (+34) 652 813 884 *Parc Científic i Tecnològic Agroalimentari de Lleida* Edifici H1 2a planta B | 25003 Lleida (Spain) Tel. 902 999 272 | (+34) 973 282 300 Fax (+34) 973 282 195 www.lleida.net <http://www.lleida.net> Política de privacidad <http://www.lleida.net/es/privacy.html>

1 0

Bug in ccm glue?
by Niels M�ller (entering a radioactive zone) ＠ Pike (-) developers forum 03 Dec '21

03 Dec '21

Hi, I've received a bug report (from someone at Opera) about a crash when using Crypto.AES.CCM. Example int main() { mixed state1 = Crypto.AES.CCM.State(); state1->set_encrypt_key(String.hex2string("bedcfb5a011ebc84600fcb296c15af0d")); state1->set_iv(String.hex2string("438a547a94ea88dce46c6c85")); state1->update(String.hex2string("")); string ct = state1->crypt(String.hex2string("")); state1->digest(); return 0; } When I try it (with Pike v8.0, installed as a debian package on x86_64) it segfaults in nettle_memxor3. As far as I can tell from 5 minutes of printf debugging, crash is inside the call to ->digest(). The set_iv method looks a bit suspicious to me, it doesn't include the required arguments for the nettle function ccm_set_nonce (and ccm is generally a bit messier to setup than most other modes). See http://www.lysator.liu.se/~nisse/nettle/nettle.html#index-ccm_005fset_005fn… There may of course be some problem in the nettle library too, in particular, I would be happier if api misuse resulted in an assert failure rather than a segfault.

2 3

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 December 2021