Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 86 of 807  Not logged in ELOG logo
    icon5.gif   Re: User Profile - Access to logbook group, posted by Tomas Rudolf on Fri May 2 18:10:36 2003 
Robert, this is exactly what we managed to do as well. And it works fine. 
The only issue is that the users from one group can "SEE" the book names 
available to other groups. 

The solution Stephane suggested seems like the only possible right now.

Anyways, thank you for your answers, Robert & Stephane !

Tomas


> I have managed to get this to work (so far).
> 
> What I do is use a separate password file and directory for each log.
> 
> I haven't tested it with with the current version but it worked fine before
> that. My testing consisted of creating a user in the main password file and
> see if he could get to anything I didn't want him to. This may not be 
enough
> for something that requires a high level of security. 
> 
> When I create a new user I move that line to the appropriate password file 
if
> it isn't already there.
> 
> You will get an invalid user message and a prompt if you try access a log 
that
> doesn't have your user name in the password file. 
> 
> I only have six people using it so this isn't much trouble.
> 
> I would like to see groups implemented to make this more manageable.
> 
> > Hi,
> > 
> > I was wondering if anyone had a solution for my problem.
> > We are trying to run several books on one server. The books are grouped 
> > such as follows :
> > 
> > Group Users1 = Book1, Book2, Book3
> > Group Users2 = Book4, Book5, Book6
> > Group Users3 = Book7, Book8, Book9
> > 
> > We would like to give access to selected users to only their Group. So 
that 
> > for instance Users1 cannot access the books of group Users3. I was 
> > wondering if there is any notion of "User profile" or security per 
logbook 
> > Group implemented?
> > 
> > What we do for now is that we have 3 different PASSELOG files and for 
each 
> > Book we need to specify which PASSELOG should be used for 
authentication. 
> > This works fine except that we prefer that users do not see the other 
> > logbooks listed in the main menu nor the other "inaccessible" logbook 
tabs 
> > in the logbook view. Is there a way to hide these for them (but only for 
> > them)?
> > 
> > Tomas
icon5.gif   Simulation of a submit, posted by Tomas Rudolf on Fri May 2 18:50:48 2003 
I have another tricky question.

Is there a way to simulate an ELOG SUBMIT?

We developed a module which automatically inserts new submits from ELOG 
into an SQL database. The module is in testing phase but we can already 
tell it does the job as it should. 

This allows us to copy ELOG entries into SQL database. But in some cases, 
we would like to transmit data in the other direction too - from SQL into 
ELOG (synchronization).

Now, one way to do that is to create .txt files with entries directly, but 
we find it too risky (file-locking mentioned in a question earlier today 
can be one of the issues). So we're contemplating a possibility that ELOG 
does these inserts for us by processing some simulated SUBMITS.

We're assuming that ON SUBMIT, you generate a POST (or a GET ?) over http 
which is then processed by the ELOGD server. This should be possible to 
simulate in our synchronization application. Are we correct in our 
assumptions?

Tomas
    icon2.gif   Re: Simulation of a submit, posted by Stefan Ritt on Fri May 2 20:10:48 2003 
> Is there a way to simulate an ELOG SUBMIT?

Have a look at the elog utility which comes in the package. It does exactly 
this. It "simulates" a browser and does a submit directly to elogd. So you 
can either redo the elog code somewhere, or call elog with the proper 
command line parameters to insert logbook entries.
    icon2.gif   Re: Simulation of a submit, posted by Tomas Rudolf on Sat May 3 11:00:34 2003 
> > Is there a way to simulate an ELOG SUBMIT?
> 
> Have a look at the elog utility which comes in the package. It does exactly 
> this. It "simulates" a browser and does a submit directly to elogd. So you 
> can either redo the elog code somewhere, or call elog with the proper 
> command line parameters to insert logbook entries.

Thank you, Stefan!
icon7.gif   "Number Attachments =" not being read after upgrade, posted by Kevin Ellwood on Wed May 7 16:54:26 2003 
Hello

I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
Attachments =" is not being read.  Looking at the changelog, I found that
"Number Attachments" has been removed in favor of "enable attachments".  I
tried looking in the documentation but I can't find a discription of the way
 in which multiple attachments are handled.  Can someone give me a pointer?

Thanks
Kevin
    icon2.gif   Re: , posted by Stefan Ritt on Wed May 7 16:58:34 2003 
> I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
> Attachments =" is not being read.  Looking at the changelog, I found that
> "Number Attachments" has been removed in favor of "enable attachments".  I
> tried looking in the documentation but I can't find a discription of the way
>  in which multiple attachments are handled.  Can someone give me a pointer?

Just upload one attachment at a time by hitting the "Upload" button, your 
message text stays there. Once you are finished, hit "Submit". Sorry, I 
thought this would be obvious, since most providers use this for their mail 
web interface.
    icon2.gif   Re: , posted by Kevin Ellwood on Wed May 7 17:27:51 2003 
> > I have upgraded elog from version 2.2.4 to 2.3.6 and then entry "Number
> > Attachments =" is not being read.  Looking at the changelog, I found that
> > "Number Attachments" has been removed in favor of "enable attachments".  I
> > tried looking in the documentation but I can't find a discription of the way
> >  in which multiple attachments are handled.  Can someone give me a pointer?
> 
> Just upload one attachment at a time by hitting the "Upload" button, your 
> message text stays there. Once you are finished, hit "Submit". Sorry, I 
> thought this would be obvious, since most providers use this for their mail 
> web interface.

No need to say sorry.  It is probably obvious to pretty much everyone.  -- It
the story of my life.

Thanks
Kevin
icon5.gif   Use Email From = $user_email, posted by Etienne Van Caillie on Mon May 12 11:20:17 2003 
if you put 

Use Email From = $user_email

we receive in the adress 'my email adress'

how to avoid  the maito: prefix ?
it gives problems when you vwant to reply from outlook

it's ok in elog to send mail from IExplorer
ELOG V3.1.5-3fb85fa6