Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 185 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6445 Entries 
Goto page Previous  1, 2, 3 ... 184, 185, 186 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  69143   Tue Apr 21 09:13:45 2020 Reply Daniel Pfuhldaniel.pfuhl@medizin.uni-leipzig.deRequestLinux | Windows | Mac OSX | All | Other3.1.4Re: CSS for HTML Mails

Hi Stefan,

I pulled the code from the repository but was not able to build it.

Sorry, I'm not a developer. Is there a good documentation you can recommend on how to do this for a Windows installation incl. how to setup a build environment?

No chance to get a more recent Windows version already precompiled? ^^

Regards,

daniel

 

Stefan Ritt wrote:

a04faf9f is pretty old: https://bitbucket.org/ritt/elog/commits/a04faf9fa9ca74657240cdc827bd2d0ae48a9df1

It's from September 2018, where the change with the CSS has been made on Decemb er 2018. You have to pull the current version from the git repository and recompile the program yourself.

/Stefan

Daniel Pfuhl wrote:

Hmm, I'm pretty sure that we are on the latest version already.

We use ELOG V3.1.4-a04faf9f

I downloaded a fresh install binary for Windows and compared the checksums:

SHA256: 0A98485134E0D43959CB6734F977B02DC9FA884D6994CE3BA141664451FDA5E5
SHA256: 0A98485134E0D43959CB6734F977B02DC9FA884D6994CE3BA141664451FDA5E5

same same.

Or do I have to change to config in order to include the CSS in the HTML?

regards,

 

daniel

 

Stefan Ritt wrote:

The CSS has been embedded in the email end of 2018, so just upgrade your server.

https://bitbucket.org/ritt/elog/commits/5165daf35cc1fb066071827719079fe0c9aa5ffb

/Stefan

Daniel Pfuhl wrote:

Hi there,

we extensively use Logbuch as a change documentation platform.

E-Mail notifications for new entries are very important for us.

Since we store sensible data in our logbooks the server is protected by a firewall.

After the firewall was activated the HTML mails are not rendered by the Outlook Mail clients we use - when they are located in an "external" net behind the firewall. I assume that's because of the css stylesheet which is linked in the source code of the HTML mail.

Is there any chance to include the CSS information in the HTML code? Otherwise we would need to make the CSS accessable from anywhere which requires in turn that the path of the CSS file can be customized.

Any idea how to solved this issue?

Best regards,

daniel

 

 

 

 

  69149   Tue May 12 15:47:33 2020 Reply Rich Loringrloring@bnl.govQuestionLinux3.1.4How to prevent file path leaks on a 404 page

Hello,

We used the Elog RPM binary installation method to install Elog. Our security scanners are complaining that Elog discloses the version information when you hit a missing page (404 error).  How can I hide this version info? Is there a snippet of code somewhere that I can comment out?

Any help is appreciated.

-Rich

  69150   Tue May 12 15:53:17 2020 Question Rich Loringrloring@bnl.govQuestionLinux3.1.4How to prevent file path leaks on a 404 page

Hello,

We used the Elog RPM binary installation method to install Elog. Our security scanners are complaining that Elog discloses the version information when you hit a missing page (404 error).  How can I hide this version info? Is there a snippet of code somewhere that I can comment out?

Any help is appreciated.

-Rich

  69167   Mon Jul 6 19:09:48 2020 Entry Janusz Szubajanusz.szuba@xfel.euBug reportLinux3.1.4bug in elog.spec

Hi, 

in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?

best

Janusz

  69168   Mon Jul 6 20:19:21 2020 Reply Laurent Jean-Rigaudlollspam@free.frBug reportLinux3.1.4Re: bug in elog.spec

Hi,

You rights, CFLAGS should not be in specfile to take care of distrib env.

Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.

With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,

rpm -i elog-.....src.rpm

rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec

 

I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.

Bye,

Laurent

 

Janusz Szuba wrote:

Hi, 

in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?

best

Janusz

 

  69169   Tue Jul 7 11:22:45 2020 Reply Janusz Szubajanusz.szuba@xfel.euBug reportLinux3.1.4Re: bug in elog.spec

Thanks for the answer, I will try with your specfile

best

Janusz

Laurent Jean-Rigaud wrote:

Hi,

You rights, CFLAGS should not be in specfile to take care of distrib env.

Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.

With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,

rpm -i elog-.....src.rpm

rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec

 

I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.

Bye,

Laurent

 

Janusz Szuba wrote:

Hi, 

in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?

best

Janusz

 

 

  69180   Thu Jul 30 17:03:12 2020 Question Jose Caballerojcaballero.hep@gmail.comQuestionLinux3.1.4testing the client: unclear it worked

Hello,

I just gave it a quick try to the command line client, to see if I can use it to access our institution service. 


[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"

 

Is that the expected output? I was expecting to see info about the latest message in the server.

Cheers,

Jose

  69182   Fri Jul 31 08:34:35 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4Re: testing the client: unclear it worked

The <hostname> you have to actually replace with your real host name. Same for logbook, username and password. 

On my local test system I get (actual password hidden here with "...")

~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test  test
Message successfully transmitted, ID=5
~$ 

Jose Caballero wrote:

Hello,

I just gave it a quick try to the command line client, to see if I can use it to access our institution service. 


[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"

 

Is that the expected output? I was expecting to see info about the latest message in the server.

Cheers,

Jose

 

Goto page Previous  1, 2, 3 ... 184, 185, 186 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6