Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 763 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  1266   Thu Jul 14 13:05:33 2005 Entry Emiliano GabrielliAlberT@SuperAlberT.itBug reportAll Re: short/long_name should point the same user

Emiliano Gabrielli wrote:
.. I mean that if I use:
Restrict edit                 = 1
; preset author and email
Preset Author                 = $short_name
Preset Author Email           = $user_email
Preset on reply Author        = $short_name
Preset on reply Author Email  = $user_email
Subst on reply subject        = Re: $subject

; these attributes cannot be changed
Locked Attributes             = Author, Author Email

and then I change Preset Author to be "$long_name" Elog does not permit the autor to edit an old post of its own ...
It is not able to argue that short and long name are the same person..

Yes I know, you'll ask me why I should change it .. the anwer is.. I don't have to, but (as I could do it logically) I'd like to be able to do..

In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
Smile



a problem related to this issue is that an attribute of userlist type automatically sets the user to be in the long form..

My proposal is to alwais store users in the long form and anly give the possibility to use the short or long form in displaing time..
  1267   Thu Jul 14 15:58:07 2005 Entry Emiliano GabrielliAlberT@SuperAlberT.itCommentAll A new ELOG user wants to register on "127.0.0.1"
A new ELOG user wants to register on "127.0.0.1"


the scenario is:
- elog on localhost
- stunnel on the external interface

I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ?
  1268   Thu Jul 14 17:29:42 2005 Reply Stefan Rittstefan.ritt@psi.chCommentAll Re: A new ELOG user wants to register on "127.0.0.1"

Emiliano Gabrielli wrote:
A new ELOG user wants to register on "127.0.0.1"


the scenario is:
- elog on localhost
- stunnel on the external interface

I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ?


You can specify the interface to liste on with the
"-n <interface>"
parameter of elogd.
  1269   Thu Jul 14 17:34:12 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportAll Re: short/long_name should point the same user

Emiliano Gabrielli wrote:
In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
Smile


Well, that teaches you not to do this error again Wink
  1270   Thu Jul 14 19:11:54 2005 Reply Emiliano GabrielliAlberT@SuperAlberT.itBug reportAll Re: short/long_name should point the same user

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
Smile


Well, that teaches you not to do this error again Wink


uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?

the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works .. Crying
  1271   Thu Jul 14 19:16:06 2005 Reply Emiliano GabrielliAlberT@SuperAlberT.itCommentAll Re: A new ELOG user wants to register on "127.0.0.1"

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
A new ELOG user wants to register on "127.0.0.1"


the scenario is:
- elog on localhost
- stunnel on the external interface

I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ?


You can specify the interface to liste on with the
"-n <interface>"
parameter of elogd.


I know Smile

the following is the configuration I'm telling about... and it raises the problem reported
albert@YYYYYYYYY:~$ ps axu | grep elog
elog     22348  1.0  1.9 23660 20408 ?       Ss   11:32   4:54 /usr/sbin/elogd -f /var/run/elogd.pid -c /etc/elog.conf -d /var/lib/elog -s /usr/share/elog -p 8081 -n 127.0.0.1 -x -D
root     22353  0.0  0.2 45436 2276 ?        Ss   11:32   0:17 /usr/sbin/stunnel -o /var/log/elog/elog_daemon.log -p /etc/ssl/certs/stunnel_XXXXXXX.pem -d XXXXXX.roma2.infn.it:8080 -r 127.0.0.1:8081
  1272   Thu Jul 14 20:24:07 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportAll Re: short/long_name should point the same user

Emiliano Gabrielli wrote:
uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?

the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works .. Crying


The "short name" is the equivalent to the unix login name. Under /etc/passwd, you have a login (short) name and a "full" (long) name. The first may not contain blanks, must be unique, while the second is more like a "real" name. This concept has been adapted in elog. While many people use cryptic or abbreviated login names, it's still nice know the real name, like if you get an email notification from someone. The userlist fills with the long_name because people refer to other people in the logbook usually with the real name (sometimes they even don't know the people's login name). The admin dropdown menu uses the short names because you look at the user database more from an administration point of view. Like if you edit /etc/passwd, you first look at the login name, not the full one. Maybe what one could add is to make the full name in the admin page a dropdown list as well, so the admin can either select the short or the long name. Another item for the wishlist Crying
  1273   Fri Jul 15 15:03:01 2005 Reply Emiliano GabrielliAlberT@SuperAlberT.itBug reportAll Re: short/long_name should point the same user

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?

the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works .. Crying


The "short name" is the equivalent to the unix login name. Under /etc/passwd, you have a login (short) name and a "full" (long) name. The first may not contain blanks, must be unique, while the second is more like a "real" name. This concept has been adapted in elog. While many people use cryptic or abbreviated login names, it's still nice know the real name, like if you get an email notification from someone. The userlist fills with the long_name because people refer to other people in the logbook usually with the real name (sometimes they even don't know the people's login name). The admin dropdown menu uses the short names because you look at the user database more from an administration point of view. Like if you edit /etc/passwd, you first look at the login name, not the full one. Maybe what one could add is to make the full name in the admin page a dropdown list as well, so the admin can either select the short or the long name. Another item for the wishlist Crying


uhmm .. what I am talking about is something simpler ... It seems to me that elog does not use always the "login name" but somethins refers to the "gecos" ... What I'm askinf for is to separe the login name (to which elog has to refer for everything internally) and the long/short_name mechanism that should be a mere display issue ...

May be that it is the same to ask for the introdution of a "user_id" or to treat the login name as the uid, .. the "Author" field should be filled both with the long and the short name (and it is so now!) but, when checking the original author on a Edit action, aelog as to check always the actual logged *short* name against the original Author *short* name .. becoise is only the short name that should have a sense for messages .. the long one is only a nice reminder Smile

Hope my english makes me to be understod now Wink
ELOG V3.1.5-2eba886