Description of problem: Tried to read a gzipd file. Version-Release number of selected component: GeoIP-1.4.8-6.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: geoiplookup -f GeoLiteCity.dat.gz 72.240.117.247 crash_function: geoiplookup executable: /usr/bin/geoiplookup kernel: 3.9.9-302.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #0 geoiplookup at geoiplookup.c:273
Created attachment 777458 [details] File: backtrace
Created attachment 777459 [details] File: cgroup
Created attachment 777460 [details] File: core_backtrace
Created attachment 777462 [details] File: dso_list
Created attachment 777463 [details] File: environ
Created attachment 777464 [details] File: limits
Created attachment 777465 [details] File: maps
Created attachment 777466 [details] File: open_fds
Created attachment 777467 [details] File: proc_pid_status
Created attachment 777468 [details] File: var_log_messages
If there's anywhere in the documentation that suggests that geoiplookup works with compressed files, please point it out and I'll reopen this bug and fix the documentation.
The bug isn't that it didn't use the file I downloaded from wget http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz but that it segfaulted with a Sig 11. There are root level programs that use geoiplookup in places which a sig-11 could possibly mean a security problem. However I understand that I didn't use the program correctly.
(In reply to Stephen John Smoogen from comment #12) > The bug isn't that it didn't use the file I downloaded from > > wget http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz > > but that it segfaulted with a Sig 11. There are root level programs that use > geoiplookup in places which a sig-11 could possibly mean a security problem. > However I understand that I didn't use the program correctly. That would not be a Fedora packaging issue but an upstream issue that the utility isn't verifying the file type first. Please open a bug upstream.
FWIW, this should be fixed in GeoIP 1.6.5 currently in testing.