Re: [mv] How-To PGP 6.5

["Ron Phipps" <takedown@cdsnet.net>]

******    message to minivend-users from "Ron Phipps" <takedown@cdsnet.net>     ******

>> Hey All,
>>
>> I thought I would share my experiences with setting up PGP 6.5 and
Minivend
>> together in hopes to help others out...
>
>Thanks for the info, Ron! A series of 'how-to' documentation would be
>really helpful in flatening out this rather steep learning curve for MV.


What I'm planning to do is when we setup our next catalog is to document all
of the steps that I go through.  This latest installation and catalog have
been rushed due to an agressive schedule so there was not much time for
documentation (Although I'm kicking my self now).

>
>[key admin snipped]
>
>Another important step if you're running MV for a group of users and using
>the multi-group option is that you have to add the Minivend user to each
>new catalog user's group (if you use the common paradigm of having each
>user in their own group) so that MV can read the catalog files.


Thanks for the information.  For right now all the catalogs are owned and
ran by the user minivend.  Our current client would rather us do all the
maintenance so no need to look into groups...  yet! :)

>
>> 5.  Do as David Babler suggested, change the ENCRYPTOR variable in the
>> catalog.cfg to:
>>
>> Variable ENCRYPTOR /usr/bin/pgp_start.sh -fate __ORDERS_TO__ 2>/dev/null
>>
>> 6.  Make sure you do not change this line: (I had changed it to a 1,
when
>> the email orders were sent the copy to __ORDERS_TO__ was blank instead of
>> encrypted with the data)
>>
>> Route main      encrypt          0
>
>Well, there seems to be some Perl quoting issues involved and my original
>non-quoted, variable-refered combo doesn't seem to work well for all
>cases. Specifically, there seems to be differences among the several Perl
>encryption routines in Order.pm and whether or not the encryption program
>string makes it through without getting improperly parsed. The line above
>*should* work, but probably won't - it's just supposed to encrypt the
>whole email message and is independent of the credit_card definition. I
>*think* (Mike?) that the only safe way to set these are to ignore the main
>ENCRYPTOR variable and specify the whole pgp string for the
>encrypt_program IN DOUBLE QUOTES. This is actually how the documentation
>illustrates the route directive. Also, you can use the 'pgp_cc_key' and
>'pgp_key' variables and specify the key-id, though you will HAVE to
>specify the key with a leading '0x' to force shell quoting to give it to
>pgp correctly and use the %s token. One of the remaining problems seems to
>be how the encrypted email is formatted. With both 'encrypt' and
>'credit_card' set the resultant email is unreadable in Pine. Remove the
>mime multipart header line and it works - this may be what you're seeing
>as empty messages - although pretty much anything that pgp doesn't like
>will give you a really empty message. If the test mail is going to your
>Linux box, take a look at the mail file for the store owner and see if the
>message is truly empty or just broken.
>
>-Dave


I'm going to test again with these directives and see if I can get to the
bottom of the problem.  I viewed the messages in both outlook and pine both
return an empty message.  Viewing the message source in outlook produces
just the headers.  I have not used the %s and %f place holders for the
encrypt_program and think I will pass for right now since the credit card is
atleast encrypted.  Thanks for your help Dave.

-Ron


>
>-
>To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
>email with 'UNSUBSCRIBE minivend-users' in the body to
Majordomo@minivend.com.
>Archive of past messages: http://www.minivend.com/minivend/minivend-list
>

-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list