paragasu wrote:
if you want client to send encrypted form to server. then it must be
done using some kind of
client side script (javascript?).
I am using C++.
i don't think it is reliable.
Why would it not be reliable if I were using a public-key/private-key
encryption library which works both with PHP and C++ ?
why not just use https protocol. all data between client and server
will be encrypted.
The data must be encrypted/decrypted going both ways between the client
and the server. Does using https automatically do that ? If it does that
would be great.
On 1/1/09, Per Jessen <per@xxxxxxxxxxxx> wrote:
Edward Diener wrote:
Phpster wrote:
In reading the license I believe it refers to the gnupg itself, not
the application it may be embedded in. You are completely free to use
gnupg as you choose including modifying it to meet your needs.
I always thought the GNU public license demanded that any non-free
modules, which use any software distributed with this license, make
their source code freely available to end users. If this is either not
the case or no longer the case, then I will be glad to use GnuPG.
If you are distributing or selling your non-GPL software and you use GPL
software with it, then yes, I believe you are required to make your
source code available to the end-user too.
Maybe have a quick look at http://gpl-violations.org/
/Per Jessen, Zürich
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
