Last modified: 2012-06-22 21:37:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T33885, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 31885 - CheckUser WHOIS link broken
CheckUser WHOIS link broken
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-reviewed
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-10-22 16:19 UTC by dlh
Modified: 2012-06-22 21:37 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
WHOIS link patch (674 bytes, patch)
2011-10-22 16:19 UTC, dlh
Details

Description dlh 2011-10-22 16:19:31 UTC
Created attachment 9269 [details]
WHOIS link patch

On the CheckUser page there is a link to check WHOIS info, but the website's URL format changed.

Attached is a patch to fix the issue.
Comment 1 Platonides 2011-10-22 22:57:19 UTC
The old url seems to continue working.

If we changed it, maybe it should be to http://whois.arin.net/ui/arin.xsl?q=$1 (the search box on its top page)
Comment 2 John Du Hart 2011-10-23 00:24:29 UTC
Maybe we should use a WHOIS that supports RIRs other than itself. Right now I can get all the relavent information for an ARIN IP ( http://whois.arin.net/ui/arin.xsl?q=97.107.139.12 ), but anything from a different RIR is just a WHOIS for that /8 ( http://whois.arin.net/ui/arin.xsl?q=46.105.138.12 ). Not very helpful.
Comment 3 Mark A. Hershberger 2011-10-26 01:39:02 UTC
http://www.ip-address.org/tracer/ip-whois.php works but has ads.

http://whois.domaintools.com/46.105.138.12 works without ads and only a single cookie.
Comment 4 John Du Hart 2011-10-26 14:23:45 UTC
Although I love domain tools I would prefer something that's, uh, not meant to be profited from. Like the WHOIS tool on the toolserver.
Comment 5 Mark A. Hershberger 2011-10-26 19:08:02 UTC
or a PHP implementation of WHOIS? http://pear.php.net/package/Net_Whois for example:

$ pear install Net_Whois
$ php -r 'require ("Net/Whois.php");$w = new Net_Whois();echo $w->query("n 46.105.138.12");'
results in:

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=46.105.138.12?showDetails=true&showARIN=false&ext=netref2
#

NetRange:       46.0.0.0 - 46.255.255.255
CIDR:           46.0.0.0/8
OriginAS:       
NetName:        46-RIPE
NetHandle:      NET-46-0-0-0-0
Parent:         
NetType:        Allocated to RIPE NCC
Comment:        These addresses have been further assigned to users in
Comment:        the RIPE NCC region. Contact information can be found in
Comment:        the RIPE database at http://www.ripe.net/whois
RegDate:        2009-09-29
Updated:        2009-09-30
Ref:            http://whois.arin.net/rest/net/NET-46-0-0-0-0

OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:      
PostalCode:     1001EB
Country:        NL
RegDate:        
Updated:        2011-09-24
Ref:            http://whois.arin.net/rest/org/RIPE

ReferralServer: whois://whois.ripe.net:43

OrgAbuseHandle: RNO29-ARIN
OrgAbuseName:   RIPE NCC Operations
OrgAbusePhone:  +31 20 535 4444 
OrgAbuseEmail:  hostmaster@ripe.net
OrgAbuseRef:    http://whois.arin.net/rest/poc/RNO29-ARIN

OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444 
OrgTechEmail:  hostmaster@ripe.net
OrgTechRef:    http://whois.arin.net/rest/poc/RNO29-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

%ERROR:101: no entries found
%
% No entries found in the selected source(s).
Comment 6 Mark A. Hershberger 2011-10-26 19:15:06 UTC
Avoiding "n " before the IP is better since $w->query("46.105.138.12"):

#
# Query terms are ambiguous.  The query is assumed to be:
#     "n 46.105.138.12"
#
# Use "?" to get help.
#

#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=46.105.138.12?showDetails=true&showARIN=false&ext=netref2
#

NetRange:       46.0.0.0 - 46.255.255.255
CIDR:           46.0.0.0/8
OriginAS:       
NetName:        46-RIPE
NetHandle:      NET-46-0-0-0-0
Parent:         
NetType:        Allocated to RIPE NCC
Comment:        These addresses have been further assigned to users in
Comment:        the RIPE NCC region. Contact information can be found in
Comment:        the RIPE database at http://www.ripe.net/whois
RegDate:        2009-09-29
Updated:        2009-09-30
Ref:            http://whois.arin.net/rest/net/NET-46-0-0-0-0

OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:      
PostalCode:     1001EB
Country:        NL
RegDate:        
Updated:        2011-09-24
Ref:            http://whois.arin.net/rest/org/RIPE

ReferralServer: whois://whois.ripe.net:43

OrgAbuseHandle: RNO29-ARIN
OrgAbuseName:   RIPE NCC Operations
OrgAbusePhone:  +31 20 535 4444 
OrgAbuseEmail:  hostmaster@ripe.net
OrgAbuseRef:    http://whois.arin.net/rest/poc/RNO29-ARIN

OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444 
OrgTechEmail:  hostmaster@ripe.net
OrgTechRef:    http://whois.arin.net/rest/poc/RNO29-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '46.105.138.0 - 46.105.138.15'

inetnum:         46.105.138.0 - 46.105.138.15
netname:         HexxehNET
descr:           Hexxeh.net
country:         GB
org:             ORG-OL17-RIPE
admin-c:         OTC14-RIPE
tech-c:          OTC14-RIPE
status:          ASSIGNED PA
mnt-by:          OVH-MNT
source:          RIPE # Filtered

organisation:   ORG-OL17-RIPE
org-name:       OVH Ltd
org-type:       OTHER
address:        3 Southwark street
address:        LONDON SE1 1RQ
address:        UK
abuse-mailbox:  abuse@ovh.net
admin-c:        OTC2-RIPE
mnt-ref:        OVH-MNT
mnt-by:         OVH-MNT
source:         RIPE # Filtered

role:           OVH UK Technical Contact
address:        OVH Ltd
address:        3 Southwark street
address:        LONDON SE1 1RQ
address:        UK
admin-c:        OK217-RIPE
tech-c:         GM84-RIPE
nic-hdl:        OTC14-RIPE
abuse-mailbox:  abuse@ovh.net
mnt-by:         OVH-MNT
source:         RIPE # Filtered

% Information related to '46.105.0.0/16AS16276'

route:          46.105.0.0/16
descr:          OVH ISP
descr:          Paris, France
origin:         AS16276
mnt-by:         OVH-MNT
source:         RIPE # Filtered
Comment 7 p858snake 2011-10-26 22:18:53 UTC
(In reply to comment #5)
> or a PHP implementation of WHOIS? http://pear.php.net/package/Net_Whois for
> example:
> 
> $ pear install Net_Whois
> $ php -r 'require ("Net/Whois.php");$w = new Net_Whois();echo $w->query("n
> 46.105.138.12");'
> results in:
That would require the pear package of NetWhois installed wouldn't, Which is something we don't really want (more "third party" dependices)
Comment 8 Thehelpfulone 2012-05-05 11:24:24 UTC
I can see this has been marked as patch reviewed - has this been implemented yet?
Comment 9 Marcin Cieślak 2012-06-21 11:28:18 UTC
nope, filed as Gerrit change #12357
Comment 10 Marcin Cieślak 2012-06-22 21:37:12 UTC
The change has been merged into the git repository. Hope to see it live soon. Thank you!

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


Navigation
Links