1 |
On Monday, July 2, 2018 12:40:29 AM CDT Adam Carter wrote: |
2 |
> > > > Anyone one know how I can change the keyserver address used by |
3 |
> > |
4 |
> > portage? I |
5 |
> > |
6 |
> > > > keep getting "no route to host" for hkps.pool.sks-keyservers.net when |
7 |
> > |
8 |
> > I |
9 |
> > |
10 |
> > > > sync. |
11 |
> > > |
12 |
> > > What are you trying to do? Find the command being run and run it |
13 |
> > > manually while specifying --keyserver. Also file a bug report. |
14 |
> > > |
15 |
> > > I posted my last reply after pgp.mit.edu also failed. The URL you give |
16 |
> > > is obviously a key server pool, but it looks like MIT's may be also |
17 |
> > > (without inspecting it). I retried on MIT's URL until the request went |
18 |
> > > through. If you can't change the URL then keep trying. |
19 |
> > > |
20 |
> > > The issue is, I think, that the pool will give you servers that don't |
21 |
> > > support HKP, but I have had this issue when contacting keyservers |
22 |
> > > directly. |
23 |
> > > |
24 |
> > > Cheers, |
25 |
> > > |
26 |
> > > R0b0t1 |
27 |
> > |
28 |
> > Currently, portage is using that pool url when I run emaint's sync module. |
29 |
> > I |
30 |
> > keep getting the "no route to host" error from it, and no indication what |
31 |
> > server it's actually being directed to. |
32 |
> > |
33 |
> > What I want to do is reconfigure portage to use a particular server that I |
34 |
> > know |
35 |
> > is reliable. |
36 |
> |
37 |
> Looks like its using multiple A records; |
38 |
> |
39 |
> $ host hkps.pool.sks-keyservers.net |
40 |
> hkps.pool.sks-keyservers.net has address 18.9.60.141 |
41 |
> hkps.pool.sks-keyservers.net has address 18.191.65.131 |
42 |
> hkps.pool.sks-keyservers.net has address 37.191.226.104 |
43 |
> hkps.pool.sks-keyservers.net has address 92.43.111.21 |
44 |
> hkps.pool.sks-keyservers.net has address 193.164.133.100 |
45 |
> hkps.pool.sks-keyservers.net has address 216.66.15.2 |
46 |
> hkps.pool.sks-keyservers.net has IPv6 address 2001:470:1:116::6 |
47 |
> hkps.pool.sks-keyservers.net has IPv6 address 2600:1f16:41e:bd0a::73:6b73 |
48 |
> hkps.pool.sks-keyservers.net has IPv6 address |
49 |
> 2a01:4a0:59:1000:223:9eff:fe00:100f |
50 |
> hkps.pool.sks-keyservers.net has IPv6 address 2a02:c205:3001:3626::1 |
51 |
> |
52 |
> For an ugly hack you could test these to find one that works, then add that |
53 |
> one to your /etc/hosts file. |
54 |
> |
55 |
> Perhaps there's a hostmaster@××××××××××××××××××××××××.net you could notify |
56 |
> to fix it? |
57 |
|
58 |
Yes. That is how the pool URL works. It does some sort of load-balancing via |
59 |
DNS resolution. That's why it has so many addresses. |
60 |
|
61 |
I am well aware of the /etc/hosts hack, but it's an ugly work-around. I'd |
62 |
rather be able to configure portage itself to use a different pool or a specific |
63 |
server, rather than mess around with DNS resolutions. And I haven't been |
64 |
having any luck in searching for how to configure the keyserver used by |
65 |
Portage. |
66 |
|
67 |
Yes, there is an email address I could message to notify them that there is a |
68 |
problematic server, but because Portage tells me nothing about which server |
69 |
it's using other than the pool URL, I have nothing helpful to tell them. |
70 |
|
71 |
-- |
72 |
Elijah Mark Anderson |
73 |
mark@××××××.name |
74 |
-- |
75 |
「塵も積もれば山となる。」 |
76 |
"Even dust, when piled up, becomes a mountain" - Ancient Japanese proverb |