All Projects apt-panopticon  apt-panopticon_cgp boxes meta-impy  ImpyReleaseBuilder NPC-tool SledjHamr  IGnoble  NGIW  opensim-SC toyboxInstaller website - cgit website - CGraphz website - Mantis

View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000048apt-panopticonFeaturepublic2019-06-25 03:202019-06-25 08:35
Reporteronefang Assigned Toonefang  
PrioritynoneSeverityfeatureReproducibilityN/A
Status confirmedResolutionopen 
Summary0000048: Deal with SRV DNS records.
DescriptionNone of the mirrors have one, so I haven't implemented this yet.
TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
related to 0000054 closedonefang Should we checkIP() on returned redirects? 

Activities

onefang

onefang

2019-06-25 03:21

administrator   ~0000042

Note that I do ask for SRV records and store them, I just don't do anything with them.
onefang

onefang

2019-06-25 08:24

administrator   ~0000049

Last edited: 2019-06-25 08:28

 Evilham -

Re: SRV is not used in deb devuan.org, it's used in some of the other involved hostnames
Mote flagrantly in deb debian.org
Think about the redirects
If one mirrpr redirects to deb.debian.org, SRVs are relevant
And "it's not used now" in a speced thing is a formula for "it's broken and we don't know how"
Has happened before with IPv6
Not used directly, but the moment a mirror redirects to an ipv6 enabled host that is not properly set up, we have a problem
yeah check _http._tcp.deb.debian.org SRV

Which answers 0000054: Should we checkIP() on returned redirects?



$ dig _http._tcp.deb.debian.org SRV

; <<>> DiG 9.10.3-P4-Debian <<>> _http._tcp.deb.debian.org SRV
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 900
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;_http._tcp.deb.debian.org.	IN	SRV

;; ANSWER SECTION:
_http._tcp.deb.debian.org. 279	IN	SRV	10 1 80 prod.debian.map.fastly.net.

;; Query time: 684 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jun 25 18:28:16 AEST 2019
;; MSG SIZE  rcvd: 100

Issue History

Date Modified Username Field Change
2019-06-25 03:20 onefang New Issue
2019-06-25 03:20 onefang Status new => assigned
2019-06-25 03:20 onefang Assigned To => onefang
2019-06-25 03:21 onefang Note Added: 0000042
2019-06-25 04:10 onefang Status assigned => feedback
2019-06-25 08:24 onefang Note Added: 0000049
2019-06-25 08:24 onefang Relationship added related to 0000054
2019-06-25 08:28 onefang Note Edited: 0000049
2019-06-25 08:35 onefang Status feedback => confirmed