ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68375
|
Tue Aug 9 04:23:07 2016 |
| Chris Smyth | chris.smyth@comcast.net | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
Andreas Luedeke wrote: |
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
68377
|
Tue Aug 9 14:01:04 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You need to download the source file package of ELOG and compile it. If you don't know what a Makefile is, then it is likely futile for you to attempt to compile ELOG.
Or in other words: you cannot use SSL.
Chris Smyth wrote: |
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
Andreas Luedeke wrote: |
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
|
68378
|
Tue Aug 9 14:08:20 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Request | Windows | Latest | Re: Sample of actual elog Config with URL in SSL | You've already named your solution: drop the very old ELOG version and download the new one. Obviously it was compiled with USE_SSL and you can use it right away.
Since you probably don't even have the source files of the old version, you'll have no chance to make it work with that. Just use ELOG 3.1.0.
Chris Smyth wrote: |
By the Makefile i belive you are refering to the elogd.cfg? if not what file do I have use?
I have added
port = 443
ssl = 1
Without sucess.
I then tried
port = 443
use_ssl = 1
still no sucess.
I cant find any file that has "#USE_SSL =1" that I can uncomment. I am using an older version of ELOG (ELOG278-2) reading all the documentation I cant seem to figure it out.
I also configured elogd to listen on port 443
Opened a CMD window and entered >elogd -p 443
Says listening on port 443 but still not working.
On the most curent version of ELOG 3.1.0 I just modify the elogd.cfg added ssl = 1 and change the port to 443 and everthing works as advertised. I do the same on this version and I cant get it working. I could really use some help. Thanks for the fast response.
Andreas Luedeke wrote: |
Very easy: uncomment the line USE_SSL=1 in the Makefile and then compile.
You'll need of course a gcc compiler on your Windows system, a makefile environment, SSL libraries, etc.. If you don't have that: ask you local administrator.
Cheers, Andreas
|
how do I compile elogd with USE_SSL=1?
Andreas Luedeke wrote: |
You normally don't need to specify "URL = xxx" at all. It is only needed if you work with a Proxy that changes the normal ELOG URL. And yes, you'll need "Port = 433" and "SSL =1".
And elogd must be compiled with USE_SSL=1, maybe that's your problem?
In addition you should buy a valid SSL certificate. Otherwise every user needs to acknowledge an exception for your invalid SSL certificate.
Cheers, Andreas
Dawang wrote: |
HI Guys,
Can you please give me an idea how will I write in the config. I want my elog will be accessed via internet. Though there's a tutorial / guideline, I need an actual config file for me to easily grasp how the URL = xxx should be write. Do my port should be Port = 433 and SSL=1?
Thanks,
Raymund
|
|
|
|
|
|
68649
|
Fri Jul 21 15:24:33 2017 |
| Devrim Esenturk | devrim.esenturk@gmail.com | Question | Windows | Latest | Conditional attribute activation | I have a stock database running latest elog version on windows. I am reserving some products which not been sent to customer mistakenly and using value "reserved" for it. But I need another attribute for comment reason of reserving but this attribute must be activated when reserved value selected. Is this possible? I didn't see any option for this at admin guide.
Thank you |
68650
|
Mon Jul 24 14:33:51 2017 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | Latest | Re: Conditional attribute activation | Yes, this is possible by using "Conditional Attributes". Have a look at the ELOG syntax help: https://midas.psi.ch/elog/config.html#conditional
To hide attributes on edit, you can use "Show Attributes Edit = ..." for the conditions; and you only list the comment reason for the case where the value of the other attribute has the value "reserved".
If you don't get it to work, then just post your logbook config with some comments on what you want to achieve.
Cheers, Andreas
Devrim Esenturk wrote: |
I have a stock database running latest elog version on windows. I am reserving some products which not been sent to customer mistakenly and using value "reserved" for it. But I need another attribute for comment reason of reserving but this attribute must be activated when reserved value selected. Is this possible? I didn't see any option for this at admin guide.
Thank you
|
|
67692
|
Fri Aug 1 22:46:09 2014 |
| Chuck Brost | brost_chuck@solarturbines.com | Question | Windows | Elog V2.9. | Elog and Certs | 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.. |
67693
|
Sat Aug 2 06:59:22 2014 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | Elog V2.9. | Re: Elog and Certs |
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? |
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! |
|