On 1/7/2005 3:01 AM, Jacek Konieczny wrote:

> On Thu, Jan 06, 2005 at 11:04:50AM -0500, Vivek Khera wrote:
>> >Is it possible to limit slave slon access to the master database? Or
>> >will Slony work well if all slon processes run on the master node? 
>> >Would
>> >then it be possible that some change in slony data on the slave node
>> >will cause change in master database?
>> >
>> 
>> the slon processes can run anywhere that they can communicate to the 
>> requested DB.  I run all my slon processes on the same box.
> 
> Now, the question is: is it possible for a specially crafted database
> content (including the slony control structures) on the slave node to
> fool slon daemons to modify the master database? I don't mean the
> unknown bugs that may be there, but the Slony design or known
> bugs/limitations.

Yes, that is possible. The slon serving any node will read and execute 
events that are generated on another node. Those events are created by 
calling the appropriate functions on the other node and every superuser 
can do that, so cracking one node in a Slony-I setup is enough.

You will need to wait for the file based log propagation.


Jan

> 
> Greets,
> 	Jacek
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #