> Berin, > > well I don't know if it is the same reason as for > encryption. During the discussion I also asked > one of the WSS gurus about the topic. Here is his > answer to my question: > > <cite> > This behaviour is absolutely necessary in order that exclusive > canonicalization can function correctly in the case of > changes to apex definitions of the default namespace. The > canonicalization specifications should both have been > defined to always emit apex xmlns=""; this lack introduces > abstract security attacks against the default namespace which > specifications such as &wsse; and &decrypt; have to work around > with these ugly warts. > </cite> > from Merlin Hughes, Betrusted > > Does this info helps you? (I'm in no way an expert on this topic). > > Regards, > Werner >
Well, In the current c14n implementation changing the behaviour is only a how the symb table is create(i.e. When I create the symbol table the xmlns="" binding is marked as rendered, so it is not emitted), I can parametrized this behaviour. But what happend in the excl c14n when the xmlns is not visibly utilezed and it isn't in the inclusive string. Do we render it or not? Raul
