Bug 224530 - jwhois is explicitely built without caching support
jwhois is explicitely built without caching support
Product: Fedora
Classification: Fedora
Component: jwhois (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
Depends On:
  Show dependency treegraph
Reported: 2007-01-25 21:44 EST by Paul Wouters
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-29 14:48:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Document that cache can be disabled at compile time. (1.28 KB, patch)
2007-01-29 14:47 EST, Miloslav Trmač
no flags Details | Diff

  None (edit)
Description Paul Wouters 2007-01-25 21:44:55 EST
Description of problem:
jwhois is built without cache support. This causes problems with repeated
queries on TLD jwhois server swith rate limit.
It is also NOT clear from looking at either the man page or the config file

Version-Release number of selected component (if applicable):

Expected results:
A working cache. Using setgid jwhois with /var/cache/jwhois should be perfectly

Additional info:
Even if there is an argument against disabling this functionality, could we at
least mention this in the /etc/jwhois.conf file. I've had to go through this
broken cache more then once now to "remember" that it was disabled on purpose
Comment 1 Miloslav Trmač 2007-01-29 14:47:10 EST
Created attachment 146855 [details]
Document that cache can be disabled at compile time.

Thanks for your report.

As the README file says:
"Chances are, if you don't use jwhois actively, there is little point in
configuring a cache since it would not be used very much anyway."

There are two kinds of potential vulnerabilities in jwhois when using the cache
- Exploiting jwhois to run arbitrary code as the "jwhois" group and eventually
  as other users running jwhois.
  It is difficult to estimate the risk, it is probably comparable to the risk
  of exploiting jwhois by a malicious server, which we must live with.
- Intentionally polluting the shared cache with incorrect data.

  From a quick look, this seems to be possible under favorable conditions.
  The code isn't very strict about keeping the cache correct, and the fact that

  adding the whois server as a part of the cache lookup key has happened only
  in jwhois-3.2.3 doesn't inspire much confidence.

So, I don't think enabling the global cache is worth the risk;	I have sent the
attached patch upstream to note the possibility of disabled cache in the

Ideally, it should be possible to have a per-user cache, but that development
probably needs to happen upstream.

Note You need to log in before you can comment on or make changes to this bug.