| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67696
|
Mon Aug 11 22:21:43 2014 |
 | Chuck Brost | brost_chuck@solarturbines.com | Question | Windows | Elog V2.9. | Re: Elog and Certs |
| Andreas Luedeke wrote: |
|
| Chuck Brost wrote: |
|
Elog V2.9.1-2435 if it matters.
It is time again to install the certs for SSL in Elog, and the standard openssl command line does not seem to produce the files that I need in order to get it working on my system.
I copied the file to my trusty linux server and ran the command "openssl pkcs12 -in cert.p12 -clcerts -out cert.pem " as I did last time, last time I got a nice little .crt and .key file.. this time.. no such luck.. I can get by with the guys just hitting the continue and go past the expired cert notice for a bit.. but if I cannot fix it reasonably soon.. well, it won't be pretty for me.. <grin>
Any ideas that anyone can give will be appreciated.. this is a bit outside my usual duties around here..
|
I'm not an expert in this field, but I think openssl is not meant to create a certificate for you, it is meant to create a certificate request form (CSR) and then you buy the certificate with that form from a vendor. Once you have the certificate then you just need to copy it to the right place for ELOG (or Apache) to use it, you don't need openssl for that.
⇄
English (auto-detected) » English
You can have a look at: http://www.rackspace.com/knowledge_center/article/generate-a-csr-with-openssl
Good luck!
PS: This is of course an openssl question: another forum could may be more helpful?
|
for what it is worth, if anyone else is doing this.. try
openssl pkcs12 -in file.pkx -nodes -out file.pem
I have what I need and all is well! |
|
67245
|
Wed Apr 11 17:43:13 2012 |
 | Christopher Lee | chris@chrisandclaire.org | Question | Linux | 2435 | ELOG and Gmail? | Firstly, as with some of the others recently, I am a complete newb when it comes to linux, Though I refuse to let that stop me and really want to get this working.
Pretty much I have a situation where I have been asked to install ELOG, though I am unable to use port 25 at all and also need to use GMAIL for the SMTP server?
It is also my undertanding from the documentation that ELOG only sends mail via port 25
So, I have setup iptables to forward everything from port 25 and a GMAIL IP address used in ELOG's global config for the SMTP, to a stunnel that redirects everything to GMAIL on port 465.
While getting that right took me almost two days, and that was with tons of help and more than half of it being spoon fed to me (though I have learnt SO SO MUCH from just that).
I am still unable to get ELOG to send emails, even if does now seem to connect
Below is a copy of the log from last night (I have spent most of the day trying to sort it out further, but I get the same error)
So I guess my question is, Is it possible to use GMAIL, with ELOG, based on my current conditions, and does anyone have any idea what I can do to go on from here, as I doubt I am the first one to head down this road?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
10-Apr-2012 21:45:19 [Chris@1.2.3.4] {logbookA} Email from <chris@server.com> to chris@server.com, SMTP host 173.194.67.108:
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 220 mx.google.com ESMTP XXXXXXXX.XX^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA}
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} EHLO SERVER.COM^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-mx.google.com at your service, [152.106.18.2]^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-SIZE 35882577^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-8BITMIME^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-AUTH LOGIN PLAIN XOAUTH^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250 ENHANCEDSTATUSCODES^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} AUTH LOGIN^M
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Username:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} username@gmail.com
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Password:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} MYXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} 501 5.5.2 Cannot Decode response fl2sm792152wib.2
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Right now I am pretty stuck, and any advice would be greatly appreciated on how to move forward.
Thanks in Advance
|
|
67247
|
Thu Apr 12 14:38:09 2012 |
| Christopher Lee | chris@chrisandclaire.org | Question | Linux | 2435 | Re: ELOG and Gmail? |
| Stefan Ritt wrote: |
|
| Christopher Lee wrote: |
|
Firstly, as with some of the others recently, I am a complete newb when it comes to linux, Though I refuse to let that stop me and really want to get this working.
Pretty much I have a situation where I have been asked to install ELOG, though I am unable to use port 25 at all and also need to use GMAIL for the SMTP server?
It is also my undertanding from the documentation that ELOG only sends mail via port 25
So, I have setup iptables to forward everything from port 25 and a GMAIL IP address used in ELOG's global config for the SMTP, to a stunnel that redirects everything to GMAIL on port 465.
While getting that right took me almost two days, and that was with tons of help and more than half of it being spoon fed to me (though I have learnt SO SO MUCH from just that).
I am still unable to get ELOG to send emails, even if does now seem to connect
Below is a copy of the log from last night (I have spent most of the day trying to sort it out further, but I get the same error)
So I guess my question is, Is it possible to use GMAIL, with ELOG, based on my current conditions, and does anyone have any idea what I can do to go on from here, as I doubt I am the first one to head down this road?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
10-Apr-2012 21:45:19 [Chris@1.2.3.4] {logbookA} Email from <chris@server.com> to chris@server.com, SMTP host 173.194.67.108:
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 220 mx.google.com ESMTP XXXXXXXX.XX^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA}
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} EHLO SERVER.COM^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-mx.google.com at your service, [152.106.18.2]^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-SIZE 35882577^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-8BITMIME^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250-AUTH LOGIN PLAIN XOAUTH^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} 250 ENHANCEDSTATUSCODES^M
10-Apr-2012 21:45:20 [Chris@1.2.3.4] {logbookA} AUTH LOGIN^M
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Username:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} username@gmail.com
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} Password:
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} MYXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10-Apr-2012 21:45:21 [Chris@1.2.3.4] {logbookA} 501 5.5.2 Cannot Decode response fl2sm792152wib.2
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Right now I am pretty stuck, and any advice would be greatly appreciated on how to move forward.
Thanks in Advance
|
As far as I know GMAIL requires SSL for its SMTP connection, which ELOG does not (yet) support. But you can set up your own SMTP server easily. Should be easier than your iptables work.
|
It does require SSL, though thats where stunnel came in.(Thanks to Sergio for all the help and getting me that far, as well as with all the iptable help :D) .
I was however finally able to get it working just a few minutes ago using GMAIL as the SMTP.
I was able to telnet into smtp.gmail.com over the stunnel, and when I repeated the process that elog goes through from information that I grabbed with TCPdump, everthing would work, until it got to the password that ELOG sends and that was created using : /usr/local/sbin/elogd -t password -c /usr/local/elog/elogd.cfg. When I tried to decode the password, it also gave me errors.
I encoded the password myself, and when I changed the one in [global] to match the one I created instead, ELOG was able to connect and send mail (What I still dont understand is that when I encode my own username to use on telnet, it fails, but the one I got from the tcpdump from elog works.. so its a mixture of the ELOG encoded username, and my own encoded password).
I dont know if it would help if I type up the rest of what we did to get it working here for anyone else for future reference. It does require iptables and stunnel to be installed. Though its a single entry into iptables, and small addition to stunnel.conf once they are running. |
|
67248
|
Sat Apr 14 11:10:14 2012 |
| Christopher Lee | chris@chrisandclaire.org | Question | Linux | 2435 | Re: ELOG and Gmail? | To get it to work required a working installation of IPTABLES and STUNNEL
First is to add the following details into elogd.cfg
| /usr/local/elog/elogd.cfg wrote: | SMTP username = username@gmail.com
SMTP host = 173.194.67.108
SMTP Password = |
This SMTP IP address is a virtual host from Googles SMTP, Any IP Address could technically be used.
Next is to redirect all traffic to port 25 and the above IP address, to STUNNEL.
| Quote: | | sudo iptables -t nat -A OUTPUT -p tcp -d 173.194.67.16 -dport 25 -j DNAT --to 127.0.0.1:10555 |
You can select any port other than 10555 if required. Next you need to modify the STUNNEL config file and add the following.
| /etc/stunnel/stunnel.conf wrote: | [elogssl]
client = yes
accept = 10555
connect = smtp.gmail.com:465 |
Last was the password. For some reason sudo /usr/local/sbin/elogd -t <password> -c /usr/local/elog/elogd.cfg created a password that was unreadable by google.
To recreate your own run the following command:
| Quote: | | perl -MMIME::Base64 -e 'print encode_base64("\000not.my.re\@l.password")' |
Replace "\000not.my.re\@l.password" with the GMAIL password, remember to escape with a \ any @ signs you might have.
Copy the output and add that into the elogd.cfg file in the SMTP Password syntax.
kill the STUNNEL PID if it is running and restart it to to load the new details, also remember to save your IPTABLES for next reboot
And that should be it, so now ELOG uses a port other than 25, and also redirects via SSL to a SMTP like GMAIL. |
|
67250
|
Mon Apr 16 11:10:07 2012 |
 | Christopher Lee | chris@chrisandclaire.org | Bug report | Linux | 2435 | Forgot Password | We seem to have a problem with retrieving user passwords using the forgot password system
This only happens when trying to use the password recovery from the first screen that forces people to log in with the following syntax:
Protect selection page = 1
Password file = XXXXX
On the first page of our elog which can be found at
http://physics.uj.ac.za/elog/
Now currently there is one page that is viewable by guests, so going to this direct link, bypasses the login at the main page
If you try login from this page, and then use the forgot password link, the email that gets sent through will then work.
The first email that gets sent through using the main login page has the following link:
https://physics.uj.ac.za/elog/?redir=%3Fcmd%3DChange+password%26oldpwd%3DYJAATGHSIRRSBLLP&uname=Tester&upassword=YJAATGHSIRRSBLLP
When clicking on the above link normally, it takes you to a NULL user
The email link that gets sent from the guest page, that works, looks like this:
https://physics.uj.ac.za/elog/General/?redir=%3Fcmd%3DChange+password%26oldpwd%3DSACWEHJWWHKEXLMO&uname=Tester&upassword=SACWEHJWWHKEXLMO
Attached is a copy of the cfg file. The last few logbooks are all actually just copies of TEMPLATE A, so I have removed all their details to make the file easier to read for now
|
| Attachment 1: elogd.cfg
|
[global]
; GENERAL SETTINGS
port = 8080
URL = https://physics.uj.ac.za/elog/
Login expiration = 48
;sets login to first page
Protect selection page = 1
Password file = XXXXXX
Self register = 4
;SMTP email settings
SMTP username = physics.uj.elog@gmail.com
SMTP Password = XXXXXX
SMTP host = 173.194.67.108
;error logging details:
Logging level = 3
Logfile = elog.log
; Admins
Admin user = Chris, sash, connell
;Groups
Show top groups = 1
Group Open Logbooks = General, General Physics
Group Personal = Simon Connell, Martin Cook, Marius Tchonang, Doomnull Unwuchola, Admin Users, Claire Lee
Top Group Personal Logbooks = Open Logbooks, Personal
Top Group Instruments = Lang Topography, On-line LAUE, Plane Wave Topography, Diamond Processing
Top Group Collaboration = ATLAS - H --> Z'Z', ATLAS - W --> l nu tau nu, ATLAS - Astro-Particle, ATLAS - MuonDB, JLAB - Omega
;Top Group Templates = Template A, Template B
[global Personal Logbooks]
Admin user = Chris, sash, connell
[global Instruments]
Admin user = Chris, sash, connell
[global Collaboration]
Admin user = Chris, sash, connell
[Template A]
; use user level password access
Password file = XXXXXX
Admin user = Chris, sash, connell
login user = Chris, sash, connell
; look and feel
Date format = %B %d, %Y
Title image URL = https://physics.uj.ac.za/elog/
; attributes
Attributes = Author, Author Email, Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other
Extendable attributes = Category
Required Attributes = Category, Subject
Thread display = $Subject, entered by $author on $Entry date
Quick filter = Date, Category
; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email
; these attributes cannot be changed
Locked Attributes = Author, Author Email
; only author can change its own entry
Restrict edit = 1
; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email
; No Email notification
Suppress Email to users = 1
[Template B]
; use user level password access
Password file = XXXXXX
; Admin user = Chris, sash, connell
; login user = Chris, sash, connell
Theme = default
Display mode = threaded
Entries per page = 100
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1
Summary lines = 1
Display Email recipients = 1
#Suppress Email to users = 0
#Email All =
#Use Email From = physics.uj.elog@physics.uj.ac.za
#Use Email Subject = [ELOG][$logbook][$date][$subject]
#Preset Email = $user_email
#Email Encoding = 1
#Email Format = 15
Title image URL = https://physics.uj.ac.za/elog/
; look and feel
;Date format = %B %d, %
Title image URL = https://physics.uj.ac.za/elog/
Comment = Testing Worklist
List Display = Edit, ID, Job Description, Location, Status, Date Entered, Date Closed
Thread Display = $Location, $Job Description, $Date Entered, $Date Closed,
#Start Page = ?Status=2-Open&mode=threaded&sort=Location
Start Page = ?wpwd=1&mode=threaded&Status=2-Open&sort=Location
Date Format = %A, %B %d, %Y
Time Format = %A, %B %d, %Y, %H:%M
Message Height = 6
Attributes = Location, Status, Date Entered, Date Closed, Job Description, Author, Email
Type To Do = Time
Type Date Entered = time
Type Date Closed = time
Options Status = 1-To Do{1}, 2-Open{2}, 3-Closed{3}, 4-Suspended{4}
{1} Preset To Do = $Date
{2} Preset Date Entered = $Date
{3} Preset Date Closed = $Date
{4} Preset Date Closed = $Date
Options Location = Sequim, Port Angeles, All, Secaira
Extendable options = Location,
Page Title = Simon's Worklist - $subject
Option Author = Filled In Automatically
Subst Author = $long_name
Menu Commands = Back, New, Edit, Delete, Reply, Find, Select, Copy to, Move to,
Reverse sort = 1
Quick Filter = Location, Status
Subst on reply subject = Re: $Job Description
Thread display = $subject, posted by $author on $Entry time
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author
Quick filter = Date, Category, Status
[General]
[General Physics]
[Simon Connell]
[Martin Cook]
[Marius Tchonang]
[Doomnull Unwuchola]
[Admin Users]
[Claire Lee]
[Lang Topography]
[On-line LAUE]
[Plane Wave Topography]
[Diamond Processing]
[ATLAS - H --> Z'Z']
[ATLAS - W --> l nu tau nu]
[ATLAS - Astro-Particle]
[ATLAS - MuonDB]
[JLAB - Omega]
|
|
67256
|
Tue May 1 09:20:00 2012 |
 | Christopher Lee | chris@chrisandclaire.org | Bug report | Linux | 2435 | Re: Forgot Password |
| Stefan Ritt wrote: |
|
| Christopher Lee wrote: |
|
We seem to have a problem with retrieving user passwords using the forgot password system
|
Thanks for reporting that bug. With the help of your config file I finally could reproduce and fix it. The fix is contained in SVN revision 2462.
|
Thanks mate.. Glad to know it wasn't just me going insane? I'll keep an eye out for the new file |
|
437
|
Sun Oct 12 08:37:00 2003 |
| Christopher Jones | cjjones@zombieworld.com | Bug report | Windows | 2.3.9 | Elogd.exe Crashes When There are too Many Replies to Replies... | Hi,
We have been using Elog successfully as a shiftlog book for over a month
now, but I recently ran into an annoying bug, I think.
We had a thread that was created and was being replied to over several
days. We first replied to the original thread and then each subsequent
reply was a reply of the previous reply. When the thread reached above 13
of these, the elogd.exe would crash everytime a user attempted to select
the logbook that contained the enormous thread.
I found the only workaround was to manually delete the offending entry
from the log file and to instruct my users to not reply to replies unless
absolutely necessary. I have been able to replicate this error across the
rest of my logbooks as well. If there is any more information you may
need, please feel free to contact me.
Thanks,
Chris Jones |
|
456
|
Fri Nov 21 07:59:50 2003 |
| Christopher Jones | cjjones@zombieworld.com | Bug report | Windows | 2.3.9 | Re: Elogd.exe Crashes When There are too Many Replies to Replies... | > I found a stack overflow if there are too many replies. This has been fixed in
> the current CVS verson of elogd.c and will be incorporated into the next release.
Many thanks for your quick reply to this issue. I have also noticed that when
moving a log entry that contains as few as 4 replies to replies with the "Move to"
command that the elog server will crash. I ran into this issue many times when I
created a new logbook and was trying to move some of the longer threads into it.
Please let me know if you would like me to send some sample entries from our
logbook that illustrate this.
Thanks,
Chris |
|