other comment or point of view?
BR,
Emilien
-Message d'origine-
De : nut-upsdev-bounces+emilienkia=eaton@lists.alioth.debian.org
[mailto:nut-upsdev-bounces+emilienkia=eaton@lists.alioth.debian.org] De la
part de Arjen de Korte
Envoyé : vendredi 7 janvier 2011 20:59
À : nut-upsdev
2011/1/10 Arjen de Korte nut+de...@de-korte.org
mailto:nut%2bde...@de-korte.org
Citeren emilien...@eaton.com:
The main reason is to homogenize directive names
between apps (mainly upsmon which uses
2011/1/10 Arjen de Korte nut+de...@de-korte.org
mailto:nut%2bde...@de-korte.org
Citeren emilien...@eaton.com:
The main reason is to homogenize directive names
between apps
-Message d'origine-
De :
nut-upsdev-bounces+emilienkia=eaton@lists.alioth.debian.or
g
[mailto:nut-upsdev-bounces+emilienkia=eaton@lists.alioth.d
ebian.org] De la part de Arjen de Korte
Envoyé : mardi 11 janvier 2011 22:15
À : nut-upsdev
Objet : [Nut-upsdev] Client
-Message d'origine-
De :
nut-upsdev-bounces+emilienkia=eaton@lists.alioth.debian.or
g
[mailto:nut-upsdev-bounces+emilienkia=eaton@lists.alioth.d
ebian.org] De la part de Arjen de Korte
Envoyé : mercredi 12 janvier 2011 09:59
À : nut-upsdev@lists.alioth.debian.org
Hi all,
After client's certificate verifications discussion in the mailing-list,
I have done some tests with nut trunk and - if my config is not too bad
- I think ther is a bug with server certificate verification.
With a clean trunk checkout, compile and installation; and with the
following
Hi all,
I have tested with many configurations and whatever certificate
configuration (with, without, self-signed or not) used, server
certificate is always approved.
Reverting commit r2819 seems fixing the problem.
Index: /trunk/clients/upsclient.c
Hi all,
I am pleased to announce that NSS port of NUT is finished.
Port is fully functionnal (same functionnalities as openssl, and a
not-activated-by-default client certificate validation function) and
successfully tested by myself (external tests are pending, Frederic Bohe
is planned for) with
2011/6/12 Charles Lepple clep...@gmail.com
On Jun 12, 2011, at 12:48 PM, Arnaud Quette wrote:
2011/6/12 Charles Lepple clep...@gmail.com
On Jun 11, 2011, at 3:53 PM, Arnaud
This mail is a reply to mails from Charles Lepple and Petr Kubánek dated from
july 7 with the same topic.
From: Charles Lepple
One thing with SWIG (and other binding systems) is that it is not
easy to handle errors gracefully. I can't count how many times I got
segmentation violation
Hi Thomas
-Message d'origine-
De :
nut-upsdev-bounces+emilienkia=eaton@lists.alioth.debian.or
g
[mailto:nut-upsdev-bounces+emilienkia=eaton.com@lists.alioth.d
ebian.org] De la part de Thomas Jarosch
Envoyé : dimanche 28 août 2011 01:03
À : nut-upsdev@lists.alioth.debian.org
Hi Thomas
-Message d'origine-
De :
nut-upsdev-bounces+emilienkia=eaton@lists.alioth.debian.or
g
[mailto:nut-upsdev-bounces+emilienkia=eaton.com@lists.alioth.d
ebian.org] De la part de Thomas Jarosch
Envoyé : dimanche 28 août 2011 01:04
À : nut-upsdev@lists.alioth.debian.org
Hi,
One minor thing: the @author tags in the javadoc comments
should probably have the angle brackets around the email
address escaped as lt; and gt;, or the email address
should be dropped. At least the version of javadoc on my
system is treating the email address like an HTML tag.
One minor thing: the @author tags in the javadoc comments
should probably have the angle brackets around the email
address escaped as lt; and gt;, or the email address
should be dropped. At least the version of javadoc on my
system is treating the email address like an HTML tag.
Done
14 matches
Mail list logo
