Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 180 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 ... 179, 180, 181 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subject
  68381   Thu Aug 11 09:18:27 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindows3.1.1Re: Quick Filter not searching on Enter

I've checked for this forum logbook, and pressing "enter" while having focus in the quickfilter text field does initiate the search. Does it work for you with this logbook?

Alan Grant wrote:

With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching?

 

  68380   Wed Aug 10 16:46:09 2016 Question Alan Grantagrant@winnipeg.caQuestionWindows3.1.1Quick Filter not searching on Enter

With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching?

  Draft   Wed Aug 10 15:40:49 2016  Alan Grantagrant@winnipeg.caQuestionWindows3.1.1Quick Filter not searching

With all of our instances of Elog where we have Quick Filters enabled, any filter that we input characters into does not search the server when we press enter (there is no "Search" button). Interestingly, it will only search when we click anywhere on a blank area of the Elog interface. Is that the intended procedure for searching?

  68378   Tue Aug 9 14:08:20 2016 Reply Andreas Luedekeandreas.luedeke@psi.chRequestWindowsLatestRe: 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

 

 

 

 

 

  68377   Tue Aug 9 14:01:04 2016 Reply Andreas Luedekeandreas.luedeke@psi.chRequestWindowsLatestRe: 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

 

 

 

 

 

  68375   Tue Aug 9 04:23:07 2016 Reply Chris Smythchris.smyth@comcast.netRequestWindowsLatestRe: 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

 

 

 

 

  68374   Thu Aug 4 21:53:37 2016 Reply Andreas Luedekeandreas.luedeke@psi.chRequestWindowsLatestRe: Sample of actual elog Config with URL in SSL

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

 

 

 

  68373   Thu Aug 4 16:40:14 2016 Reply Chris Smythchris.smyth@comcast.netRequestWindowsLatestRe: Sample of actual elog Config with URL in SSL

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

 

 

Goto page Previous  1, 2, 3 ... 179, 180, 181 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6