>On October 12, 2017 9:29:40 AM CDT, John Burrell <[email protected]> 
>wrote:
>>I'm using the systemd dev version of the BLFS book.
>>
>>When I do:
>>
>>/usr/sbin/make-ca -g
>>
>>I get:
>>
>>sed: -e expression #1, char 3: unexpected `,'
>>WARNING! /tmp/tmp.BboBPQ3a68/certdatanew.txt has no 'Revision' value.
>>Will run conversion unconditionally.
>>grep: /tmp/tmp.BboBPQ3a68/certs/*.tmp: No such file or directory
>>grep: /tmp/tmp.BboBPQ3a68/certs/*.tmp: No such file or directory
>>grep: /tmp/tmp.BboBPQ3a68/certs/*.tmp: No such file or directory
>>grep: /tmp/tmp.BboBPQ3a68/certs/*.tmp: No such file or directory
>>awk: fatal: cannot open file `/tmp/tmp.BboBPQ3a68/certs/*.tmp' for
>>reading (No such file or directory)
>>printf: usage: printf [-v var] format [arguments]
>>unable to load certificate
>>140454917710912:error:0D07207B:asn1 encoding
>>routines:ASN1_get_object:header too long:crypto/asn1/asn1_lib.c:101:
>>unable to load certificate
>>140043819283520:error:0906D06C:PEM routines:PEM_read_bio:no start
>>line:crypto/pem/pem_lib.c:691:Expecting: TRUSTED CERTIFICATE
>>
>>plus a whole lot more. It ends with:
>>
>>
>>ls: cannot access '/tmp/tmp.BboBPQ3a68/ssl/certs/*.pem': No such file
>>or directory
>>Error! Only 0 certificates were generated!
>>Exiting without update!
>>
>>I haven't run the command as root as I use MSB's package management
>>method.
>>
>>Any suggestions would be appreciated
>>
>>Thanks
>>
>>jb.
>
>
>Somebody else mentioned a similar error to me. I guessing that I missed some 
>config that is not so >esoteric. I obviously didn't gaurd well enough and will 
>get a look at it this evening. You can grab a copy >of the certdata.txt file 
>and add the -c switch in the interim. man make-ca[8]. Also, for pkgusers, 
>there is >a destination switch so that you can do the extract and build in a 
>separate directory and move into place >after the fact if you prefer. As far 
>as using it, however, I'm not sure you should be running make-ca as the 
>>pkguser. Are other shared configuration files or common data files owned by 
>the pkguser?
>
>--DJ

I downloaded a certdata.txt file and used the -C and -D options as you 
suggested. It all worked fine.

Almost all installed files are owned by the pkguser.  I would rather not 
install any files as root as this will screw up the pkg mngt process, as you 
can imagine.

jb.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to