Re: passdb TODO list
Jeremy Allison wrote: On Sat, Jun 15, 2002 at 12:25:42AM +1000, Andrew Bartlett wrote: Otherwise, all strings are 'unix strings'. But what character set is a unix string ? What if we get an incoming UCS2 string that doesn't map ? We need to use utf8 in all the backends. This is a good chance to fix this mess once and for all and I think we should take it. Certainly, I think that the backends that have a 'native' character set should use it - that is, LDAP and LDAPv3 servers should use UTF8, and I'm sure that idra would probably like tdbsam2 to use UCS2. As to the others, and things like secrets.tdb, we probably should use UTF8, but the case is far less strong... (becouse the current setup allows it to be changed, which may or may not be a good thing). Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
passdb TODO list
I figured I might just jot down some ideas for the future of the passdb subsystem, as well as some of the more immediate todo items: Actually use the 'unload' passdb code. Currently we don't ever shut down the passdb, execpt on error. We are going to need to do this kind of stuff if we are to make pdb_xml work (for example). Also, we need to get interface versioning going: We have just changed the interface, but we didn't tell anybody :-) (SID stuff). I would like to get pdb_xml into Samba at some stage. What do people think of the idea? (Its a passdb that exports to XML in order to allow backups/hand updates pdb backends, tdbsam in particular.) I've not looked at it much, but it does require the basic stuff like new configure magic (to detect the XML lib etc). http://people.nl.linux.org/~jelmer/downloads/ I'm sure there is more, so I'll probably add to this later. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
Re: passdb TODO list
Toomas Soome wrote: I cave an question regarding to pdb_ interface. in 2.2 pdb_nisplus code I translated some strings from dos to unix and vice-versa. this translation helped to manage information correctly from windows side and from unix side. now unix_to_dos and dos_to_unix calls are gone in 3.0, what should I do? is this translation needed at all in 3.0? passdb should not do any translation, unless it wants to use unicode or the backend uses a particular (fixed) encoding. Otherwise, all strings are 'unix strings'. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
Re: passdb TODO list
On Fri, Jun 14, 2002 at 05:02:58PM +0300, Toomas Soome wrote: I cave an question regarding to pdb_ interface. in 2.2 pdb_nisplus code I translated some strings from dos to unix and vice-versa. this translation helped to manage information correctly from windows side and from unix side. now unix_to_dos and dos_to_unix calls are gone in 3.0, what should I do? is this translation needed at all in 3.0? What we're going to need for 3.0 is to wrap all incoming system strings in a function that converts to internal format, and wrap all outgoing system strings in a function that converts back. Then we need to determine what we will store our strings in (probably utf8), then we need to write upgrade code that will convert from our current mix of DOS and UNIX codepages in databases into utf8. This is one of the reasons why 3.0 is further away than we think - this has to be done before we can get ready to ship. Jeremy.
Re: passdb TODO list
On Sat, Jun 15, 2002 at 12:25:42AM +1000, Andrew Bartlett wrote: Otherwise, all strings are 'unix strings'. But what character set is a unix string ? What if we get an incoming UCS2 string that doesn't map ? We need to use utf8 in all the backends. This is a good chance to fix this mess once and for all and I think we should take it. Jeremy.
Re: passdb TODO list
Yes, please do use utf8 in every backend or just expect data will come in in utf8 and remember to handle it properly inside the module if it does not cope well with the way you have to store things, maybe we could also get a bit further and suddendly change everything to talk UCS2 so keep it in mind too. On Fri, 2002-06-14 at 17:59, Jeremy Allison wrote: On Sat, Jun 15, 2002 at 12:25:42AM +1000, Andrew Bartlett wrote: Otherwise, all strings are 'unix strings'. But what character set is a unix string ? What if we get an incoming UCS2 string that doesn't map ? We need to use utf8 in all the backends. This is a good chance to fix this mess once and for all and I think we should take it. Jeremy. -- Simo Sorce - [EMAIL PROTECTED] Xsec s.r.l. via Durando 10 Ed. G - 20158 - Milano tel. +39 02 2399 7130 - fax: +39 02 700 442 399 signature.asc Description: This is a digitally signed message part
