Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 113 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6444 Entries 
Goto page Previous  1, 2, 3 ... 112, 113, 114 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  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

 

 

 

 

 

 

 

  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

 

 

 

 

 

 

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

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

 

 

 

 

 

  68938   Wed Apr 24 10:29:00 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

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

 

 

 

 

  68937   Wed Apr 24 10:21:58 2019 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

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

 

 

 

  68936   Wed Apr 24 10:15:23 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

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

 

 

  68935   Wed Apr 24 09:43:02 2019 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" list

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

 

  68934   Wed Apr 24 09:15:26 2019 Question Nikolas Patronisnpatronis@uoi.grQuestionLinux3.1.3exclude access to a number of users in one logbook

How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL?

Goto page Previous  1, 2, 3 ... 112, 113, 114 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6