Package: tinyca
Version: 0.7.5-2
Severity: normal

My departement is R&D (Research and Development) and TinyCA apparently
calls OpenSSL without bothering to escape the special
characters. Creation of the CA then fails:

DEBUG call: /usr/bin/openssl req -new -keyform PEM -outform PEM -passin 
env:SSLPASS -config /home/bortzmeyer/.TinyCA/R&D/openssl.cnf -out 
/home/bortzmeyer/.TinyCA/R&D/cacert.req -key 
/home/bortzmeyer/.TinyCA/R&D/cacert.key -sha1
DEBUG: add to dn: FR
DEBUG: add to dn: Ile-de-France
DEBUG: add to dn: Saint-Quentin-en-Yvelines
DEBUG: add to dn: AFNIC
DEBUG: add to dn: R&D
DEBUG: add to dn: AFNIC Research & Development 
DEBUG: add to dn: [EMAIL PROTECTED]
DEBUG: add to dn: 
DEBUG: add to dn: 
DEBUG return: /usr/bin/openssl req -new -keyform PEM -outform PEM -passin 
env:SSLPASS -config /home/bortzmeyer/.TinyCA/R&D/openssl.cnf -out 
/home/bortzmeyer/.TinyCA/R&D/cacert.req -key 
/home/bortzmeyer/.TinyCA/R&D/cacert.key -sha1

sh: D/openssl.cnf: No such file or directory
sh: D/cacert.req: No such file or directory
sh: D/cacert.key: No such file or directory
error on line -1 of /home/bortzmeyer/.TinyCA/R
1779:error:02001002:system library:fopen:No such file or 
directory:bss_file.c:122:fopen('/home/bortzmeyer/.TinyCA/R','rb')


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages tinyca depends on:
ii  libgtk2-perl                  1:1.190-1  Perl interface to the 2.x series o
ii  liblocale-gettext-perl        1.05-4     Using libc functions for internati
ii  openssl                       0.9.8g-13  Secure Socket Layer (SSL) binary a

Versions of packages tinyca recommends:
ii  zip                           2.32-1     Archiver for .zip files

tinyca suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to