Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 95 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6444 Entries 
Goto page Previous  1, 2, 3 ... 94, 95, 96 ... 804, 805, 806   Next  
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  69084   Wed Jan 22 19:35:36 2020 Question Ehab Fanousefanous@lh.caRequestWindows3.1.4HTML editor tools grayed out

After we upgarde to eLog 3.1.4 ... The HTML editor tools are grayed out and you can't paste any images in the body of the log like I did below.. Any help will be much appreciated..

  69083   Wed Jan 22 19:30:41 2020 Reply Stefan Rittstefan.ritt@psi.chRequestLinux | Windows | Mac OSX | All | Other3.1.4Re: CSS for HTML Mails

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

 

 

 

  69082   Wed Jan 22 17:32:39 2020 Reply Daniel Pfuhldaniel.pfuhl@medizin.uni-leipzig.deRequestLinux | Windows | Mac OSX | All | Other3.1.4Re: CSS for HTML Mails

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

 

 

  69081   Wed Jan 22 16:35:47 2020 Reply Stefan Rittstefan.ritt@psi.chRequestLinux | Windows | Mac OSX | All | Other3.1.4Re: CSS for HTML Mails

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

 

  69080   Wed Jan 22 16:10:51 2020 Question Daniel Pfuhldaniel.pfuhl@medizin.uni-leipzig.deRequestLinux | Windows | Mac OSX | All | Other3.1.4CSS for HTML Mails

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

  69079   Mon Jan 20 13:46:56 2020 Question matthieu hellermatthieu.heller@unige.chQuestionLinux3.1.4Different behaviours to identical configuration of logbooks for email notification

Dear,

I need to setup automatic email notification using direct send through a office365 smtp server.
This part worked without any issue after setting the right MX record as SMTP host.
As I am working on the configuration file while it is already use, I created a copy of the [GENERAL] logbook to make my tests called [GENERAL COPY] (see attachement and below for the config file).

Surprisingly I manage to send the email without errors using [GENERAL COPY] but not in [GENERAL]. In that case, I get this error message:
Error sending Email via <i>"cta####-####.mail.protection.outlook.com"</i>: 4.5.3 Recipients belong to multiple tenants [AM5EUR02FT024.eop-EUR02.prod.protection.outlook.com]

In that case, I was actually not sending the mail to a mailing list but to myself, a registered user.

Do you see any reason why two identical logbooks (except for the name) would behave differently ?

Best,

elogd.cfg:

[global]
port = 8090
SSL = 0
Self register = 0
Welcome Title = <html><font size=5>Welcome to the LST1 Elog server</font></html>
Main Tab = Main Logbooks page
URL = #######
SMTP host = cta####-####.mail.protection.outlook.com
SMTP port = 25
Use Email From = mailing-list@cta-####.org
Display Email recipients = 0
Email message body      = 1

[GENERAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd

[GENERAL COPY]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd

Attachment 1: elogd.cfg 
[global]
port = 8090
SSL = 0
Self register = 0
Welcome Title = <html><font size=5>Welcome to the LST1 Elog server</font></html>
Main Tab = Main Logbooks page
URL = #######
SMTP host = cta####-####.mail.protection.outlook.com
SMTP port = 25
Use Email From = mailing-list@cta-####.org
Display Email recipients = 0
Email message body      = 1

[GENERAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd

[GENERAL COPY]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Subject, Status
Options Type = Announcements, Shift Summary, Webserver, Plans, Safety, Operations, Interventions, Measurements, Structure, Issue
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Use Email Subject = $Type, $Subject
Email Type Webserver = mailing-list@cta-####.org
Email Type "Shift Summary" = mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd


[CAMERA]
Theme = default
Comment = LST1 Camera ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = ECC, TIB, CACO, EVB, UCTS, test, Fibers, Camera, ClusCo, DATA, CACO/ClusCO, Calib box, Camera Server, Monitoring, Backplane, Observation, Daily calibration, Dragon, Operation, Trigger Mezzanine, PDB, CDTS, Switches, Cooling
Options Category = General, Hardware, Software, Network, Other, Weather conditions
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = camera
Password file = camera.pwd

[AMC]
Theme = default
Comment = LST1 AMC ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, Issues, pointing calibration
Options Category = General, Hardware, Software, Network, Other
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = amc
Password file = amc.pwd

[ENERGY]
Theme = default
Comment = LST1 Energy ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, Issues
Options Category = General, Hardware, Software, Network, Other
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = energy
Password file = energy.pwd

[DRIVE]
Theme = default
Comment = LST1 Drive ELOG
Attributes = Author, Type, Category, Subject, Status
Options Type = Software Installation, Problem Fixed, Hardware, PLC Software and Configuration, Telescope Operations, Applications, Other, PLC + Control Software debugging, Tracking Debugging
Options Category = General, Hardware, Software, Other, Other_Debug, Issues
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Extendable Options = Type, Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Status
Admin user = drive

[Startup checklist]
Comment = Shift startup checklist
Attributes = Author, D, M, Y, suic1, suic2, suic3, suic4, suic5, suwa1, suwc1, suwc2, suwc3, supa1, supc1, supc2, supc3, supc4, supc5, supc6, supc7, supc8, supc9, supc10
Quick filter = Author
Enable attachments = 0
Show text = 0
Custom new form = /usr/local/elog/html/startup_list.html
Custom edit form = /usr/local/elog/html/startup_list.html
Custom display form = /usr/local/elog/html/startup_list.html
List after submit = 1
Admin user = camera
Password file = camera.pwd

[Shutdown checklist]
Comment = Shift shutdown checklist
Attributes = Author, D, M, Y, sdsa1, sdtc1, sdtc2, sdtc3, sdtc4, sdtc5, sdtc6, sdtc7, sdtc8, sdtc9, sdtc10, sdtc11, sdtc12, sdtc13, sdtc14, sdfa1, sdfa2, sdfa3, sdfa4
Quick filter = Author
Enable attachments = 0
Show text = 0
Custom new form = /usr/local/elog/html/shutdown_list.html
Custom edit form = /usr/local/elog/html/shutdown_list.html
Custom display form = /usr/local/elog/html/shutdown_list.html
List after submit = 1
Admin user = camera
Password file = camera.pwd

[GENERAL ELOG PROPOSAL]
Theme = default
Comment = LST1 General ELOG
Attributes = Author, Type, Category, System, Subsystem, Subject, Status
Options Type = Shift Summary, Report, Issue, Request, Announcements, Plans
Options Category = General, Observation, Safety, Maintenance, Intervention, Hardware, Software, Network, Other
Options System  = LST1{1}, Structure{2}, Camera{3}, Drive{4}, AMC{5}, IT{6}, Energy{7}
{1} MOptions Subsystem = Shift, Maintenance, Test
{2} MOptions Subsystem = Lower, Dish
{3} MOptions Subsystem = ECC, TIB, CACO, EVB, UCTS, Fibers, ClusCo, DATA, CACO/ClusCO, Calib box, Camera Server, Monitoring, Backplane, Observation, Daily calibration, Dragon, Operation, Trigger Mezzanine, PDB, CDTS, Switches, Cooling
{4} MOptions Subsystem = PLC, Telescope Operations, Applications, Control Software, Tracking
{5} MOptions Subsystem = CCD, AMC box, Pointing calibration
{6} MOptions Subsystem = Humidifier, Cooling
{7} MOptions Subsystem = UPS, Flywheel
Options Status = Fixed, Under Process, Not Fixed
Cell Style Status Fixed  = background-color:green
Cell Style Status Not Fixed  = background-color:red
Cell Style Status Under Process  = background-color:yellow
Required Attributes = Author, Type, Category, System
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type, Category, System
Use Email Subject = $Type, $Subject
Email Type "Shift Summary" = mailing-list@cta-####.org
Email System Camera =  mailing-list@cta-####.org
Admin user = camera
Password file = camera.pwd
  69078   Thu Dec 19 17:46:33 2019 Reply Jan Christoph Terasaterasa@physik.uni-kiel.deQuestionLinuxV3.1.4-ba84827Re: PAM authentication question

Hi David,

sorry for the delay, I currently am very busy with other important work-related business, I hope I can find some time to look into this during christmas holiday season.

 

Have nice holidays,

Christoph

David Wallis wrote:

Hi Christoph,

Thanks for looking into this, if you can enable PAM + File, our users would be very happy!

The pam.d issue is probably related to CentOS/Red Hat, since our PAM expert warned me that it might be necessary.

Jan Christoph Terasa wrote:
David Wallis wrote:

I'm testing the PAM authentication feature, and have a couple questions, a suggestion, and a comment.

First the comment... it was pretty easy to get working, and is exactly what we need here, so thanks! Our PAM stack here is designed to allow logins with Active Directory, LDAP, or local accounts, so the PAM option preserves all of that.

The suggestion: In order to make it work, I had to add a symbolic link in /etc/pam.d:
    elogd -> system-auth
That might be considered for addition to the documentation (this was on Red Hat Enterprise Linux 7.7)

The questions:

  1. The docs indicate that "Self register" must be set to >= 1, but in the code (elogd.c, line 26453), if the PAM module is enabled, Self register is overriden to 0. The result is that no "register as new user" link is displayed on the login screen. Is that the intent?
  2. Related... can PAM and File authentication both be enabled? We have some logbooks that are used by both internal people (with an A/D account) and outside collaborators that get local elog accounts. This works with LDAP + File, can it work with PAM?

Thanks in advance!

 

David, thank you for reporting on your findings regarding the PAM feature. I will look into the points you mentioned:

0. On my machines (Debian testing and stable) I did not have to add anything to /etc/pam.d, but apparently Debian just uses implicit defaults then, and REHL might insist on using excplicit settings. Adding a hint in the documentation is certainly useful, thank your for the suggestion. Maybe elog should provide a pam.d config file (which can be installed/adapted by package maintainers for various OSes).

1.+2. If I remember correctly, I intentionally disabled registration when using the PAM backend, because users will register using their passwd/LDAP/NIS users, and new users can only be regustered using the appropriate tools for the authentication mechanism used. This might not be correctly reflected in the docs, I will check that. In the light of question 2., I can also re-investigate that policy, so that logins will check against both the elog user database and PAM. Self-registering can then be enabled again, and new registrees will go to the elog database. I will try to bringthe code in line with how LDAP works.

 

regards,

Christoph

 

 

  69077   Thu Dec 19 16:40:10 2019 Reply Devin Bougiedab66@cornell.eduBug reportLinux | Windows | Mac OSX | All | Other3.1.4Re: text wrapping broken in firefox
As an example, I created this same entry in the demo logbook using Safari.  As you can see there, the message is wrapped at the width that I set the text entry box.

https://elog.psi.ch/elogs/Linux+Demo/9

> When creating new logbook entries, recent versions of firefox somehow ignore the message width setting.
> 
> For example, configure a logbook with:
> Message Width = 76
> Message Height = 20
> 
> Then, create a new plain text entry that contains very long lines.  The text entry box is the correct size, but once you hit submit and view the full display of the message, it is not wrapped properly.  The summary display is wrapped properly, but not the full display.
> 
> We've only found this to be a problem with recent versions of firefox.  Chromium, Safari, and old versions of firefox behave properly.
Goto page Previous  1, 2, 3 ... 94, 95, 96 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6