public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: jwhois appears to be no longer maintained
Date: Wed, 04 Aug 2021 16:30:03 +0200	[thread overview]
Message-ID: <8F14DD31-1D66-42C1-80B3-88B288F5CFB7@ipfire.org> (raw)
In-Reply-To: <ca8da8ec-4634-4657-06f4-04bb90833752@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2614 bytes --]

Hi,

> On 29 Jul 2021, at 21:01, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Peter,
> 
> So I have been able to successfully build the new whois and have installed it into a vm and tested it out with an IP address and it worked giving the same info as with jwhois on my production IPFire system.
> 
> One thing that I am not sure about. With jwhois there are a lot of entries in /etc/jwhois.conf and then there are a couple of patches in /src/patches adding more into jwhois.conf
> 
> For the new whois the whois.conf is empty with just a note saying that if the compiled in servers are not adequate then additional ones can be added to the whois.conf.
> 
> The format for the whois.conf is different from the jwhois.conf with the = separator being replaced by a blank space. In jwhois there are also some entries with two lines with the second line giving the query format which does not look to be able to be used in whois.conf
> 
> jwhois.conf says that the type can be either cidr or regex
> 
> whois.conf says that each entry consists of a regex followed by the server. There is no mention of cidr
> 
> 
> It is not clear to me if the entries in jwhois.conf and the two jwhois patches need to be included into whois.conf but if they do then I need some help about how to reconcile the differences.

We do not have any custom changes in our configuration. This was just what we imported from somewhere else and I understood it as the standard set of servers.

I suppose removing the old configuration and continuing with a fresh default configuration is the way to go.

-Michael

> 
> Regards,
> 
> Adolf.
> 
> 
> On 21/07/2021 12:10, Adolf Belka wrote:
>> Hi Peter,
>> 
>> I haven't seen anyone else pick this up so I will give it a go and see how I get on.
>> 
>> Regards,
>> 
>> Adolf
>> 
>> On 30/05/2021 12:01, Peter Müller wrote:
>>> Hello development folks,
>>> 
>>> looking at it's Git repository (https://github.com/jonasob/jwhois), jwhois does not seem to be
>>> maintained anymore. It's last commit currently dates November 20th, 2015, while the latest release
>>> was tagged on July 10th, 2005.
>>> 
>>> Debian switched to another WHOIS client (https://github.com/rfc1036/whois), being far more actively
>>> maintained than jwhois (see also: https://packages.debian.org/buster/whois). From my point of view,
>>> we should to as well.
>>> 
>>> Since I am currently short on spare time: Is someone volounteering to do this for me?
>>> 
>>> Whoever it will be, thank you. :-)
>>> 
>>> Thanks, and best regards,
>>> Peter Müller


  reply	other threads:[~2021-08-04 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30 10:01 Peter Müller
2021-07-21 10:10 ` Adolf Belka
2021-07-29 19:01   ` Adolf Belka
2021-08-04 14:30     ` Michael Tremer [this message]
2021-08-04 16:59       ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8F14DD31-1D66-42C1-80B3-88B288F5CFB7@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox