Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #194912 > unrolled thread

apt-get: Error: Timeout was reached

Started byRainer Dorsch <ml@bokomoko.de>
First post2018-04-20 22:10 +0200
Last post2018-04-21 14:10 +0200
Articles 8 — 3 participants

Back to article view | Back to linux.debian.user

Contents

  apt-get: Error: Timeout was reached Rainer Dorsch <ml@bokomoko.de> - 2018-04-20 22:10 +0200
    Re: apt-get: Error: Timeout was reached <tomas@tuxteam.de> - 2018-04-20 22:20 +0200
      Re: apt-get: Error: Timeout was reached Rainer Dorsch <ml@bokomoko.de> - 2018-04-20 22:30 +0200
        Re: apt-get: Error: Timeout was reached Michael Lange <klappnase@freenet.de> - 2018-04-20 22:50 +0200
          Re: apt-get: Error: Timeout was reached Rainer Dorsch <ml@bokomoko.de> - 2018-04-21 00:00 +0200
        Re: apt-get: Error: Timeout was reached <tomas@tuxteam.de> - 2018-04-21 08:50 +0200
          Re: apt-get: Error: Timeout was reached Rainer Dorsch <ml@bokomoko.de> - 2018-04-21 11:00 +0200
            Re: apt-get: Error: Timeout was reached <tomas@tuxteam.de> - 2018-04-21 14:10 +0200

#194912 — apt-get: Error: Timeout was reached

FromRainer Dorsch <ml@bokomoko.de>
Date2018-04-20 22:10 +0200
Subjectapt-get: Error: Timeout was reached
Message-ID<vGKw3-44d-37@gated-at.bofh.it>
Hi,

I see often the error:
	Error: Timeout was reached  
during an apt-get update.

Any idea what could cause this and how to debug it?

The entire configuration is shown below.

root@master:~# apt-get -v
apt 1.4.8 (amd64)
Supported modules:
*Ver: Standard .deb
*Pkg:  Debian dpkg interface (Priority 30)
 Pkg:  Debian APT solver interface (Priority -1000)
 Pkg:  Debian APT planner interface (Priority -1000)
 S.L: 'deb' Debian binary tree
 S.L: 'deb-src' Debian source tree
 Idx: Debian Source Index
 Idx: Debian Package Index
 Idx: Debian Translation Index
 Idx: Debian dpkg status file
 Idx: Debian deb file
 Idx: Debian dsc file
 Idx: Debian control file
 Idx: EDSP scenario file
 Idx: EIPP scenario file
root@master:~# apt-get update
Ign:1 http://ftp.de.debian.org/debian stretch InRelease                        
Hit:2 http://ftp.de.debian.org/debian stretch Release                          
Hit:4 http://security.debian.org/debian-security stretch/updates InRelease
Error: Timeout was reached                   
Reading package lists... Done
root@master:~# cat /etc/apt/sources.list
# 

# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 NETINST 
20171209-12:10]/ stretch main

#deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 NETINST 
20171209-12:10]/ stretch main

deb http://ftp.de.debian.org/debian/ stretch main contrib non-free
deb-src http://ftp.de.debian.org/debian/ stretch main contrib non-free

deb http://security.debian.org/debian-security stretch/updates main contrib 
non-free
deb-src http://security.debian.org/debian-security stretch/updates main 
contrib non-free

# stretch-updates, previously known as 'volatile'
#deb http://ftp.de.debian.org/debian/ stretch-updates main contrib non-free
#deb-src http://ftp.de.debian.org/debian/ stretch-updates main contrib non-
free
root@master:~# ls -l /etc/apt/sources.list.d/
total 0
root@master:~#

Many thanks
Rainer
-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [next] | [standalone]

#194913

From<tomas@tuxteam.de>
Date2018-04-20 22:20 +0200
Message-ID<vGKFU-4d0-307@gated-at.bofh.it>
In reply to#194912
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Apr 20, 2018 at 10:02:40PM +0200, Rainer Dorsch wrote:
> Hi,
> 
> I see often the error:
> 	Error: Timeout was reached  
> during an apt-get update.

[...]

> Hit:2 http://ftp.de.debian.org/debian stretch Release                          
> Hit:4 http://security.debian.org/debian-security stretch/updates InRelease
> Error: Timeout was reached                   

Perhaps some server isn't responding? (I just tried http://security.debian.org
and it is responsive).

Or perhaps your network is flakey?

You just can check with

  curl -I http://security.debian.org/debian-security/

(also replace your other sources).

Hmm. Difficult to say.

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlraSdcACgkQBcgs9XrR2kaoIQCeOqaiE7+J6ao631UJNjzzx0go
wjEAn1E7YXZlmPA4ksvvswyA9udts+Lz
=ijaV
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#194914

FromRainer Dorsch <ml@bokomoko.de>
Date2018-04-20 22:30 +0200
Message-ID<vGKPr-4hX-73@gated-at.bofh.it>
In reply to#194913
Am Freitag, 20. April 2018, 22:13:11 CEST schrieb tomas@tuxteam.de:
> curl -I http://security.debian.org/debian-security/

root@master:~/tmp# curl -I http://ftp.de.debian.org/debian/
HTTP/1.1 200 OK
Date: Fri, 20 Apr 2018 20:19:14 GMT
Server: Apache/2.4.10 (Debian)
Content-Type: text/html;charset=UTF-8

root@master:~/tmp# curl -I http://security.debian.org/debian-security/
HTTP/1.1 200 OK
Date: Fri, 20 Apr 2018 20:19:23 GMT
Server: Apache
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
Referrer-Policy: no-referrer
X-Xss-Protection: 1
Cache-Control: max-age=120
Expires: Fri, 20 Apr 2018 20:21:23 GMT
X-Clacks-Overhead: GNU Terry Pratchett
Content-Type: text/html;charset=UTF-8

root@master:~/tmp# 


-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [prev] | [next] | [standalone]

#194915

FromMichael Lange <klappnase@freenet.de>
Date2018-04-20 22:50 +0200
Message-ID<vGL8J-4sa-1@gated-at.bofh.it>
In reply to#194914
Hi,

On Fri, 20 Apr 2018 22:20:12 +0200
Rainer Dorsch <ml@bokomoko.de> wrote:

> root@master:~# cat /etc/apt/sources.list
(...)
> deb http://security.debian.org/debian-security stretch/updates main
> contrib non-free
> deb-src http://security.debian.org/debian-security stretch/updates main 
> contrib non-free

here the entry in sources.list looks slightly different:

deb http://security.debian.org/ stretch/updates main contrib non-free

I wouldn't think this makes much difference, but just in case the timeout
occurs always with the security mirror it might be worth a try.

> root@master:~/tmp# curl -I http://security.debian.org/debian-security/
> HTTP/1.1 200 OK
> Date: Fri, 20 Apr 2018 20:19:23 GMT
> Server: Apache
> X-Content-Type-Options: nosniff
> X-Frame-Options: sameorigin
> Referrer-Policy: no-referrer
> X-Xss-Protection: 1
> Cache-Control: max-age=120
> Expires: Fri, 20 Apr 2018 20:21:23 GMT
> X-Clacks-Overhead: GNU Terry Pratchett
> Content-Type: text/html;charset=UTF-8

This looks also sightly different here:

$ curl -I http://security.debian.org/
HTTP/1.1 302 Found
Date: Fri, 20 Apr 2018 20:31:36 GMT
Server: Apache
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
Referrer-Policy: no-referrer
X-Xss-Protection: 1
Location: https://www.debian.org/security/
Cache-Control: max-age=120
Expires: Fri, 20 Apr 2018 20:33:36 GMT
Content-Type: text/html; charset=iso-8859-1

At first I thought that one of http://security.debian.org/ and
http://security.debian.org/debian-security/ was just a symlink to the
other on the same machine, but maybe the above might indicate that those
mirrors are actually not identical?

Just a thought, though.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Youth doesn't excuse everything.
		-- Dr. Janice Lester (in Kirk's body), "Turnabout
                   Intruder", stardate 5928.5.

[toc] | [prev] | [next] | [standalone]

#194916

FromRainer Dorsch <ml@bokomoko.de>
Date2018-04-21 00:00 +0200
Message-ID<vGMev-57g-49@gated-at.bofh.it>
In reply to#194915
Hi,

I just realized sometimes it also shows in apt-get upgrade:

[...]
Setting up libreoffice-writer (1:5.2.7-1+deb9u4) ...
Setting up libreoffice-base (1:5.2.7-1+deb9u4) ...
Setting up libreoffice-report-builder-bin (1:5.2.7-1+deb9u4) ...
Setting up libreoffice-report-builder (1:5.2.7-1+deb9u4) ...
Setting up libreoffice-help-en-us (1:5.2.7-1+deb9u4) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Error: Timeout was reached
root@master:~#

Am Freitag, 20. April 2018, 22:41:34 CEST schrieb Michael Lange:
> Hi,
> 
> On Fri, 20 Apr 2018 22:20:12 +0200
> 
> Rainer Dorsch <ml@bokomoko.de> wrote:
> > root@master:~# cat /etc/apt/sources.list
> 
> (...)
> 
> > deb http://security.debian.org/debian-security stretch/updates main
> > contrib non-free
> > deb-src http://security.debian.org/debian-security stretch/updates main
> > contrib non-free
> 
> here the entry in sources.list looks slightly different:
> 
> deb http://security.debian.org/ stretch/updates main contrib non-free
> 
> I wouldn't think this makes much difference, but just in case the timeout
> occurs always with the security mirror it might be worth a try.
> 
> > root@master:~/tmp# curl -I http://security.debian.org/debian-security/
> > HTTP/1.1 200 OK
> > Date: Fri, 20 Apr 2018 20:19:23 GMT
> > Server: Apache
> > X-Content-Type-Options: nosniff
> > X-Frame-Options: sameorigin
> > Referrer-Policy: no-referrer
> > X-Xss-Protection: 1
> > Cache-Control: max-age=120
> > Expires: Fri, 20 Apr 2018 20:21:23 GMT
> > X-Clacks-Overhead: GNU Terry Pratchett
> > Content-Type: text/html;charset=UTF-8
> 
> This looks also sightly different here:
> 
> $ curl -I http://security.debian.org/
> HTTP/1.1 302 Found
> Date: Fri, 20 Apr 2018 20:31:36 GMT
> Server: Apache
> X-Content-Type-Options: nosniff
> X-Frame-Options: sameorigin
> Referrer-Policy: no-referrer
> X-Xss-Protection: 1
> Location: https://www.debian.org/security/
> Cache-Control: max-age=120
> Expires: Fri, 20 Apr 2018 20:33:36 GMT
> Content-Type: text/html; charset=iso-8859-1
> 
> At first I thought that one of http://security.debian.org/ and
> http://security.debian.org/debian-security/ was just a symlink to the
> other on the same machine, but maybe the above might indicate that those
> mirrors are actually not identical?
> 
> Just a thought, though.
> 
> Regards
> 
> Michael
> 
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
> 
> Youth doesn't excuse everything.
> 		-- Dr. Janice Lester (in Kirk's body), "Turnabout
>                    Intruder", stardate 5928.5.


-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [prev] | [next] | [standalone]

#194918

From<tomas@tuxteam.de>
Date2018-04-21 08:50 +0200
Message-ID<vGUvo-2h1-1@gated-at.bofh.it>
In reply to#194914
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Apr 20, 2018 at 10:20:12PM +0200, Rainer Dorsch wrote:
> Am Freitag, 20. April 2018, 22:13:11 CEST schrieb tomas@tuxteam.de:
> > curl -I http://security.debian.org/debian-security/
> 
> root@master:~/tmp# curl -I http://ftp.de.debian.org/debian/
> HTTP/1.1 200 OK
> Date: Fri, 20 Apr 2018 20:19:14 GMT
> Server: Apache/2.4.10 (Debian)
> Content-Type: text/html;charset=UTF-8
> 
> root@master:~/tmp# curl -I http://security.debian.org/debian-security/
> HTTP/1.1 200 OK

[...]

Yeah, that succeeded *once*, but you suggested that your problem
is intermittent.

Either your network connection is sometimes down (you might see
traces of that in your system log) or security.debian.org is
sometimes down (somewhat less probable, since more folks would
complain), or "something" in the path between you two is sometimes
down.

To catch this "sometimes" you'll have to invest a bit more of
work.

I'd start by looking into syslog, around the times your upgrade
complains. Next, you might want to watch connectivity -- there sure
are nice programs out there, with graphing and things, but just
pinging your upstream router every minute might give you a rough
impression, like so:

  ping -i 60 <your upstream router here> > /tmp/connect.log 2>&1 &

and have look at the result after a day or so.

If you're on WiFi, check for bad signal quality or too many nearby
routers (or other sources of noise). If it's Ethernet, flakey cables
or connectors are known for doing nasty things. And so on.

It's a bit like hunting :-)

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlra3YgACgkQBcgs9XrR2kaS1wCfcfX3VDhq9X7azonwDojhjvL9
K5YAn2YyuMsIWQ535uR3L5S9ApZ2Ocmc
=nnfe
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#194919

FromRainer Dorsch <ml@bokomoko.de>
Date2018-04-21 11:00 +0200
Message-ID<vGWxc-3xi-15@gated-at.bofh.it>
In reply to#194918
Hi Tomás,

many thanks for your response :-)

Am Samstag, 21. April 2018, 08:43:20 CEST schrieb tomas@tuxteam.de:
> On Fri, Apr 20, 2018 at 10:20:12PM +0200, Rainer Dorsch wrote:
> > Am Freitag, 20. April 2018, 22:13:11 CEST schrieb tomas@tuxteam.de:
> > > curl -I http://security.debian.org/debian-security/
> > 
> > root@master:~/tmp# curl -I http://ftp.de.debian.org/debian/
> > HTTP/1.1 200 OK
> > Date: Fri, 20 Apr 2018 20:19:14 GMT
> > Server: Apache/2.4.10 (Debian)
> > Content-Type: text/html;charset=UTF-8
> > 
> > root@master:~/tmp# curl -I http://security.debian.org/debian-security/
> > HTTP/1.1 200 OK
> 
> [...]
> 
> Yeah, that succeeded *once*, but you suggested that your problem
> is intermittent.
> 
> Either your network connection is sometimes down (you might see
> traces of that in your system log) or security.debian.org is
> sometimes down (somewhat less probable, since more folks would
> complain), or "something" in the path between you two is sometimes
> down.
> 
> To catch this "sometimes" you'll have to invest a bit more of
> work.
> 
> I'd start by looking into syslog, around the times your upgrade
> complains. Next, you might want to watch connectivity -- there sure
> are nice programs out there, with graphing and things, but just
> pinging your upstream router every minute might give you a rough
> impression, like so:
> 
>   ping -i 60 <your upstream router here> > /tmp/connect.log 2>&1 &
> 
> and have look at the result after a day or so.
> 
> If you're on WiFi, check for bad signal quality or too many nearby
> routers (or other sources of noise). If it's Ethernet, flakey cables
> or connectors are known for doing nasty things. And so on.
> 
> It's a bit like hunting :-)

I am on ethernet and all other debian machines in the subnet are doing 
excellent. syslog was an excellent idea, indeed there are many suspicious 
entries:

Apr 21 10:35:13 master kernel: [3019173.333566] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:36:01 master kernel: [3019221.240105] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:36:11 master kernel: [3019231.951162] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:36:35 master kernel: [3019256.044369] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:37:10 master kernel: [3019290.823572] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:37:10 master kernel: [3019290.823932] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:37:10 master kernel: [3019290.824625] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:37:13 master kernel: [3019293.735943] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration
Apr 21 10:37:53 master kernel: [3019333.828612] IPv6: ipv6_create_tempaddr: 
retry temporary address regeneration

Also the output of 

root@master:~# ip addr show|wc -l
63614
root@master:~# 

and

root@master:~# ip addr show|head -40
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
    link/ether 18:66:da:20:6f:2d brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.2/24 brd 192.168.0.255 scope global dynamic eno1
       valid_lft 853609sec preferred_lft 853609sec
    inet6 fd38:81d3:9dac:0:f0ef:7ae3:c2bf:3bd8/64 scope global temporary 
dynamic 
       valid_lft 604795sec preferred_lft 86240sec
    inet6 fd38:81d3:9dac:0:80cd:9129:26ce:bee5/64 scope global temporary 
dynamic 
       valid_lft 604794sec preferred_lft 86239sec
    inet6 fd38:81d3:9dac:0:402a:7f5d:c391:9d23/64 scope global temporary 
dynamic 
       valid_lft 604793sec preferred_lft 86238sec
    inet6 fd38:81d3:9dac:0:a457:e576:bdd9:84f5/64 scope global temporary 
dynamic 
       valid_lft 604786sec preferred_lft 86231sec
    inet6 fd38:81d3:9dac:0:f928:5018:1834:fbc6/64 scope global temporary 
dynamic 
       valid_lft 604783sec preferred_lft 86228sec
    inet6 fd38:81d3:9dac:0:8ce6:e31c:4745:e335/64 scope global temporary 
dynamic 
       valid_lft 604783sec preferred_lft 86228sec
    inet6 fd38:81d3:9dac:0:818c:c093:8084:fcad/64 scope global temporary 
dynamic 
       valid_lft 604774sec preferred_lft 86219sec
    inet6 fd38:81d3:9dac:0:1c74:e734:3319:2ae3/64 scope global temporary 
dynamic 
       valid_lft 604749sec preferred_lft 86194sec
    inet6 fd38:81d3:9dac:0:15de:1534:8301:d55d/64 scope global temporary 
dynamic 
       valid_lft 604728sec preferred_lft 86173sec
    inet6 fd38:81d3:9dac:0:b05b:c204:aa6e:4cf0/64 scope global temporary 
dynamic 
       valid_lft 604720sec preferred_lft 86165sec
    inet6 fd38:81d3:9dac:0:9886:8ee9:627f:8bab/64 scope global temporary 
dynamic 
       valid_lft 604706sec preferred_lft 86151sec
    inet6 fd38:81d3:9dac:0:2de1:2328:70a:deef/64 scope global temporary 
dynamic 
       valid_lft 604698sec preferred_lft 86143sec
    inet6 fd38:81d3:9dac:0:191e:271d:2251:1bc9/64 scope global temporary 
dynamic 
       valid_lft 604688sec preferred_lft 86133sec
    inet6 fd38:81d3:9dac:0:39e3:80e5:cb6e:381f/64 scope global temporary 
dynamic 
       valid_lft 604643sec preferred_lft 86088sec
    inet6 fd38:81d3:9dac:0:c182:fa23:e7d:c3e2/64 scope global temporary 
dynamic 
       valid_lft 604643sec preferred_lft 86088sec
root@master:~# 

look really strange.

That interface is managed by network-manager .... I am wondering if I should 
fall back to /etc/network/interfaces ...

For network-manager I do not have experience on headless system, tried this 
here to get information (is the systemd-networkd not running expected?)

root@master:~# networkctl --all
WARNING: systemd-networkd is not running, output will be incomplete.

IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           n/a         unmanaged 
  2 eno1             ether              n/a         unmanaged 

2 links listed.
root@master:~# 


Any idea why IPv6 is not properly working is welcome.


Thanks
Rainer



-- 
Rainer Dorsch
http://bokomoko.de/

[toc] | [prev] | [next] | [standalone]

#194922

From<tomas@tuxteam.de>
Date2018-04-21 14:10 +0200
Message-ID<vGZv3-5Gv-7@gated-at.bofh.it>
In reply to#194919
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Apr 21, 2018 at 10:50:47AM +0200, Rainer Dorsch wrote:
> Hi Tomás,
> 
> many thanks for your response :-)

[...]

> retry temporary address regeneration
> Apr 21 10:36:01 master kernel: [3019221.240105] IPv6: ipv6_create_tempaddr: 

[...]

> Also the output of 
> 
> root@master:~# ip addr show|wc -l
> 63614

Yikes.

> root@master:~# 
> 
> and
> 
> root@master:~# ip addr show|head -40
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 
> default qlen 1
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
>        valid_lft forever preferred_lft forever
>     inet6 ::1/128 scope host 
>        valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP 
> group default qlen 1000
>     link/ether 18:66:da:20:6f:2d brd ff:ff:ff:ff:ff:ff
>     inet 192.168.0.2/24 brd 192.168.0.255 scope global dynamic eno1
>        valid_lft 853609sec preferred_lft 853609sec
>     inet6 fd38:81d3:9dac:0:f0ef:7ae3:c2bf:3bd8/64 scope global temporary 
> dynamic 
>        valid_lft 604795sec preferred_lft 86240sec
>     inet6 fd38:81d3:9dac:0:80cd:9129:26ce:bee5/64 scope global temporary 

[...]

> root@master:~# 
> 
> look really strange.

Indeed. That doesn't look sane.

Alas, with Network Manager I'm out of my depth. It *might* be this privacy
enhanced thingy (generating temporary IPV6 addresses to avoid tracking
across connections), like here:

  https://askubuntu.com/questions/764695/how-do-i-get-a-stable-ipv6-address-in-16-04

But it might be something completely different :-D

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrbKLgACgkQBcgs9XrR2kY4EgCfV/F5FARpKsOAD/fXStOemFHB
eHMAnjh01QpBG0xQtMHZgAX5ap19ZIpn
=KVet
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web