ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 555 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Show attachments

6460 Entries

Goto page Previous 1, 2, 3 ... 554, 555, 556 ... 806, 807, 808 Next

Thu Apr 12 08:57:51 2012

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.

67247

Thu Apr 12 14:38:09 2012

Christopher Lee

chris@chrisandclaire.org

Stefan Ritt wrote:

Christopher Lee wrote:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

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

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.

68039

Fri Jul 3 21:26:32 2015

Using stunnel4 and the 3.1.0 version of elog, I was able to use gmail smtp without the use of iptables.

In my elogd.cfg I chose:

SMTP username = <gmailusername>@gmail.com
SMTP Password = <The hash produced with the perl statement posted by Christopher Lee>
SMTP host = 127.0.0.1

And in /etc/stunnel/stunnel.conf:

[elogssl]
client = yes
accept = 127.0.0.1:25
connect = smtp.gmail.com:465
verify = 2
CApath = /etc/ssl/certs

FInally, run sudo stunnel4.

67952

Fri Jun 5 10:18:38 2015

Re: ELOG Version field in elogs/Forum

> Hi Stefan,
> could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
> number?
> That would be 13 characters.
> 
> Cheers
> Andreas

Ok, done.

/Stefan

67860

Wed Apr 15 04:02:41 2015

Re: ELOG Version 3.1.0 announcement

congrats, any detail changelog? I assume in software packages?

is it save just install and overwrite the old version?

Stefan Ritt wrote:

This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments, it contains a long awaited "autosave" feature.

Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). If your browser crashes or closes for some reason, you will loose your entered text. To avoid that, ELOG starting from version 3.1.0 has an autosave feature. Whenever you enter some text, it is saved in the background as a draft message to the server. If your browser is closed by accident, you always can go back to the logbook, click "New" and ELOG will tell you that there is a draft message and asks you if you want to edit it. When you edit and regularly submit this message, it becomes a "normal" entry and the draft flas is removed. In addition to the background saving, there is now also a "Save" button so you can manually save your text to the draft entry.

I have tested this to some extent, but I might not have seen all browser/OS combinations, so in case there is a problem, please report it here.

Happy Easter,
Stefan

67861

Wed Apr 15 09:01:04 2015

Re: ELOG Version 3.1.0 announcement

The changelog is here: http://midas.psi.ch/elog/download/ChangeLog

It is save to install the new version over the old one.