Bug 1050096

This worked for me as root, but segfaulted is a regular user.

Hi Jon,

I have done all the steps above as root user when I encountered the problem.

I have segfault even if I simply run squidGuard without any arguments. Below is stack trace:
#0  0x00007ffff73305b0 in __memcpy_ssse3 () from /lib64/libc.so.6
#1  0x0000555555558ea1 in memcpy (__len=40, __src=<optimized out>, __dest=0x7ffffffd6b00) at /usr/include/bits/string3.h:51
#2  sgDbUpdate (Db=0x555555781b10, key=key@entry=0x55555577d372 "bob", value=0x557701a0 <Address 0x557701a0 out of bounds>, len=len@entry=40) at sgDb.c:513
#3  0x000055555555b7b1 in sgSourceUser (user=0x55555577d372 "bob") at sg.y:593
#4  0x000055555555f296 in yyparse () at sg.y:225
#5  0x000055555555f673 in sgReadConfig (file=<optimized out>) at sg.y:385
#6  0x0000555555557158 in main (argc=2, argv=0x7fffffffe618, envp=0x7fffffffe630) at main.c:141

ltrace shows that it happen when parsing src section of config file. In my case it is:
src admins {
    user bob administrator
}
I think it's related to #1034903.

It happens when there is "user" element in src section. In default configuration file there is "src admin" section containing "user root foo bar" element.
It is related to bug #1034903, bug #1205636, bug #1109158. Backtraces from those reports also point to this (sgSourceUser).

Hi,
I am facing the same problem. 

Actual results:
Segmentation fault (core dumped).


squidGuard.log
2015-04-26 19:31:36 [9132] init domainlist /usr/local/squidGuard/db/porn/domains
2015-04-26 19:31:37 [9132] create new dbfile /usr/local/squidGuard/db/porn/domains.db

I did some debugging. Backtrace shows, that it must be related to the following (messages during compilation):

sg.y: In function ‘sgSourceUser’:
sg.y:593:32: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
   sgDbUpdate(sp->userDb, user, (char *) setuserinfo(),
                                ^
sg.y: In function ‘sgSourceUserList’:
sg.y:649:36: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
       sgDbUpdate(sp->userDb, line, (char *) setuserinfo(),
                                    ^
sg.y:657:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
        sgDbUpdate(sp->userDb, p, (char *) setuserinfo(),
                                  ^
sg.y: In function ‘sgSourceExecUserList’:
sg.y:807:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
       sgDbUpdate(sp->userDb, sc, (char *) setuserinfo(),
                                  ^

AFAICS it affects only 64 bit systems. The workaround is to install 32-bit squidGuard package on 64-bit system.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This bug report is valid also for Fedora 22. Please don't close it without fixing.

See if the build here helps.

https://fedorapeople.org/~limb/squidGuard/

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.