+[ Curtis Maloney ]-
| On Fri, 30 Jun 2000, Andrew Kenneth Milton wrote:
| > Just to make those people who think "It will never happen to me" think
| > twice, the Australian Government Treasury site was hacked and lots of
| > banking details about lo
On Fri, 30 Jun 2000, Andrew Kenneth Milton wrote:
> Just to make those people who think "It will never happen to me" think
> twice, the Australian Government Treasury site was hacked and lots of
> banking details about lots of small businesses was released.
>
> The Australian Treasury was very hap
On Sat, Jun 10, 2000 at 07:58:48AM +1300, Graham Chiu wrote:
> >http://www.post1.com/home/ngps/zope/zsmime
>
> Any ETA on the Win32 binaries?
Real Soon Now! ;-)
Seriously, I've just compiled M2Crypto with Borland's BC++ 5.5 free
compiler suite and linked with MSVC-built Python and OpenSSL.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In article <[EMAIL PROTECTED]>, Ng Pheng Siong
<[EMAIL PROTECTED]> writes
>Take a look at ZSmime,
>
>http://www.post1.com/home/ngps/zope/zsmime
>
Hi,
Any ETA on the Win32 binaries?
- --
Regards, Graham Chiu
gchiucompkarori.co.nz
http://www.c
Hi there,
I know your post indicates you've thought about this, but you may want to
reconsider storing CC info at all. It's a trade off on convenience for the
customer and security precautions on your site. If you don't have the
numbers, that's one less thing an intruder could do with your info
On Thu, Jun 08, 2000 at 08:57:17PM -0400, R. David Murray wrote:
> You have a ZCommerce site. You accept credit cards, and securely
> communicate with a CC processor to verify the transacton. Now,
> you want to save the CC# and other info in case something needs
> to be done with it later
Hi,
> "RDM" == R David Murray <[EMAIL PROTECTED]> writes:
RDM> On Thu, 8 Jun 2000, Bill Anderson wrote:
>> Personally, I would store the actual data on a seperate server,
>> not accessible to the public.
RDM> Mmm. Yes, that makes it more secure. Still leaves the
RDM> quest
> -> > You have a ZCommerce site. You accept credit cards, and securely
> -> > communicate with a CC processor to verify the transacton. Now,
>
> Besides Bill's suggestion, keep all your servers behind a good
> firewall. One option is to use Linux IP Masquerading, having your
> webserver
-> I'd like to also have a one-box solution, though.
Ooh, that's bad JuJu. Keeping CC#s on the same box as your
webserver?
a) Pray there are no overflows/misconfigurations/etc. on the webserver
daemon.
b) Turn off EVERY other service on that box (even ssh has had a buffer
overflow).
-> > You have a ZCommerce site. You accept credit cards, and securely
-> > communicate with a CC processor to verify the transacton. Now,
Besides Bill's suggestion, keep all your servers behind a good
firewall. One option is to use Linux IP Masquerading, having your
webserver *and* dat
On Thu, 8 Jun 2000, Bill Anderson wrote:
> Personally, I would store the actual data on a seperate server, not
> accessible to the public.
Mmm. Yes, that makes it more secure. Still leaves the question
of encryption/decryption of the data and key management, but it
makes the cracking a lot less
"R. David Murray" wrote:
>
> OK, any of you out there who have thought about ecommerce, cryptography,
> and zope, I've got a design question for you. Actually, this question
> is independent of zope, but I need to solve it in a zope context.
>
> You have a ZCommerce site. You accept credit car
12 matches
Mail list logo
