Re: From command line: "command Submit not allowed", posted by David Wallis on Wed Oct 21 15:14:13 2020
|
Hi David, thanks for your input!
This logbook has been around for almost 10 years, and has evolved from file-based authentication, to LDAP, and finally to PAM (that can use any
of local password files, LDAP, and Active Directory), and I'm thinking that might be the root of this problem. There are old account entries from the |
Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 16:00:03 2020
|
I'm converting our on-call logbook, with 25 years of history, to elog. Is there a way to override the current date/time for the Date field with the
creation date/time of the original logbook entry? |
|
Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 16:37:07 2020
|
Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date",
upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?
Stefan |
|
Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 17:45:29 2020
|
Hi Andreas,
Thanks for your input! After a little testing, it appears that if I make "Orig Date" the first field, it will fall under the Date field
in the logbook file. I can then do a global delete of Date:, and replace Orig Date: with Date:, leaving it as the first field in the entry. Then I can |
|
Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 22:24:18 2020
|
Hi Andreas,
It was actually easier than that. The time stamps in the old system were in epoch format, so when I created the new record, (my conversion program
was written in Python), I simply formatted that value in the format Stefan pointed out below, and defined the Orig Date field as text. Then I was able |
|
results of security scan, posted by David Stops on Mon Nov 1 12:52:23 2021
|
Recently central IT scanned our elog server and reported the following "vulnerabilities"
42873 (1) - SSL Medium Strength Cipher Suites Supported (SWEET32)
51192 (1) - SSL Certificate Cannot Be Trusted
65821
(1) - SSL RC4 Cipher Suites Supported (Bar Mitzvah)
85582 (1) - Web Application Potentially Vulnerable to Clickjacking
Is |
|
Re: results of security scan, posted by David Stops on Thu Nov 4 13:48:00 2021
|
Thanks, I'll try that and see what happens
David |
Incorrect Display, posted by David Spindler on Sat May 21 15:05:23 2005 
|
I hope this is the correct place for an apparent bug report. The display is incorrect except when displaying a particular entry. I just downloaded 2.6.0-beta
thinking I was getting 2.5.9. Nice surprise. The elcode (bbcode? ) is a great idea, but the display, when showing the main screen of a logbook does not
have the correct fields showing in the correct places. I will attach two screen captures for illustraton. Never mind, I guess not. It is not letting me |