[Info-Ingres] #ingres IRC logs

DATABASE

Re: [Info-Ingres] #ingres IRC logs

Postby Grant Croker » Thu, 17 Sep 2009 20:21:15 GMT



See  http://www.**--****.com/ 
information on connecting including using your web browser as the IRC 
client.

regards

g

-- 
Grant Croker, Ingres Corp
Ingres PHP and Ruby maintainer
 http://www.**--****.com/ 
I'll be more enthusiastic about encouraging thinking outside the box when there's evidence of any thinking going on inside it.
     -- Terry Pratchett



Similar Threads:

1.[Info-Ingres] #ingres IRC channel on freenode.net

 XXXX@XXXXX.COM  wrote:
> 
> A quick check of the channels such as #mysql, #postgresql, and #linux
> shows serious numbers and interest. There are smaller channels for
> budding open source projects as well.
...
> I'd be interested in what others think?

The two are complementary, like the post and the telephone.  

I'm not a big IRC guy because I like the asychronicity of email, and I
agree with Roy that Ingres at this point is better off with one email
channel.  But the immediacy of IRC can be useful in its own right, and
will help the larger community if its denizens make the effort to forward
any useful outcomes to the mailing list.  

--jkl

2.#ingres IRC logs

3.[Info-ingres] [ingres] [Info-ingres] Dates users were created in Ingres

4.[Info-ingres] RES: [Info-ingres] RES: [Info-ingres] SQL Injection attacks

> -----Mensagem original-----
> De:  XXXX@XXXXX.COM  
> [mailto: XXXX@XXXXX.COM ] Em nome de Emiliano
> Enviada em: Monday, June 12, 2006 10:06 AM
> Para:  XXXX@XXXXX.COM 
> Assunto: Re: [Info-ingres] RES: [Info-ingres] SQL Injection attacks
> 
> On 2006-06-12, Leandro Pinto Fava < XXXX@XXXXX.COM > wrote:
> > Three years ago we had a case of SQL Injection against our web
portal of
> > students's info. This portal was made using ICE and reports in 1999
> > (with very bad security control). Now we have this portal made in
PHP
> > and the possibility of SQL injection is nearly null (I think :-().
We
> > had another web application (ASP) that suffered a successful SQL
> > injetcion too. The problems were corrected as well.
> 
> And (to hook into the delightful discussion I'm having with Roy), I'll
> bet you dimes to dollars that both were using query assembly.

The ASP app was, but the ICE app was not directly. Report Writer
internally should work with query assembly when passing parameters to
run a report.

> 
> The PHP function addslashes ought to protect you if you use it
> consistently. PHP ADODb has parameter binds, which are better.

Yes.

> 
> > In our case the problems were in the application layer.
> 
> HTML injection?

No, when I said application layer, I wanted to say the problem was not
in database server.

Leandro.

5.[Info-ingres] RES: [Info-ingres] RES: [Info-ingres] SQL Injection attacks

6. [Info-ingres] [Users] How to Log errors while executing ingres sql command

7. [Info-ingres] FW: [Users] How to Log errors while executing ingres sql command

8. [Info-ingres] copy and refresh the errlog.log while ingres is up



Return to DATABASE

 

Who is online

Users browsing this forum: No registered users and 74 guest