Michael A. Peters wrote:
John Allsopp wrote:
Well no they are not logged in, it's just an embedded iframe so that's
my main issue with my method, anyone could look at the web page
source, pinch the URL of the iframe and they'd have the username and
password.
I think the only way to do it is
John Allsopp wrote:
Well no they are not logged in, it's just an embedded iframe so that's
my main issue with my method, anyone could look at the web page source,
pinch the URL of the iframe and they'd have the username and password.
I think the only way to do it is to make a key per referrin
John Allsopp wrote:
Robert Cummings wrote:
Ashley Sheridan wrote:
On Fri, 2010-02-12 at 16:12 -0500, Robert Cummings wrote:
John Allsopp wrote:
Hi everyone
There may be blinding bits of total ignorance in this so don't
ignore the obvious.
This is a security question, but a sentence of ba
At 12:36 PM + 2/13/10, John Allsopp wrote:
Sorted, I think .. unless you spot any faulty reasoning in the
above. Thanks very much guys :-)
The faulty reasoning is that you want to provide something to a
select group of people but are exposing it to the world. That's not
going to work.
Robert Cummings wrote:
Ashley Sheridan wrote:
On Fri, 2010-02-12 at 16:12 -0500, Robert Cummings wrote:
John Allsopp wrote:
Hi everyone
There may be blinding bits of total ignorance in this so don't
ignore the obvious.
This is a security question, but a sentence of background: I'm
writin
On Sat, Feb 13, 2010 at 7:33 AM, Ryan Sun wrote:
> In that case, referer is for authentication, and id is for authorization, I
> think
>
> On Fri, Feb 12, 2010 at 6:23 PM, Ashley Sheridan
> wrote:
>
> > On Fri, 2010-02-12 at 18:25 -0500, Ryan Sun wrote:
> >
> > authenticate by remote domain name
In that case, referer is for authentication, and id is for authorization, I
think
On Fri, Feb 12, 2010 at 6:23 PM, Ashley Sheridan
wrote:
> On Fri, 2010-02-12 at 18:25 -0500, Ryan Sun wrote:
>
> authenticate by remote domain name or remote ip
>
> $_SERVER['HTTP_REFERER']
>
> then your clients wi
On Fri, 2010-02-12 at 18:25 -0500, Ryan Sun wrote:
> authenticate by remote domain name or remote ip
>
> $_SERVER['HTTP_REFERER']
>
> then your clients will not have to put their username/password in clear text
> http://www.mydomain.com?h=300&w=250
> and you will just check if you have their dom
authenticate by remote domain name or remote ip
$_SERVER['HTTP_REFERER']
then your clients will not have to put their username/password in clear text
http://www.mydomain.com?h=300&w=250
and you will just check if you have their domain on your list
I'm not sure if there is better one but
" 'HTTP_
Ashley Sheridan wrote:
On Fri, 2010-02-12 at 16:12 -0500, Robert Cummings wrote:
John Allsopp wrote:
Hi everyone
There may be blinding bits of total ignorance in this so don't ignore
the obvious.
This is a security question, but a sentence of background: I'm writing
software for a mapping
On Fri, 2010-02-12 at 16:12 -0500, Robert Cummings wrote:
> John Allsopp wrote:
> > Hi everyone
> >
> > There may be blinding bits of total ignorance in this so don't ignore
> > the obvious.
> >
> > This is a security question, but a sentence of background: I'm writing
> > software for a mappi
John Allsopp wrote:
Hi everyone
There may be blinding bits of total ignorance in this so don't ignore
the obvious.
This is a security question, but a sentence of background: I'm writing
software for a mapping/location website and I want to be able to provide
something others can plug into t
Hi everyone
There may be blinding bits of total ignorance in this so don't ignore
the obvious.
This is a security question, but a sentence of background: I'm writing
software for a mapping/location website and I want to be able to provide
something others can plug into their website that wou
13 matches
Mail list logo
