Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 201 of 801  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  68940   Wed Apr 24 11:30:37 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post a minimel elogd.cfg file with which I can reproduce the problem?

Stefan

Heinz Junkes wrote:

Sorry, 

I meant "read only" by using "Restrict edit time" settings. e.g.

Restrict edit time = 24

I understand this to mean that an entry should not be able to be modified after 24 hours.

Heinz

Stefan Ritt wrote:

There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.

Stefan

Heinz Junkes wrote:

Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.

Heinz

Stefan Ritt wrote:

There are two ways:

1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.

2) Use "Login user = <usr list>" to restrict access to certain users in that list.

Stefan

Heinz Junkes wrote:

Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz

Heinz Junkes wrote:

submissions via the elog - program can overwrite entries even if the user has no edit rights

 

 

 

 

 

 

  68941   Wed Apr 24 11:56:24 2019 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

I ask my users where they had the problems and then create a demo for testing.
Thanks Heinz

Stefan Ritt wrote:

So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post a minimel elogd.cfg file with which I can reproduce the problem?

Stefan

Heinz Junkes wrote:

Sorry, 

I meant "read only" by using "Restrict edit time" settings. e.g.

Restrict edit time = 24

I understand this to mean that an entry should not be able to be modified after 24 hours.

Heinz

Stefan Ritt wrote:

There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.

Stefan

Heinz Junkes wrote:

Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.

Heinz

Stefan Ritt wrote:

There are two ways:

1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.

2) Use "Login user = <usr list>" to restrict access to certain users in that list.

Stefan

Heinz Junkes wrote:

Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz

Heinz Junkes wrote:

submissions via the elog - program can overwrite entries even if the user has no edit rights

 

 

 

 

 

 

 

  68944   Fri Apr 26 11:24:21 2019 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

Stefan, will send the info off this forum.

Heinz

Heinz Junkes wrote:

I ask my users where they had the problems and then create a demo for testing.
Thanks Heinz

Stefan Ritt wrote:

So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post a minimel elogd.cfg file with which I can reproduce the problem?

Stefan

Heinz Junkes wrote:

Sorry, 

I meant "read only" by using "Restrict edit time" settings. e.g.

Restrict edit time = 24

I understand this to mean that an entry should not be able to be modified after 24 hours.

Heinz

Stefan Ritt wrote:

There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.

Stefan

Heinz Junkes wrote:

Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.

Heinz

Stefan Ritt wrote:

There are two ways:

1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.

2) Use "Login user = <usr list>" to restrict access to certain users in that list.

Stefan

Heinz Junkes wrote:

Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz

Heinz Junkes wrote:

submissions via the elog - program can overwrite entries even if the user has no edit rights

 

 

 

 

 

 

 

 

  68945   Fri Apr 26 17:22:46 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

Ok, I found the issue. The "Restrict edit time" is only checked when one clicks on "Edit" in the browser. The elog command line tool does not really an edit, but just submits an entry with an (old) ID. I added a check also for that case so now it should work. The commit is in git.

Stefan

Heinz Junkes wrote:

Stefan, will send the info off this forum.

Heinz

Heinz Junkes wrote:

I ask my users where they had the problems and then create a demo for testing.
Thanks Heinz

Stefan Ritt wrote:

So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post a minimel elogd.cfg file with which I can reproduce the problem?

Stefan

Heinz Junkes wrote:

Sorry, 

I meant "read only" by using "Restrict edit time" settings. e.g.

Restrict edit time = 24

I understand this to mean that an entry should not be able to be modified after 24 hours.

Heinz

Stefan Ritt wrote:

There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.

Stefan

Heinz Junkes wrote:

Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have forbidden further editing.

Heinz

Stefan Ritt wrote:

There are two ways:

1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.

2) Use "Login user = <usr list>" to restrict access to certain users in that list.

Stefan

Heinz Junkes wrote:

Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz

Heinz Junkes wrote:

submissions via the elog - program can overwrite entries even if the user has no edit rights

 

 

 

 

 

 

 

 

 

  797   Tue Nov 16 18:07:31 2004 Question Stefan Rittstefan.ritt@psi.ch   Re: elog password access without users
> i
  794   Tue Nov 16 18:07:31 2004 Question Stefan Rittstefan.ritt@psi.ch   Re: elog password access without users
> is there a way to set up a logbook so that a password is required to get
> into it, but no username?

Have a look under "Access control" in the manual. What you need is "Read
Password".
  795   Tue Nov 16 22:06:29 2004 Question damon nettlesnettles@phgrav.phys.lsu.edu   Re: elog password access without users
> > is there a way to set up a logbook so that a password is required to get
> > into it, but no username?
> 
> Have a look under "Access control" in the manual. What you need is "Read
> Password".

thanks. that seems to get me the functionality i needed. is there any way to
get rid of the username line when using the "Read Password" feature? as it is
now, you can either leave it blank or enter anything you want, so long as you
use the correct password it still works. however, to keep users from getting
confused, i think it would be better to only have a box asking you for the
password and not both the password and username.
  796   Tue Nov 16 22:45:24 2004 Reply Stefan Rittstefan.ritt@psi.ch   Re: elog password access without users
> thanks. that seems to get me the functionality i needed. is there any way to
> get rid of the username line when using the "Read Password" feature?

No, this is an HTTP standard. The dialog box is generated by your browser, and I
do not know any way to prevent it.
ELOG V3.1.5-3fb85fa6