ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67019
|
Mon Feb 21 09:05:05 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | latest | Re: Windows 7 and entry storage |
Greg Damhorst wrote: |
I have been playing with Elog on windows 7. I want to set up an elog that can be accessed from our local network, and I discovered that can be done by running the server on windows and entering the host machine's computer-name:8080 in a browser on any machine on the network.
I had the server registered as a windows service, but oddly, when I re-booted the server didn't seem to be running (problem #1).
I then ran into some other problems (currently trivial) but I eventually got around to uninstalling and reinstalling Elog. I deleted all the existing logbooks and data files when I uninstalled, and even deleted everything in the folder I had used as a backup to the Elog directory. So, after reinstalling, I should be getting only the demo logbook and the original demo entry, right?
BUT I'm actually getting the three logbooks that I had created before I uninstalled (problem #2). Even though the entire Elog directory was deleted when I uninstalled... including config file and logbook directory. I can go into "Program Files" now and see that the config file present is the default/demo config file (from the most recent install)... yet when I launch elog in a browser, I am seeing those three logbooks from before, even though they should be gone from my hard drive.
Elog must be storing data somewhere else... where?
(p.s. I've also tried clearing my cache and deleting cookies in the browser)
If it's relevant, when I'm not on the local PC hosting the server, I am accessing it through a university network, and I've found that I can enter computer-name:8080 from ANY machine on the University's nertwork to access elog.
|
Problem #1: Check if the service is on automatic start. Go to "My Computer/Manage/Services and Applications/Services" and search for the elogd entry. On the "Startup Type" column you should see "Automatic". If not, change it by double clicking on it. You might have to be administrator to do this.
Problem #2: Elog stores information ONLY in the directory you install it to. There is only one elogd.cfg file, and the logbook subdirectory below that. So I have no idea where your problem comes from. I would say you did not delete some of the files, but I'm sure you double checked that. |
67304
|
Sun Jul 29 00:59:51 2012 |
| Phil Rubin | prubin@gmu.edu | Question | Linux | latest | ssh tunneling with elog running under Apache | In a configuration with elog running (8080) under Apache (80) [as explained in admin guide], what is the syntax for tunnelling in with ssh, of both the ssh command and the browser locator? |
67305
|
Sun Jul 29 15:43:20 2012 |
| Phil Rubin | prubin@gmu.edu | Question | Linux | latest | Re: ssh tunneling with elog running under Apache |
Phil Rubin wrote: |
In a configuration with elog running (8080) under Apache (80) [as explained in admin guide], what is the syntax for tunnelling in with ssh, of both the ssh command and the browser locator?
|
Maybe some more information will help with the question. Here's the results of my playing around with URL = /host.domain/subdir in elog.cfg. Commented out, I can access locally with http://localhost:8080 and tunnelled (1234:host.domain:8080) with http://localhost:1234, with and without Apache (i.e., Apache is bypassed?). URL = /host.domain/elog in elog.cfg works locally with browser locator localhost:8080 (of course), localhost/elog, and host.domain/elog, but the tunnel directly to 8080 no longer works, nor does http://localhost:4321/elog (even though this ends up showing the same URL on the remote browser as on the local browser) (4321:host.domain:80). http://localhost:4321 brings up the Apache window. Every other URL assignment I tried failed both locally and remotely, so, I assume the ssh tunnel directive is wrong, or the browser locator, or maybe still URL = . Anyway, my question is, what am I doing wrong? |
67319
|
Tue Aug 28 22:48:47 2012 |
| Szu-Ching Peckner | speckner@nd.edu | Question | Linux | latest | show permitted individual logbooks on selection page | How do I make selection page show only list of logbooks that logged on user has access to?
Right now, say I have 4 logbooks, and I have access to 2 of them. I turned on Protect Selection page = 1. So when I go to home page, I need to logon first, then I am given selection page. I am given list of 4 logbooks, I can only click into 2, which is expected.
Instead of given list of 4 logbooks, I would like to know if there is a way to make selection page only contains 2 logbooks which I have access to?
|
67320
|
Tue Aug 28 23:02:07 2012 |
| Szu-Ching Peckner | speckner@nd.edu | Question | Linux | latest | secure way to allow users create logbook | I don't think there is a good secure way so far, but would like to have your opinion.
If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves? |
67323
|
Wed Aug 29 10:46:49 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | latest | Re: secure way to allow users create logbook |
Szu-Ching Peckner wrote: |
I don't think there is a good secure way so far, but would like to have your opinion.
If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?
|
Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.
- Stefan |
67324
|
Wed Aug 29 14:35:45 2012 |
| Szu-Ching Peckner | speckner@nd.edu | Question | Linux | latest | Re: secure way to allow users create logbook |
Stefan Ritt wrote: |
Szu-Ching Peckner wrote: |
I don't think there is a good secure way so far, but would like to have your opinion.
If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?
|
Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.
- Stefan
|
Thanks, that is good option. |
67326
|
Wed Aug 29 18:16:37 2012 |
| Szu-Ching Peckner | speckner@nd.edu | Question | Linux | latest | Re: secure way to allow users create logbook |
Stefan Ritt wrote: |
Szu-Ching Peckner wrote: |
I don't think there is a good secure way so far, but would like to have your opinion.
If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?
|
Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.
- Stefan
|
Is there a way to set user permission based on certain attribute? can Allow command = <user list> based on attribute?
for example, say type home, user1 can read, user2 can write, user3 can not access type home, but can access type work.
In short, is access control available when I use type to get functionality of separate logbooks? If so, how is this access control done?
|
|