Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 285 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  67606   Thu Nov 7 08:08:12 2013 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX2.9.2-2494Re: Compilation failure on Mac OSX 10.9

A.G. Schubert wrote:

Stefan Ritt wrote:

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.

Best regards,
Stefan 

Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74.  I undid my changes to Makefile, tried to compile, but got the same errors.  

I then pulled down elog and mxml with git, and these are working for me with no errors.  Thanks!

SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon. 

  67640   Thu Dec 19 19:42:48 2013 Disagree John Haggertyhaggerty@bnl.govBug reportMac OSX2.9.2-2475ELOG on Chrome on MacOS?
In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text.  I ran elogd -v by hand, 
and there were no obvious problems, and I looked at the developer consoles in Chrome, and the only place I see any hint of what the problem might 
be is the Javascript console which says this:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
Uncaught SecurityError: Blocked a frame with origin "http://localhost:8080" from accessing a frame with origin "chrome-
extension://pioclpoplcdbaefihamjohnefbikjilc".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of 
"chrome-extension". Protocols must match.
 fckeditorcode_gecko.js:36

It works ok in Safari, but it would be nice to use Chrome, and it was working ok until recently.  I don't think the problem occurred when I updated to 
Mac OS 10.9.1, but I don't keep careful track of the Chrome version.  It's not critical, but I pretty much exhausted what I knew how to debug.  I have 
close to the latest elog (2.9.2-2455), although I see the same phenomenon on this elog (.2.9.2-2475) and I think it's related to this thread:

http://productforums.google.com/forum/#!msg/maps/hQhwWA56NbA/2XL35dU7le4J

I tried the prescription in the October 22 entry, but it didn't seem to help, although I wasn't sure I had really tested it with compressed javascript and 
cache and what have you.
  67641   Fri Dec 20 09:25:08 2013 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX2.9.2-2475Re: ELOG on Chrome on MacOS?
> In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
> Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
> in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text. 

That's strange. I just tried myself (by accident I have the same versions of Chrome and OSX) and it just worked fine. The fckedit code has not change a long time, so I guess it's not related to the exact version of 
elogd. Anyhow I want to switch to ckedit when I get some time, which maybe fixes the problem. What happens if you try to write in this forum, do you have the same problem? Sometime the fcdedit code take 
quite long time to load when accessed remotely. If your browser gives up, you might hat to click on "reload". In chrome there is also the "Developer tools" window, which shows you all HTTP requests and 
responses on the network. Otherwise I run out of ideas what could be different for you compared to me.

Cheers,
Stefan
  67642   Fri Dec 20 13:38:09 2013 Reply John Haggertyhaggerty@bnl.govBug reportMac OSX2.9.2-2475Re: ELOG on Chrome on MacOS?
> > In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
> > Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
> > in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text. 
> 
> That's strange. I just tried myself (by accident I have the same versions of Chrome and OSX) and it just worked fine. The fckedit code has not change a long time, so I guess it's not related to the exact version of 
> elogd. Anyhow I want to switch to ckedit when I get some time, which maybe fixes the problem. What happens if you try to write in this forum, do you have the same problem? Sometime the fcdedit code take 
> quite long time to load when accessed remotely. If your browser gives up, you might hat to click on "reload". In chrome there is also the "Developer tools" window, which shows you all HTTP requests and 
> responses on the network. Otherwise I run out of ideas what could be different for you compared to me.
> 
> Cheers,
> Stefan

Later on, I tried the prescription pointed to in that thread that says in scripts/fckeditor/editor/js/fckeditorcode_gecko.js to replace

FCKTools.FixDocumentParentWindow = function(A){ if (A.document) A.document.parentWindow=A; for (var i=0;i<A.frames.length;i++) FCKTools.FixDocumentParentWindow(A.frames[i]);};

with: 

FCKTools.FixDocumentParentWindow = function(A){try{ if (A.document) A.document.parentWindow=A;} catch(e){};for (var i=0;i<A.frames.length;i++) FCKTools.FixDocumentParentWindow(A.frames[i]);};

and after I got all my brackets straight, my pages were visible.  I'm still not sure when this turned up, since I use my elog every day (hour) and so I'd hardly miss it when I upgraded various things, although I don't watch Chrome updating itself that closely.

Have a good holiday!
  67646   Tue Jan 7 04:28:28 2014 Agree John Haggertyhaggerty@bnl.govBug reportMac OSX2.9.2Due to Evernote web clipper
I investigated a little further the problem with fckedit in Chrome with the hints in the Chrome Developer Javascript window for debugging, and it seems the problem occurs when I have the Evernote web clipper extension enabled. If I disable it, I am able to make entries on any server, otherwise the cursor is missing and there is no way to enter text as reported in an earlier thread that I inadvertently failed to reply to.
  67650   Tue Jan 14 05:19:47 2014 Reply Ed McNicholed@mcnichol.comBug reportMac OSX2.9.2-2494Re: Compilation failure on Mac OSX 10.9

Stefan Ritt wrote:

A.G. Schubert wrote:

Stefan Ritt wrote:

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.

Best regards,
Stefan 

Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74.  I undid my changes to Makefile, tried to compile, but got the same errors.  

I then pulled down elog and mxml with git, and these are working for me with no errors.  Thanks!

SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon. 

 I too am having issues installing on Mac OS X 10.9.1. I changed CFLAGS in makefile to;

CFLAGS += -O3 -funroll-loops -fomit-frame-pointer -W -Wall -D_FORTIFY_SOURCE=0

I get many lines of errors like this when I run make;

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/openssl/ssl.h:1491:6: note: 'SSL_accept' declared here

int     SSL_accept(SSL *ssl) DEPRECATED_IN_MAC_OS_X_VERSION_10_7_AND_LATER;

        ^

src/elogd.c:28809:19: warning: 'SSL_set_fd' is deprecated: first deprecated in OS X 10.7 [-Wdeprecated-declarations]

                  SSL_set_fd(ka_ssl_con[i_min], ka_sock[i_min]);

 

                  ^

 
  67651   Tue Jan 14 08:15:19 2014 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX2.9.2-2494Re: Compilation failure on Mac OSX 10.9

Ed McNichol wrote:

Stefan Ritt wrote:

A.G. Schubert wrote:

Stefan Ritt wrote:

A.G. Schubert wrote:

When compiling elog on OSX 10.9 (Mavericks), I get the error below.

Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.

All over sudden gcc comes with its own version of "strlcpy", which I had defined "manually" since many years inside ELOG. Using -DFORTIFY_SOURCE=0 will not harm, so you can use it. The "real" solution is to take our ELOG's strlcpy/strlcat, which I did on the current SVN version.

Best regards,
Stefan 

Ok, I tried updating my SVN working copy, but I didn't get any updates past elog rev. 2494, mxml rev. 74.  I undid my changes to Makefile, tried to compile, but got the same errors.  

I then pulled down elog and mxml with git, and these are working for me with no errors.  Thanks!

SVN is obsolete and will NOT be maintained any more, since we completely switched to GIT. Actually I will disable the service soon. 

 I too am having issues installing on Mac OS X 10.9.1. I changed CFLAGS in makefile to;

CFLAGS += -O3 -funroll-loops -fomit-frame-pointer -W -Wall -D_FORTIFY_SOURCE=0

I get many lines of errors like this when I run make;

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/openssl/ssl.h:1491:6: note: 'SSL_accept' declared here

int     SSL_accept(SSL *ssl) DEPRECATED_IN_MAC_OS_X_VERSION_10_7_AND_LATER;

        ^

src/elogd.c:28809:19: warning: 'SSL_set_fd' is deprecated: first deprecated in OS X 10.7 [-Wdeprecated-declarations]

                  SSL_set_fd(ka_ssl_con[i_min], ka_sock[i_min]);

 

                  ^

 

If you would use the Makefile from the GIT repository there would be no errors under OS X 10.9.1:

/elog$ make                                                                                                                                                                 
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -w -c -o crypt.o src/crypt.c                                         
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -o elog src/elog.c crypt.o -lssl                                     
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -w -c -o regex.o src/regex.c                                         
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -w -c -o auth.o src/auth.c                                           
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -c -o mxml.o ../mxml/mxml.c                                          
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -c -o strlcpy.o ../mxml/strlcpy.c                                    
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -o elogd src/elogd.c crypt.o auth.o regex.o mxml.o strlcpy.o -lssl   
cc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations -I../mxml  -DHAVE_SSL -o elconv src/elconv.c -lssl                                         
/elog$                                                                                                                                                                      

Actually what you need is -Wno-deprecated-declarations to suppress the warnings. The open SSL functions will at some point be removed from OSX, they have their own implementation of SSL. So then we either have to ship openSSL together with elog or use Apple's implementatoin. But for now we are still fine.

/Stefan

 

 

  67746   Mon Jan 12 23:26:18 2015 Question Eric Quinteroericq@caltech.eduBug reportMac OSX3.0.0Problem with embedded Iframes

We've upgraded our ELOG installation to v3, and we really like the new CKeditor. However, one of my users has noticed a problem when using Iframe HTML elements with CKeditor; namely that the HTML is not present when trying to edit the post, and saving the post erases the HTML. 
I was able to reproduce this fairly simply, by trying to embed a youtube video. I would create a new post, click the "Source" view in CKeditor, and paste something like the following:
<iframe width="420" height="315" src="//www.youtube.com/embed/RzZgFKoIfQI" frameborder="0" allowfullscreen></iframe>
Upon submission, this produces a totally normal .log file in the logbook directory, and the video is viewable on the ELOG page:

Date: Mon, 22 Dec 2014 15:52:20 -0800
Author: test
Type: General
Category: General
Subject: test
Attachment:
Encoding: HTML
========================================
<iframe width="420" height="315" src="//www.youtube.com/embed/RzZgFKoIfQI" frameborder="0" allowfullscreen></iframe>


Then, upon hitting "Edit," I am greeted by a totally empty CKeditor window, and hitting "Source" does not display the original HTML. 
Any help is greatly appreciated!

PS: Including the first line of the logfile in this very post would cause the submitted post to be truncated for some reason, although the preview looked fine. Pasting it here also caused the log to end abruptly. The string is "(dollar sign)(at symbol)MID(at symbol)(dollar sign): 9"

ELOG V3.1.5-3fb85fa6