At 2:23 AM +0200 8/30/10, Bostjan Skufca wrote:
Hi tedd!
Reading this thread I assume you are doing RPC stuff when you are
expressing yourself as "the access" to database, which normaly
describes direct access to database.
In your case, you should divide the phrase "hacked server" into two
At 3:58 PM -0400 8/30/10, Paul M Foster wrote:
Is that about right?
Other than the fact that this solution should be rife with latency
issues, it seems like it would be secure.
I assume you're doing this as an academic exercise. If you had an actual
client who wanted to go to this much trouble
On Sun, Aug 29, 2010 at 12:24:31PM -0400, tedd wrote:
> Hi gangl:
>
> I realize that the problem stated herein has been solved by others,
> so I'm not claiming I've done anything new -- it's only new to me. It
> was a learning experience for *me* and my solution may help others.
>
> In any event
tedd wrote:
> And then there is the security involved in what happens *if* your
> server is hacked and all your "private" data is seen by a third
> party. What does all that entail -- and -- how you might be able
> protect yourself should be paramount in every developer's mind.
IMHO, not in a no
Hi tedd!
Reading this thread I assume you are doing RPC stuff when you are expressing
yourself as "the access" to database, which normaly describes direct access
to database.
In your case, you should divide the phrase "hacked server" into two separate
types of incidents (let's talk about your "ma
To all:
Part of the problem in discussing security is that there are all
sorts of security issues.
There is the obvious cleaning and scrubbing of data coming into your
site from outside sources such as from POST, GET, COOKIES, and such.
There's the security problem of communication between
tedd wrote:
> Like in this example, I use HTTPS in all the steps yet one responder
> said "use HTTPS". That means: 1) He didn't understand what I was
> saying; 2) He didn't read what I wrote, which probably the reason for
> #1.
You said "secure communication", which (in this context) is quite
cle
Jim Lucas wrote:
> Per Jessen wrote:
>> tedd wrote:
>>
>>> Hi gangl:
>>>
>>> I realize that the problem stated herein has been solved by others,
>>> so I'm not claiming I've done anything new -- it's only new to me.
>>> It was a learning experience for *me* and my solution may help
>>> others.
>>
At 10:31 AM -0700 8/29/10, Jim Lucas wrote:
Per Jessen wrote:
tedd wrote:
Hi gangl:
I realize that the problem stated herein has been solved by others,
so I'm not claiming I've done anything new -- it's only new to me. It
was a learning experience for *me* and my solution may help others.
In
Per Jessen wrote:
tedd wrote:
Hi gangl:
I realize that the problem stated herein has been solved by others,
so I'm not claiming I've done anything new -- it's only new to me. It
was a learning experience for *me* and my solution may help others.
In any event, I've finished creating a method f
tedd wrote:
> Hi gangl:
>
> I realize that the problem stated herein has been solved by others,
> so I'm not claiming I've done anything new -- it's only new to me. It
> was a learning experience for *me* and my solution may help others.
>
> In any event, I've finished creating a method for esta
On 29 August 2010 18:24, tedd wrote:
> Hi gangl:
>
> I realize that the problem stated herein has been solved by others, so I'm
> not claiming I've done anything new -- it's only new to me. It was a
> learning experience for *me* and my solution may help others.
>
> In any event, I've finished cre
12 matches
Mail list logo
