Exploit Browser Tabs to Make Anonymous Entries, posted by Alan Stone on Wed Jul 30 19:54:28 2008
|
One of my shifters just managed to make an anonymous logbook entry even though the Author attribute is required.
It turns out that he had two tabs in his browser opened/logged into the Elog. He logged out in one tab only. Then he
did some other work on the desktop. Then he returned to the browser to make a new logbook entry, finding the tab which |
Re: Exploit Browser Tabs to Make Anonymous Entries, posted by Stefan Ritt on Thu Jul 31 09:25:01 2008
|
Alan Stone wrote:
One of my shifters just managed to make an anonymous logbook entry even though the Author attribute is |
Elog crashing with "segfault" during file upload, posted by Jesse Wodin on Thu Jul 17 01:16:49 2008
|
Hi there, I just compiled and installed elog on a machine running the newest Ubuntu server. Everything went fine - no problems. Running elog on it's
own (no apache). I moved over a bunch of logbooks from an older elog, which seemed to work. Now, elog seems to crash when people are uploading files.
Here is a snip from my syslog, and you can see each time it crashes with "error 4." |
Re: Elog crashing with "segfault" during file upload, posted by Jesse Wodin on Fri Jul 18 08:18:18 2008
|
Jesse Wodin wrote:
Hi there, I just compiled and installed elog on a machine running the newest Ubuntu server. Everything |
Using the command line tool to edit, posted by T. Ribbrock on Thu Aug 7 10:12:25 2008
|
I intend to create a script that updates one of our elog logbooks based on mails it receives. I was hoping to be able to do this using the "elog" command
line tool. Adding a new entry works fine, as does "replying" to an existing entry. The only thing I cannot get to work is editing an existing entry. All
entries ahve several attributes and I intend not to use the "message" itself. I tried the following (on the machine this elogd is running on): |
Re: Using the command line tool to edit, posted by Yoshio Imai on Fri Aug 8 14:27:03 2008
|
[quote=T. Ribbrock][B]NOTE:[/B] I found that this does [i]not[/i] work if LOGBOOK has any spaces in it - I would get error messages where the logbook was
not found.[/quote]
|
Re: Using the command line tool to edit, posted by T. Ribbrock on Fri Aug 8 14:50:56 2008
|
[quote="Yoshio Imai"][quote=T. Ribbrock][B]NOTE:[/B] I found that this does [i]not[/i] work if LOGBOOK has any spaces in it - I would get error messages
where the logbook was not found.[/quote]
|
Re: Using the command line tool to edit, posted by Stefan Ritt on Mon Aug 11 11:02:18 2008
|
T. Ribbrock wrote:
I intend to create a script that updates one of our elog logbooks based on mails it receives. I was hoping |