Bug#1053533: mbedtls: enable MBEDTLS_NIST_KW_C
Source: mbedtls Severity: wishlist X-Debbugs-Cc: phco...@silabs.com, jerome.pouil...@gmail.com Hello, I have just noticed MBEDTLS_NIST_KW_C was not enabled (and obviously my project[1] depends on it). I usually use the default config provided by mbedtls (which I believe enable all the possible options). Do you know if there is any reason to strip down this configuration? [1] https://github.com/SiliconLabs/wisun-br-linux -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-12-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1027861: linux: consider enabling CONFIG_IPV6_RPL_LWTUNNEL
Source: linux Severity: wishlist Tags: ipv6 X-Debbugs-Cc: jerome.pouil...@gmail.com Hi folks, "RPL Source Routing Header" (CONFIG_IPV6_RPL_LWTUNNEL) is currently disabled. It seems it is only an oversight since this option is not explicitly mentioned in debian kernel config file (and features like "Segment Routing Header encapsulation" are enabled while they are very close of "RPL Source Routing Header"). We consider to use RPL Source Routing Header in our implementation of border router for Low-Power and Lossy Networks[1]. So, I would be very glad to see this option enabled on Debian. FYI, I have build a custom kernel with this option enabled without any pain. I could send a patch if you need. Thank you, [1]: https://github.com/SiliconLabs/wisun-br-linux -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.10-custom (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1001555: (no subject)
Before 8.10-3 I was able to connect to my VPN using gp-saml-gui[1]. It would be great if we could keep compatibility with existing scripts. [1]: https://github.com/dlenski/gp-saml-gui -- Jérôme Pouiller
Bug#996726: Some other questions
On Friday 5 November 2021 03:02:13 CET Norbert Preining wrote: > > After 2 weeks, the bug has finally been fixed. But I wonder why the bug > > wasn't tested out in the unstable branch and was pushed into the testing > > Because on unstable everything worked. The bug happens only due to > different transition times from unstable to testing. This cannot be > tested in unstable before. Is there a way to avoid this problem happen in the future? -- Jérôme Pouiller
Bug#310495: any chances to fix the par?
On 2013-09-03 10:39, Jérôme Pouiller wrote: Hi, To be fair, I wrote patch for unicode support in par 5 years ago. I know where are some issues on this patch but I have never had time to fix them. Although, I wrote a new version of the patch: http://sysmic.org/dl/par/par_1.52-i18n.4.patch I really not sure it would fix all issues, but, it may help. As Sergiusz noticed it, this patch is not an unified patch. So it is easy to apply. I regenerated it and place it on same location. In add, I generated corresponding debian packages here: http://sysmic.org/dl/par/debian/par_1.52-4_amd64.deb http://sysmic.org/dl/par/debian/par_1.52-4.dsc http://sysmic.org/dl/par/debian/par_1.52-4.diff.gz http://sysmic.org/dl/par/debian/par_1.52.orig.tar.gz http://sysmic.org/dl/par/debian/par_1.52-4_amd64.changes I repeat these modifications was wrote 5 years ago, and I had never had time to really test it. -- Jérôme Pouiller, Sysmic Embedded Linux specialist http://www.sysmic.fr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#310495: any chances to fix the par?
Hi, To be fair, I wrote patch for unicode support in par 5 years ago. I know where are some issues on this patch but I have never had time to fix them. Although, I wrote a new version of the patch: http://sysmic.org/dl/par/par_1.52-i18n.4.patch I really not sure it would fix all issues, but, it may help. -- Jérôme Pouiller, Sysmic Embedded Linux specialist http://www.sysmic.fr -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#310495: [EMAIL PROTECTED]: Re: [PATCH] Add multibyte support]
Le mardi 3 octobre 2006 07:09, Kapil Hari Paranjape a écrit : However, I am still unable to get *any* reasonable output from this input for your version of par. There may be something wrong in my settings so I am sending you my environment variables and the output of par jez.out kapil.out. Your variable PARINIT contains 'rTbqgR B=.,?_A_a Q=_s|'. If you remove option 'g', it work well. Nevertheless, option 'g' shouldn't produce this. It is a bug. I try to correct it today. -- Jérôme Pouiller (Jezz) jezz AT sysmic DOT org
Bug#310495: [EMAIL PROTECTED]: Re: [PATCH] Add multibyte support]
Le mardi 3 octobre 2006 11:02, Kapil Hari Paranjape a écrit : On Tue, 03 Oct 2006, Jérôme Pouiller wrote: [...] Nevertheless, option 'g' shouldn't produce this. It is a bug. I try to correct it today. Thanks for this. Yes. It works now. As you say the problem is with the character tests in reformat.c. These are the character tests (like isalnum) for single-width characters. We need to include the character tests for wide characters (iswalnum). I havn't notice any use of functions for single-width characters. But, during processing of option 'g', I didn't updade correctly width of words. It is now fixed. I have fiwed warning during compilation too. You can find all files par_1.52-i18n.3* on http://sysmic.org/par/debian. bye, -- Jérôme Pouiller (Jezz) jezz AT sysmic DOT org
Bug#310495: [EMAIL PROTECTED]: Re: [PATCH] Add multibyte support]
Le samedi 16 septembre 2006 03:22, Kapil Hari Paranjape a écrit : On Fri, 15 Sep 2006, Jérôme Pouiller wrote: Le Ven 15 septembre 2006 9:14, Kapil Hari Paranjape a écrit : [...] 2. From the 'par' built by you as well as the one built by me I am unable to get the 'correct' output for the sample file that was submit by the original submitter of the bug report #310495. Is there some specific environment variable that needs to be set or unset? Yes, your current charset ñust be identic to charset of input text. Something like export LANG=en_IE.UTF-8 should make output correct. My current LANG environment variable is en_IN.UTF-8. I would be grateful if you would download the text given by the original submitter in the bug report and check that your version of par manages to format it correctly. I haven't been able to do that here so far ... Actually, my result is different from result submitted in bug report. I send in attachement my result (mine.out), text given in bug report (your.out) and diff between them (diff). Have you same results than me? Results are different but, I don't think your.out is better than mine.out. What do you think about? -- Jérôme Pouiller (Jezz) jezz AT sysmic DOT org http://sysmic.org 1,2c1,2 Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen --- Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen 5c5 kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä --- kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä 9,10c9,10 par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä --- par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä 15c15 kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä --- kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä 17c17 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, --- -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset ja UTF-8 -koodaus toimivat par-työkalun kanssa. Tässä tyhjänpäiväinen virke, jonka avulla testaan, kuinka ääkköset
Bug#310495: [EMAIL PROTECTED]: Re: [PATCH] Add multibyte support]
Le Sam 16 septembre 2006 3:22, Kapil Hari Paranjape a écrit : On Fri, 15 Sep 2006, Jérôme Pouiller wrote: Le Ven 15 septembre 2006 9:14, Kapil Hari Paranjape a écrit : [...] 2. From the 'par' built by you as well as the one built by me I am unable to get the 'correct' output for the sample file that was submit by the original submitter of the bug report #310495. Is there some specific environment variable that needs to be set or unset? Yes, your current charset ñust be identic to charset of input text. Something like export LANG=en_IE.UTF-8 should make output correct. My current LANG environment variable is en_IN.UTF-8. I would be grateful if you would download the text given by the original submitter in the bug report and check that your version of par manages to format it correctly. I haven't been able to do that here so far ... Strange... I am currently in holidays. I will test this behaviour as soon as I will come back at home (1st October). best regards, -- Jérôme Pouiller (Jezz) jerome DOT pouiller AT sysmic DOT org
Bug#378301: juman: FTBFS: Segmentation fault during makepat
It'd seems real problem come from '-O2' option $ apt-get source juman cd juman-5.1 fakeroot ./debian/rules pre-build cd build-tree/juman-5.1 env CFLAGS='-O2' ./configure make do segfault but $ apt-get source juman cd juman-5.1 fakeroot ./debian/rules pre-build cd build-tree/juman-5.1 env CFLAGS='' ./configure make doesn't (notice default of CFLAGS is -O2 -g) I tried to execute valgrind on makepat (compiled without '-O2'), but, it found no errors. -- Jérôme Pouiller (Jezz) jezz AT sysmic DOT org
Bug#378301: juman: FTBFS: Segmentation fault during makepat
Le jeudi 3 août 2006 11:33, Jérôme Pouiller a écrit : I tried to execute valgrind on makepat (compiled without '-O2'), but, it found no errors. In fact, I didn't run correctly valgrind, there is only one error with CFLAGS=-g: ==32258== Conditional jump or move depends on uninitialised value(s) ==32258==at 0x4026754: getpath (iotool.c:145) ==32258==by 0x80487C2: main (makepat.c:46) Because strlen(JumanPath) == 0. It isn't our bug but, it'd be a good idea to correct it and with CFLAGS=-O2 -g, this error appears: ==1782== Use of uninitialised value of size 4 ==1782==at 0x8048A3E: main (makepat.c:68) makepat.c:68 match with return of main function. Surely, there is a buffer overflow while write in one of local variables of main function. So I have search an invalid acces to one these variables and it appears: char kugiri[1]; [...] sprintf(kugiri,\t); \t use two bytes, so this instruction overwrite some data of stack and program do segfault. I join patch to correct this bug: diff -r juman-5.1.orig/build-tree/juman-5.1/makepat/makepat.c juman-5.1/build-tree/juman-5.1/makepat/makepat.c 32c32 char kugiri[1]; /* �ڤ� */ --- char kugiri[2]; /* �ڤ� */ -- Jérôme Pouiller (Jezz) jezz AT sysmic DOT org
Bug#310495: [EMAIL PROTECTED]: Re: [PATCH] Add multibyte support]
Le mardi 1 août 2006 15:30, Jérôme Pouiller a écrit : Le vendredi 28 juillet 2006 13:04, Mohammed Adnène Trojette a écrit : On Mon, Jul 24, 2006, Mohammed Adnène Trojette wrote: It works well for me too. Great! I don't know what was the problem, but this version seems OK to me. It seems I was too fast. It still freeze when I launch it in vim. It works well on command line. I confirm this bug: $ par 50 EOF bla bla EOF bla bla ^C $ par version par 1.52-i18n.1 I thinks it is an error with use of strtok(). It shouldn't be very hard to resolve. I think, I can solve it before end of week. ok, it was a stupid bug: In par.c:719: wchar_t ch; should be char ch; this bug not appear in -O0. I have updated patch (http://sysmic.org/par/par-1.52-i18n.2.diff.gz), package (http://sysmic.org/par/debian/par_1.52-i18n.2_i386.deb), and all other stuffs (http://sysmic.org/par) PS : As suggested by some Debian mainteners, I have changed structure of my archive: * par_1.52.orig.tar.gz is original from Adam M. Costello * par-1.52-i18n.2.diff.gz is my patch * par-1.52-i18n.2.tgz is par_1.52.orig.tar.gz patched with par-1.52-i18n.2.diff.gz * debian/par_1.52.orig.tar.gz is a symbolic link on par_1.52.orig.tgz * debian/par_1.52-i18n.2.diff.gz is patch to apply to build debian package. This patch contains all debian stuff and my patch in debian/patches * debian/par_1.52-i18n.2_i386.deb is built package -- Jérôme Pouiller (jerome DOT pouiller AT sysmic DOT org)
Bug#310495: [EMAIL PROTECTED]: Re: [PATCH] Add multibyte support]
Le vendredi 28 juillet 2006 13:04, Mohammed Adnène Trojette a écrit : On Mon, Jul 24, 2006, Mohammed Adnène Trojette wrote: It works well for me too. Great! I don't know what was the problem, but this version seems OK to me. It seems I was too fast. It still freeze when I launch it in vim. It works well on command line. I confirm this bug: $ par 50 EOF bla bla EOF bla bla ^C $ par version par 1.52-i18n.1 I thinks it is an error with use of strtok(). It shouldn't be very hard to resolve. I think, I can solve it before end of week. -- Jérôme Pouiller (Jezz) jerome DOT pouiller AT sysmic DOT org
Bug#310495: [EMAIL PROTECTED]: Re: [PATCH] Add multibyte support]
Le mardi 11 juillet 2006 17:57, Mohammed Adnène Trojette a écrit : On Tue, Jul 11, 2006, Mohammed Adnène Trojette wrote: Please could upload a patched version of par in experimental, even if upstream has not integrated the patch yet? Just for information, with par rebuilt with your patch, par did not work any longer. Sorry for my belated answer, I was a little busy these days. How did you build it? Can you send me an exemple? What is your $LANG value? What is the behaviour? Is it crash? Version I have packaged (http://www.sysmic.org/par/par_1.52-i18n.1_i386.deb) seems work well. -- Jérôme Pouiller (jerome DOT pouiller AT sysmic DOT org)
