Bug 215321 - net/jwhois with damaged base consumes all available memory and crashes many other running services
Summary: net/jwhois with damaged base consumes all available memory and crashes many o...
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Tobias Kortkamp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-15 14:14 UTC by Vladyslav V. Prodan
Modified: 2018-12-28 05:19 UTC (History)
1 user (show)

See Also:

Attachments
truss jwhois -c /usr/local/etc/jwhois.conf.1 5.230.141.0/24 (44.59 KB, text/plain)
2016-12-15 14:17 UTC, Vladyslav V. Prodan 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladyslav V. Prodan 2016-12-15 14:14:26 UTC 
Subj.

FreeBSD 11.0-STABLE #0 r309276: Tue Nov 29 13:33:29 EET 2016

# pkg info jwhois
jwhois-4.0_5
Name           : jwhois
Version        : 4.0_5
Installed on   : Wed Dec 14 05:32:57 2016 EET
Origin         : net/jwhois
Architecture   : freebsd:11:x86:64

# diff jwhois.conf.1 jwhois.conf.sample
950c950
< cachefile = "/var/db/jwhois/jwhois2";
---
> #cachefile = "/var/lib/jwhois.db";
956d955
< cacheexpire = 96;
967c966
< browser-pathname = "/usr/local/bin/lynx";
---
> browser-pathname = "/usr/bin/lynx";
1005c1004
< connect-timeout = 12;
---
> #connect-timeout = 3;

#truss jwhois -c /usr/local/etc/jwhois.conf.1 5.230.141.0/24

Attached trace query and problem in the database
Comment 1 Vladyslav V. Prodan 2016-12-15 14:17:43 UTC 
Created attachment 177986 [details]
truss jwhois -c /usr/local/etc/jwhois.conf.1 5.230.141.0/24

The output truss command
Comment 2 Vladyslav V. Prodan 2016-12-15 14:20:25 UTC 
And archive of problem in the database

https://mega.nz/#!1pJTkQJD!Sx6Pf9rn486gjjjeFLGG4f5PT9HYnLPayeRgwffIblY
Comment 3 Walter Schwarzenfeld freebsd_triage 2018-01-13 02:23:20 UTC 
Maintainer feedback, please!
Comment 4 Marco Steinbach 2018-01-16 12:04:38 UTC 
Hi.

I think this port does not have a maintainer -- the MAINTAINER entry in the Makefile points to ports@.

I've removed myself from this PR.
Comment 5 Walter Schwarzenfeld freebsd_triage 2018-01-16 12:10:19 UTC 
Sorry, my fault.
Comment 6 Tobias Kortkamp freebsd_committer freebsd_triage 2018-12-28 05:19:19 UTC 
Things like this need to be reported upstream.  There is very little we can do
when the code is unable to handle corrupted databases and behaves badly with
them.  I do not see any evidence that this is intrinsic to the FreeBSD port.