Releases: RIPE-NCC/whois
Releases · RIPE-NCC/whois
Whois Release 1.117
Whois release 1.117 contains the following changes:
- Parent status for LIR-PARTITIONED PA cannot be ASSIGNED PA (#1669)
- ASSIGNED PA Cannot have less/more specific ASSIGNED PA (#1672)
- Aggregation by LIR Parent should not be allowed for Aggregation by LIR (#1673)
- Do not allow LIR-PARTITIONED PA under SUB-ALLOCATED PA in (#1702)
- RDAP Self Links Must Have the Type Set (#1685)
- RDAP Validate Correct Key Before Redirect (#1689)
- RDAP Fix Relation For Cross-Prefix Inetnum Range (#1693)
- RDAP Bottom should check Parent does not CONTAINS search term (#1701)
- RDAP Non Existing Search IP Terms in TOP and UP (#1703)
- RDAP Add "-rdap" prefix to Relations And Change links (#1700)
- RDAP Minimum status for Relations (#1705)
- NRTMv4 Correct aut-num object class name in delta file (#1692)
- NRTMv4 Client Reject Deltas When Discontinuous and reinitialise (#1699)
- NRTMv4 Client Reject update in case client is ahead instead of reinitialise (#1698)
- Support OAuth 2.0 (#1688)
Whois 1.116 Release
Whois release 1.116 contains the following changes :
- RDAP Relation Searches Endpoint (#1603)
- Fixes to RDAP RIR-Search (Basic Searches) Feature (#1611)
- Return Abuse-c Entity for RDAP organisation Entity Query (#1659)
- Update key-cert lookup URL in update notification (#1631)
- Warn if mbrs-by-ref in set object is changed (#1662)
- Warn on override if set membership claim is not supported by mbrs-by-ref (#1660)
- NRTMv4 use EC p256 key instead of ec25519 (#1645)
- Remove old NRTMv4 Update Notification File Links (#1652)
- Do not send the SOURCE in NRTMv4 relative URLs (#1654)
Whois 1.115.1 Release
Whois release 1.115.1 contains the following change:
- Fix parsing API key details
Whois 1.115 Release
Whois release 1.115 contains the following changes
- API key authentication (#1569, #1597, #1618, #1620, #1622, #1624, #1626, #1627)
- NRTMv4 client implementation (#1560, #1574, #1575, #1596, #1579, #1577, #1605, #1609, #1610, #1621)
- Use relative path in NRTMv4 update notification file (#1583)
- Add JWS Support To Fix Race Condition in NRTMv4 (#1564, #1589)
- Add MNTNER to RDAP Entities Search (#1612)
- Import ARIN and LACNIC IRR database dumps into mirror (#1428)
- Syncupdates will return an error in future if used over HTTP (#1561)
- Mailupdates will return an error in future if a password is used (#1559)
- Include password authentication type in Whois Update notifications (#1541)
- Extend Maximum Length of an Email Address (#1545)
- Allow blocking by source address on Port 43 Queries (#1539)
- Generate mail Message-ID including angle brackets. (#1534)
- Change Database Schema from Latin1 to UTF8 (#1525)
Whois Release 1.114
Whois release 1.114 contains the following changes:
- NRTMv4 Key Rotation (#1484)
- Return an error if an email address is longer than 80 characters (#1492)
- DoS Filter for Update Requests (#1495)
- Block IP Filter (#1498)
- Use transaction manager per datasource (#1501)
- "text" Content Type processed as "text/plain" for Mail Messages (#1515)
- Add Warning When Password Authentication is used in Mailupdates (#1511)
- Mp-member Attribute is clickable (#1506)
Whois Release 1.113.2
30e26dc2
Whois Release 1.112.1
[update] validate max references (#1486)
Whois Release 1.113.1
bd49c515
Whois Release 1.113
Whois Release 1.112
- [all] NWI-4: Add ALLOCATED-ASSIGNED PA inetnum status (#1432)
- [query] Set Charset Flag (#1450)
- [update] Don't allow "mnt-lower" on assignments (#1452)
- [api] Fixed Syncupdates HELP Bug (#1453)
- [rdap] RDAP Link Title is a String not List (#1445)
- [mail] Remove Message If Bounce Detection Or Unsubscribe Fails (#1418)
- [mail] Handle Multiple Delivery Status Notification Failure Responses for the Same Email Address (#1417)
- [mail] Final-Recipient: RFC822 is case insensitive (#1423)
- [mail] Refactor Mail Sender to allow multiple recipients (#1411)
- [all] Route ROA checker (#1416)
- [all] Schedule ROA load each 15 minutes (#1444)
- [query] Allow inverse query for e-mail from trusted addresses (#1435)
- [query] Allow inverse query for sponsoring-org from all addresses (#1431)
- [nrtm] Return 404 on invalid NRTMv4 notification file path (#1422)