| chat.freenode.net #tryton log beginning Thu Jul 31 00:00:01 CEST 2008 | ||
| 2008-07-31 06:20 -!- udono(n=udono@dynamic-unidsl-85-197-25-158.westend.de) has joined #tryton | ||
| 2008-07-31 07:57 -!- Gedd(n=ged@77.109.115.178) has joined #tryton | ||
| 2008-07-31 08:42 <udono> Good Morning | ||
| 2008-07-31 09:07 -!- kultviech(n=kultviec@p549746D2.dip.t-dialin.net) has joined #tryton | ||
| 2008-07-31 09:30 -!- bechamel(n=user@user-85-201-14-207.tvcablenet.be) has joined #tryton | ||
| 2008-07-31 09:39 -!- cedk(n=ced@gentoo/developer/cedk) has joined #tryton | ||
| 2008-07-31 10:39 <FWiesing> good morning! | ||
| 2008-07-31 10:51 <cedk> Hey guys, it seems that tiny has now also take the states functionality | ||
| 2008-07-31 10:51 <cedk> http://amit-mendapara.blogspot.com/2008/07/whats-going-on.html | ||
| 2008-07-31 10:51 <cedk> they call it attrs | ||
| 2008-07-31 10:52 <cedk> at the point 7 | ||
| 2008-07-31 10:55 <cedk> it is here: http://bazaar.launchpad.net/%7Eopenerp/openobject-client-web/trunk/revision/1689 | ||
| 2008-07-31 10:55 <cedk> but it seems to be only for the webclient | ||
| 2008-07-31 10:58 <bechamel> cedk: what is "complex widget" and "simple widget" ? | ||
| 2008-07-31 11:00 <bechamel> cedk: and i don't understand why they use list like "[('state','=','draft')]" to define the condtition for an attribute, those list are useful for the db not in the client | ||
| 2008-07-31 11:01 <cedk> bechamel: because it is for the javascript | ||
| 2008-07-31 11:01 <bechamel> maybe is to convert them into javascript | ||
| 2008-07-31 11:01 <bechamel> :) | ||
| 2008-07-31 11:01 <cedk> bechamel: they can do eval | ||
| 2008-07-31 11:01 <cedk> of course it is really less powerfull than ower implementation | ||
| 2008-07-31 11:02 <cedk> and once again, it is only for the webclient and not for the gtk | ||
| 2008-07-31 11:02 <cedk> so it is impossible to have concistance between both | ||
| 2008-07-31 11:06 <cedk> bechamel: and I think complex widget are one2many and many2many | ||
| 2008-07-31 11:07 <cedk> bechamel: but I don't see what is complex there :-) | ||
| 2008-07-31 11:07 <bechamel> cedk: :) | ||
| 2008-07-31 11:10 <cedk> I begin to understand why etiny is so slow, they make the validation of field on the server side before :-) | ||
| 2008-07-31 11:13 <bechamel> cedk: what do you call validation of field | ||
| 2008-07-31 11:13 <cedk> bechamel: to see if a field is required, they call the server when you try to save it | ||
| 2008-07-31 11:14 <cedk> bechamel: but I suppose that there is many stuff like this | ||
| 2008-07-31 11:14 <bechamel> cedk: ok | ||
| 2008-07-31 11:15 <cedk> bechamel: otherwise, the logo looks good | ||
| 2008-07-31 11:15 <cedk> bechamel: I like the big one with the curve | ||
| 2008-07-31 11:15 <cedk> bechamel: and the circle with the footprint in green | ||
| 2008-07-31 11:16 <bechamel> cedk: i don't like the footprint in green :), i dont know why, i prefer non-color logo | ||
| 2008-07-31 11:18 <cedk> bechamel: for icon in top left border, I find this is good to have some color | ||
| 2008-07-31 11:19 <bechamel> cedk: the one i like is lost among o lot of circlr logo :) | ||
| 2008-07-31 11:20 <bechamel> if someone is following the conversation it's easier whit this: http://www.b2ck.com/~bch/logo.svg :) | ||
| 2008-07-31 11:21 <bechamel> cedk: for the green footprint: it's whit the black background ? | ||
| 2008-07-31 11:22 <cedk> I just fix the server to send the right mimetype for svg | ||
| 2008-07-31 11:22 <bechamel> cedk: good idea | ||
| 2008-07-31 11:24 <cedk> bechamel: with big black circle with small white circle | ||
| 2008-07-31 11:24 <FWiesing> cedk: I have a problem with my trytond - I send you an e-mail with the error-message | ||
| 2008-07-31 11:25 <FWiesing> cedk: I execute the sql-script - you sent me the link - yesterday and then all is working fine | ||
| 2008-07-31 11:25 <cedk> FWiesing: or you can post it on roundup like that if others have the same issue they will have the solution | ||
| 2008-07-31 11:25 <FWiesing> OK | ||
| 2008-07-31 11:26 <CIA-54> tryton: FWiesing roundup * #228/trytond didn't start after update: [new] After update this morning I can't start the trytond. I excute the sql-script yesterday - and then all is working fine. | ||
| 2008-07-31 11:29 <CIA-54> tryton: ced roundup * #228/trytond didn't start after update: [resolved] Ok I see there was a wrong commit that breaks the database creation. Now it is fixed, but all databases that was created after, can no ... | ||
| 2008-07-31 11:40 -!- kultviech(n=kultviec@p549746D2.dip.t-dialin.net) has left #tryton | ||
| 2008-07-31 12:19 -!- Timitos(n=Timitos@88.217.184.172) has joined #tryton | ||
| 2008-07-31 14:02 -!- markusleist(n=markus@212.14.79.210) has joined #tryton | ||
| 2008-07-31 14:31 <udono> cedk: in tryton/gui/window/dbcreate.py there is the tooltip for administrator password: This is the password of the user that have the rights to administer databases. This is not a Tryton user, just a super administrator. If you did not changed it, the password is 'admin' after installation. | ||
| 2008-07-31 14:31 <udono> 'This is not a Tryton user' seems silently wrong?! | ||
| 2008-07-31 14:32 <udono> or is it the password for the postgresuser? | ||
| 2008-07-31 14:32 <udono> no, it cant... | ||
| 2008-07-31 14:33 <cedk> udono: it is the password that is stored in trytond.conf | ||
| 2008-07-31 14:33 <udono> cedk: for which user? | ||
| 2008-07-31 14:33 <cedk> udono: there is no real user | ||
| 2008-07-31 14:34 <cedk> it is in etc/trytond.conf | ||
| 2008-07-31 14:35 <udono> cedk: its the admin_passwd | ||
| 2008-07-31 14:35 <cedk> udono: yes | ||
| 2008-07-31 14:35 <udono> cedk: but this is not the same like for the tryton user admin?! | ||
| 2008-07-31 14:35 <cedk> udono: no, it is different | ||
| 2008-07-31 14:36 <udono> cedk: ok | ||
| 2008-07-31 14:37 <udono> thx | ||
| 2008-07-31 14:47 <udono> cedk: This is a security issue, I think | ||
| 2008-07-31 14:48 <udono> cedk: someone is able to copy the databases... | ||
| 2008-07-31 14:48 <cedk> udono: it is just the paswword that is stored in the file | ||
| 2008-07-31 14:48 <cedk> udono: we must crypt it | ||
| 2008-07-31 14:49 <udono> cedk: we can autogenerate a password for each installation, like plone does | ||
| 2008-07-31 14:49 <cedk> udono: why you just have to change it | ||
| 2008-07-31 14:51 <udono> cedk: yes, but if someone forget... i would prefer a save solution with different passwords for each installation. If a user hasn't the right to read the tryton.conf, than he cant guess the password in any case... | ||
| 2008-07-31 14:52 <udono> cedk: It mustn't be done for the first release, but imho we should hold an eye on it... | ||
| 2008-07-31 14:53 <udono> cedk: I change the text of the tooltip: This is the Tryton password for database administration. It doesn't belong to a Tryton user. The password is defined in etc/trytond.conf under admin_passwd. | ||
| 2008-07-31 14:53 <udono> cedk: How do you find. Its just security by obscurity, but maybe better then nothing... | ||
| 2008-07-31 14:54 <cedk> udono: I will not put the admin_passwd stuff because it can perhaps change | ||
| 2008-07-31 14:55 <udono> cedk: everything changes... like yesterday when I recognized, we are working on dbcreate.py... my first merge ;-) | ||
| 2008-07-31 14:56 <cedk> udono: I don't like put stuff about the server in the client | ||
| 2008-07-31 14:56 <udono> cedk: which Tooltipsentence you prefer? | ||
| 2008-07-31 14:57 <cedk> udono: the same but without "The password is defined ..." | ||
| 2008-07-31 14:58 <udono> cedk: "This is the Tryton password for database administration. It doesn't belong to a Tryton user." But with this there is no way to find out which password to use... | ||
| 2008-07-31 15:03 <cedk> udono: ok, you can put a generic line with the password is configured on the server | ||
| 2008-07-31 15:03 <udono> cedk: "This is the Tryton password for database administration. It doesn't belong to a Tryton user. You may find it in the trytond configuration file" | ||
| 2008-07-31 15:04 <cedk> udono: without file, because we must find a better solution and I don't know if it will stay in the configuration file | ||
| 2008-07-31 15:04 <udono> cedk: ok | ||
| 2008-07-31 15:19 <udono> cedk: sorry, but some other questions... we have thee passwords for creating a database... why and what are the second ones? | ||
| 2008-07-31 15:20 <udono> cedk: and why a confirmation password? | ||
| 2008-07-31 15:21 <udono> cedk: is the admin password a new password? I thought it is already defined... | ||
| 2008-07-31 15:21 <Timitos> udono: there is a new wizard for creating a database | ||
| 2008-07-31 15:21 <Timitos> before this change the standard password of the user admin was 'admin' | ||
| 2008-07-31 15:22 <Timitos> now you can provide a password for user admin yourself when creating a new database | ||
| 2008-07-31 15:22 <cedk> udono: the first is from the config file and the two second will be the admin password of the db | ||
| 2008-07-31 15:23 <udono> cedk: a postgres password for a database role?! | ||
| 2008-07-31 15:23 <Timitos> the password from the configfile is to prevent that everybody can create a database | ||
| 2008-07-31 15:23 <cedk> udono: no for the user admin | ||
| 2008-07-31 15:25 <udono> Its not a benefit for understanding to name everything 'admin' :-S | ||
| 2008-07-31 15:25 <cedk> udono: I think about super admin for db creation | ||
| 2008-07-31 15:25 <cedk> or server password | ||
| 2008-07-31 15:25 <udono> ACTION feels like in the film 'Beeing John Malchowich' | ||
| 2008-07-31 15:26 <cedk> udono: Malchowich Malchowich Malchowich Malchowich or Malchowich Malchowich | ||
| 2008-07-31 15:26 <cedk> :-) | ||
| 2008-07-31 15:26 <udono> :-) | ||
| 2008-07-31 15:26 <cedk> or admin admin admin admin ! | ||
| 2008-07-31 15:27 <udono> or http://www.youtube.com/watch?v=XZ6N5m8FpVg | ||
| 2008-07-31 15:27 <Timitos> udono: i think you should try to change these passwords in your installation. so you will see, which password is used in what context | ||
| 2008-07-31 15:28 <cedk> I think "Server Password" is a good name | ||
| 2008-07-31 15:28 <udono> Timitos: Its not a Problem of understanding which password to use when... Its just to create a dialog an unaware user can understand... | ||
| 2008-07-31 15:29 <udono> The Super admin password changes to Server Password? This sounds better... | ||
| 2008-07-31 15:30 <Timitos> what about db maintainance password? is a litte bit long but i think this password is only used in this context | ||
| 2008-07-31 15:32 <udono> Timitos: db maintanance went into the direction "Its a password for the Database", but in fact it is a Password for the Tryton server, so I find Server Password a bit better. | ||
| 2008-07-31 16:35 <udono> someone knows how long a postgres databasename can be? (how many chars are allowed?) | ||
| 2008-07-31 16:43 <udono> its ok, I c its already implemented | ||
| 2008-07-31 16:46 <udono> oh, not ok... I try to find out myself | ||
| 2008-07-31 16:58 <udono> its 64 chars... | ||
| 2008-07-31 16:59 <udono> cedk: is it save not to restrict the size of admin password in tryton? I think of Overflow Attacs... | ||
| 2008-07-31 17:00 <cedk> udono: in the client interface no | ||
| 2008-07-31 17:01 <udono> cedk: so should the admin password be restricted in the client? | ||
| 2008-07-31 17:03 <cedk> udono: it is not a problem of password size but more in the server thread when it reads messages | ||
| 2008-07-31 17:05 <udono> cedk: ok, I set no restriction for the password size | ||
| 2008-07-31 17:07 <cedk> udono: but I don't know what is the best solution to limit message on the server side | ||
| 2008-07-31 17:08 <udono> cedk: the gtk.Entry has a limit of 65536 | ||
| 2008-07-31 17:08 <cedk> udono: yes I know, but crackers will not use the gtk client :-) | ||
| 2008-07-31 17:09 <udono> cedk: :-) | ||
| 2008-07-31 18:20 <cedk> udono: for now the message length with pysocket is limited to 99999999 | ||
| 2008-07-31 18:20 <udono> ok, than its above the maximum of gtk.entry | ||
| 2008-07-31 18:21 <cedk> udono: yes but I don't know if it is good | ||
| 2008-07-31 18:21 <cedk> udono: if you want to upload big files | ||
| 2008-07-31 18:22 <udono> cedk: yes, you are right, this could be a future problem... | ||
| 2008-07-31 18:22 <udono> cedk: btw, I found a way to restrict the input for the databasename to alphanum and _ | ||
| 2008-07-31 18:22 <cedk> but to prevent DOS we need to put a limit | ||
| 2008-07-31 18:23 <cedk> udono: good, you add function on keypress event | ||
| 2008-07-31 18:23 <udono> cedk: yeah | ||
| 2008-07-31 18:23 <udono> :-) | ||
| 2008-07-31 18:24 <cedk> udono: it is always better to prevent error than put an error message | ||
| 2008-07-31 18:24 <udono> cedk: This is my aim | ||
| 2008-07-31 18:24 <udono> cedk: less text | ||
| 2008-07-31 18:25 <udono> cedk: why not a limit of 999.999.999 | ||
| 2008-07-31 18:25 <udono> cedk: so we have 1Gbyte | ||
| 2008-07-31 18:26 <udono> cedk: better, make it a configuration Variable, so everyone can decide on their Hardware | ||
| 2008-07-31 18:27 <cedk> udono: but you must have the same value on each side client and server | ||
| 2008-07-31 18:27 <cedk> udono: but I think about a solution to avoid this | ||
| 2008-07-31 18:27 <udono> cedk: you can set the clients serverside... | ||
| 2008-07-31 18:28 <cedk> udono: this is because the first 8 char in the protocol is the message length | ||
| 2008-07-31 18:29 <cedk> udono: but we can say that the first char until the first space will be the message lenght | ||
| 2008-07-31 18:29 <udono> cedk: so the XMLRPC Protocoll is limited? | ||
| 2008-07-31 18:29 <cedk> udono: and on the server side read the first chars for the len until first space or LIMIT | ||
| 2008-07-31 18:30 <cedk> udono: it is not xmlrpc, it is our own protocol | ||
| 2008-07-31 18:30 <udono> cedk: sounds good, with the webdav we need a bigger load | ||
| 2008-07-31 18:31 <cedk> udono: webdav use the http server from python | ||
| 2008-07-31 18:34 <cedk> udono: I think I will put the limit to 999.999.999 | ||
| 2008-07-31 18:35 <udono> cedk: why not as a config entry? | ||
| 2008-07-31 18:36 <cedk> udono: ok I will try to have this | ||
| 2008-07-31 18:39 -!- markusleist(n=markus@212.14.79.210) has joined #tryton | ||
| 2008-07-31 18:45 <cedk> udono: I can not make it configurable | ||
| 2008-07-31 18:46 <cedk> udono: because the client receive also message and it needs also a limit | ||
| 2008-07-31 18:46 <cedk> udono: I made the limit in a single variable on top of pysocket | ||
| 2008-07-31 18:46 <cedk> udono: so it is easy to change it | ||
| 2008-07-31 18:46 <udono> cedk: ok, it seems the best way | ||
| 2008-07-31 18:47 <cedk> udono: and I reduce a little bit the size of the message send | ||
| 2008-07-31 18:48 <udono> cedk: so we can move big files with webdav and limited ones with tryton client. For me this sounds a good solution. | ||
| 2008-07-31 18:49 <CIA-54> tryton: C?dric Krier <ced@b2ck.com> default * 797:0bb2ff11cf7e trytond/trytond/pysocket.py: Use MAX_LENGHT in pysocket and don't use fixed size for length of message | ||
| 2008-07-31 18:49 <CIA-54> tryton: C?dric Krier <ced@b2ck.com> default * 578:6183a3f97928 tryton/tryton/pysocket.py: Use MAX_LENGHT in pysocket and don't use fixed size for length of message | ||
| 2008-07-31 18:49 <cedk> udono: yes but put in an ERP file bigger than 1Go doesn't seem to me usefull | ||
| 2008-07-31 18:50 <cedk> to test you need to update both client and server | ||
| 2008-07-31 18:50 <udono> cedk: tryton is no ERP its more ;-) | ||
| 2008-07-31 18:51 <cedk> udono: yes but it is not for DVD-rip collection :-) | ||
| 2008-07-31 18:52 <cedk> I fix also one possible bugs in the pysocket implementation | ||
| 2008-07-31 19:02 -!- markusleist(n=markus@212.14.79.210) has joined #tryton | ||
| 2008-07-31 19:03 <udono> cedk: did Postgres make a difference between lowercase and uppercase? | ||
| 2008-07-31 19:04 <udono> cedk: in Databasenames? | ||
| 2008-07-31 19:40 -!- kultviech(n=kultviec@p5B0D3E30.dip0.t-ipconnect.de) has joined #tryton | ||
| 2008-07-31 19:57 <cedk> udono: I think | ||
| 2008-07-31 19:57 <cedk> I create test and Test database | ||
| 2008-07-31 19:58 <udono> cedk: a testdatabase out of single tests? | ||
| 2008-07-31 19:58 <udono> cedk: with the framework? | ||
| 2008-07-31 19:58 <cedk> udono: don't understand | ||
| 2008-07-31 19:59 <udono> cedk: you can create a testdatabase with a bulk of python tests with your testframework... | ||
| 2008-07-31 19:59 <udono> cedk: so it is reproducable... | ||
| 2008-07-31 20:01 <cedk> udono: I don'T where you want to go | ||
| 2008-07-31 20:01 <udono> cedk: than explain me what you like to do :-) | ||
| 2008-07-31 20:02 <cedk> udono: you ask if postgres is case sensitive with database name | ||
| 2008-07-31 20:03 <cedk> udono: so I answer that I can create test and Test database | ||
| 2008-07-31 20:03 <udono> :-) | ||
| 2008-07-31 20:03 <cedk> udono: so postgres is case sensitive | ||
| 2008-07-31 20:04 <udono> cedk: sorry, Ive been completely out of topic... Thanks for research. Momentary my client cant create new databases, because there are problems with the common.refresh_dblist and pygtk... | ||
| 2008-07-31 20:07 <cedk> udono: I just use createdb :-) | ||
| 2008-07-31 20:09 <udono> cedk: Ok, I will try it later with the client... Suddenly I solved the problem with common.refresh_dblist :-) | ||
| 2008-07-31 20:29 <udono> cedk: With the client postgres is case_in_sensitive. I cant create the two databases test and Test | ||
| 2008-07-31 20:30 <udono> cedk: Database already exists... | ||
| 2008-07-31 22:22 -!- udono(n=udono@dynamic-unidsl-85-197-25-158.westend.de) has left #tryton | ||
| 2008-07-31 23:37 -!- betamax_(i=betamax@gateway/tor/x-71e7e42d7514d02d) has joined #tryton |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
