Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #189609 > unrolled thread
| Started by | Urs Thuermann <urs@isnogud.escape.de> |
|---|---|
| First post | 2017-12-06 23:20 +0100 |
| Last post | 2017-12-07 08:50 +0100 |
| Articles | 7 on this page of 127 — 38 participants |
Back to article view | Back to linux.debian.user
Embarrassing security bug in systemd Urs Thuermann <urs@isnogud.escape.de> - 2017-12-06 23:20 +0100
Re: Embarrassing security bug in systemd Roberto C. Sánchez <roberto@debian.org> - 2017-12-06 23:50 +0100
Re: Embarrassing security bug in systemd Ben Caradoc-Davies <ben@transient.nz> - 2017-12-07 00:40 +0100
Re: Embarrassing security bug in systemd Roberto C. Sánchez <roberto@debian.org> - 2017-12-07 03:50 +0100
Re: Embarrassing security bug in systemd deloptes <deloptes@gmail.com> - 2017-12-07 07:30 +0100
Re: Embarrassing security bug in systemd Ben Caradoc-Davies <ben@transient.nz> - 2017-12-06 23:50 +0100
Re: Embarrassing security bug in systemd Dave Sherohman <dave@sherohman.org> - 2017-12-07 10:40 +0100
Re: Embarrassing security bug in systemd Tixy <tixy@yxit.co.uk> - 2017-12-07 11:30 +0100
Re: Embarrassing security bug in systemd Jonathan Dowland <jmtd@debian.org> - 2017-12-07 11:50 +0100
Re: Embarrassing security bug in systemd Jimmy Johnson <field.engineer@gmail.com> - 2017-12-09 03:50 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-09 17:50 +0100
Re: Embarrassing security bug in systemd Jimmy Johnson <field.engineer@gmail.com> - 2017-12-10 10:00 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-10 20:40 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-07 11:40 +0100
Re: Embarrassing security bug in systemd Roberto C. Sánchez <roberto@debian.org> - 2017-12-07 16:00 +0100
Re: Embarrassing security bug in systemd Michael Biebl <biebl@debian.org> - 2017-12-07 20:30 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-08 09:20 +0100
Re: Embarrassing security bug in systemd deloptes <deloptes@gmail.com> - 2017-12-08 12:40 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-08 13:40 +0100
Re: Embarrassing security bug in systemd deloptes <deloptes@gmail.com> - 2017-12-08 21:40 +0100
Re: Embarrassing security bug in systemd Jonathan Dowland <jmtd@debian.org> - 2017-12-08 17:10 +0100
Re: Embarrassing security bug in systemd Curt <curty@free.fr> - 2017-12-08 19:10 +0100
Re: Embarrassing security bug in systemd Menelaos Maglis <mmaglis@metacom.gr> - 2017-12-08 19:40 +0100
Re: Embarrassing security bug in systemd Menelaos Maglis <mmaglis@metacom.gr> - 2017-12-08 19:50 +0100
Re: Embarrassing security bug in systemd Jonathan Dowland <jmtd@debian.org> - 2017-12-08 20:50 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-08 21:20 +0100
Re: Embarrassing security bug in systemd Jonathan Dowland <jmtd@debian.org> - 2017-12-09 09:10 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-09 11:20 +0100
Re: Embarrassing security bug in systemd Jonathan Dowland <jmtd@debian.org> - 2017-12-09 19:40 +0100
Re: Embarrassing security bug in systemd Dejan Jocic <jodejka@gmail.com> - 2017-12-09 20:30 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-09 22:00 +0100
Re: Embarrassing security bug in systemd Dejan Jocic <jodejka@gmail.com> - 2017-12-10 00:40 +0100
Re: Embarrassing security bug in systemd Joe <joe@jretrading.com> - 2017-12-10 10:40 +0100
Re: Embarrassing security bug in systemd Dejan Jocic <jodejka@gmail.com> - 2017-12-10 11:20 +0100
Re: Embarrassing security bug in systemd Joe <joe@jretrading.com> - 2017-12-10 12:40 +0100
Re: Embarrassing security bug in systemd Dejan Jocic <jodejka@gmail.com> - 2017-12-10 16:10 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-11 15:10 +0100
Re: Embarrassing security bug in systemd Roberto C. Sánchez <roberto@debian.org> - 2017-12-09 21:10 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-09 21:10 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-08 21:50 +0100
Re: Embarrassing security bug in systemd John Hasler <jhasler@newsguy.com> - 2017-12-08 22:30 +0100
Re: Embarrassing security bug in systemd Glenn English <ghe2001@gmail.com> - 2017-12-09 02:50 +0100
Re: Embarrassing security bug in systemd John Hasler <jhasler@newsguy.com> - 2017-12-09 06:50 +0100
Re: Embarrassing security bug in systemd Jonathan Dowland <jmtd@debian.org> - 2017-12-09 09:20 +0100
Re: Embarrassing security bug in systemd Jonathan Dowland <jmtd@debian.org> - 2017-12-09 09:10 +0100
Re: Embarrassing security bug in systemd Christian Seiler <christian@iwakd.de> - 2017-12-15 13:30 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-15 14:10 +0100
Re: Embarrassing security bug in systemd John Hasler <jhasler@newsguy.com> - 2017-12-15 16:00 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-08 21:50 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-08 22:40 +0100
Re: Embarrassing security bug in systemd John Hasler <jhasler@newsguy.com> - 2017-12-09 00:30 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-09 10:00 +0100
Re: Embarrassing security bug in systemd Dave Sherohman <dave@sherohman.org> - 2017-12-08 10:00 +0100
Re: Embarrassing security bug in systemd Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-12-08 23:40 +0100
Re: Embarrassing security bug in systemd Joe <joe@jretrading.com> - 2017-12-09 00:30 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-09 01:20 +0100
Re: Embarrassing security bug in systemd Joe <joe@jretrading.com> - 2017-12-09 11:40 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-09 15:30 +0100
Re: Embarrassing security bug in systemd The Wanderer <wanderer@fastmail.fm> - 2017-12-10 01:00 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-10 22:20 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-09 17:50 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-09 18:20 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-09 21:20 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-10 12:00 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-10 17:10 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-10 20:40 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-10 21:30 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-10 23:10 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-11 00:10 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-11 00:50 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-11 12:30 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-11 13:40 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-11 14:40 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-10 21:50 +0100
Re: Embarrassing security bug in systemd Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2017-12-11 13:00 +0100
Re: Embarrassing security bug in systemd <tomas@tuxteam.de> - 2017-12-11 13:40 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-11 16:30 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-10 23:10 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-11 01:30 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-11 04:40 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-11 06:10 +0100
Re: Embarrassing security bug in systemd Gene Heskett <gheskett@shentel.net> - 2017-12-11 07:40 +0100
Rust? (and a wordsmithing question) (was: Re: Embarrassing security bug in systemd) rhkramer@gmail.com - 2017-12-11 15:40 +0100
Re: Rust? (and a wordsmithing question) (was: Re: Embarrassing security bug in systemd) Darac Marjal <mailinglist@darac.org.uk> - 2017-12-11 16:00 +0100
Re: Rust? (and a wordsmithing question) (was: Re: Embarrassing security bug in systemd) rhkramer@gmail.com - 2017-12-11 18:30 +0100
Re: Rust? (and a wordsmithing question) (was: Re: Embarrassing security bug in systemd) Joe <joe@jretrading.com> - 2017-12-11 16:30 +0100
Re: Rust? (and a wordsmithing question) "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2017-12-11 17:40 +0100
Re: Rust? (and a wordsmithing question) David Wright <deblis@lionunicorn.co.uk> - 2017-12-11 20:10 +0100
Re: Rust? (and a wordsmithing question) <tomas@tuxteam.de> - 2017-12-12 09:30 +0100
Re: Rust? (and a wordsmithing question) "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2017-12-12 17:30 +0100
Re: Rust? (and a wordsmithing question) <tomas@tuxteam.de> - 2017-12-12 17:50 +0100
Re: Rust? (and a wordsmithing question) Curt <curty@free.fr> - 2017-12-12 18:20 +0100
Re: Rust? (and a wordsmithing question) Richard Hector <richard@walnut.gen.nz> - 2017-12-13 04:40 +0100
Re: Rust? (and a wordsmithing question) (was: Re: Embarrassing security bug in systemd) rhkramer@gmail.com - 2017-12-11 18:30 +0100
Re: Rust? (and a wordsmithing question) (was: Re: Embarrassing security bug in systemd) David Wright <deblis@lionunicorn.co.uk> - 2017-12-12 19:10 +0100
UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd) Jason <electron@emypeople.net> - 2018-01-09 05:10 +0100
Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd) Christian Groessler <chris@groessler.org> - 2018-01-09 16:00 +0100
Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd) Roberto C. Sánchez <roberto@debian.org> - 2018-01-09 16:30 +0100
Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd) Christian Groessler <chris@groessler.org> - 2018-01-09 18:10 +0100
Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd) Erik Christiansen <dvalin@internode.on.net> - 2018-01-10 04:50 +0100
Re: Embarrassing security bug in systemd Menelaos Maglis <mmaglis@metacom.gr> - 2017-12-09 01:40 +0100
Re: Embarrassing security bug in systemd Mark Fletcher <mark27q1@gmail.com> - 2017-12-09 03:10 +0100
Re: Embarrassing security bug in systemd Joe <joe@jretrading.com> - 2017-12-09 10:50 +0100
Re: Embarrassing security bug in systemd Ric Moore <wayward4now@gmail.com> - 2017-12-09 16:40 +0100
Re: Embarrassing security bug in systemd Tom Furie <tom@furie.org.uk> - 2017-12-09 17:10 +0100
Re: Embarrassing security bug in systemd Ben Caradoc-Davies <ben@transient.nz> - 2017-12-09 22:10 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-09 18:20 +0100
Re: Embarrassing security bug in systemd Michael Stone <mstone@debian.org> - 2017-12-07 00:00 +0100
Re: Embarrassing security bug in systemd Joe <joe@jretrading.com> - 2017-12-07 09:40 +0100
Re: Embarrassing security bug in systemd Glenn English <ghe2001@gmail.com> - 2017-12-07 00:10 +0100
Re: Embarrassing security bug in systemd Brian <ad44@cityscape.co.uk> - 2017-12-07 00:10 +0100
Re: Embarrassing security bug in systemd Roberto C. Sánchez <roberto@debian.org> - 2017-12-07 03:50 +0100
Re: Embarrassing security bug in systemd Michael Lange <klappnase@freenet.de> - 2017-12-07 00:20 +0100
Re: Embarrassing security bug in systemd "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2017-12-07 00:50 +0100
Re: Embarrassing security bug in systemd Michael Stone <mstone@debian.org> - 2017-12-07 01:20 +0100
Re: Embarrassing security bug in systemd Roberto C. Sánchez <roberto@debian.org> - 2017-12-07 03:50 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-07 02:10 +0100
Re: Embarrassing security bug in systemd Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-12-07 03:40 +0100
Re: Embarrassing security bug in systemd Eric S Fraga <e.fraga@ucl.ac.uk> - 2017-12-07 08:30 +0100
Re: Embarrassing security bug in systemd Michael Biebl <biebl@debian.org> - 2017-12-07 00:50 +0100
Re: Embarrassing security bug in systemd Dejan Jocic <jodejka@gmail.com> - 2017-12-07 02:40 +0100
Re: Embarrassing security bug in systemd Menelaos Maglis <mmaglis@metacom.gr> - 2017-12-08 10:40 +0100
Re: Embarrassing security bug in systemd Roberto C. Sánchez <roberto@debian.org> - 2017-12-08 13:40 +0100
Re: Embarrassing security bug in systemd deloptes <deloptes@gmail.com> - 2017-12-08 20:10 +0100
Re: Embarrassing security bug in systemd David Wright <deblis@lionunicorn.co.uk> - 2017-12-07 01:10 +0100
Re: Embarrassing security bug in systemd Eric S Fraga <e.fraga@ucl.ac.uk> - 2017-12-07 08:30 +0100
Re: Embarrassing security bug in systemd David Baron <dbaron770@gmail.com> - 2017-12-07 08:50 +0100
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
| From | Dejan Jocic <jodejka@gmail.com> |
|---|---|
| Date | 2017-12-07 02:40 +0100 |
| Message-ID | <uTTkm-7UR-19@gated-at.bofh.it> |
| In reply to | #189619 |
On 07-12-17, Michael Biebl wrote: > > As has already been mentioned, active, local users can shutdown/reboot > the system without requiring a password. This is intended behaviour (for > the reasons already mentioned) and can indeed be overridden by custom > polkit rules. > Is there anywhere in Debian documentation example, or explanation how to override anything with custom polkit rules? I could not find it, but guess that it is possible that somehow I've missed it. > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? >
[toc] | [prev] | [next] | [standalone]
| From | Menelaos Maglis <mmaglis@metacom.gr> |
|---|---|
| Date | 2017-12-08 10:40 +0100 |
| Message-ID | <uUnip-2dT-3@gated-at.bofh.it> |
| In reply to | #189619 |
>>> I wonder how can such a severe bug make it into a Debian stable >>> distribution? And is this just an insane default setting on Debian's >>> side or is it yet another instance of brain-dead systemd behavior? >> >> Maybe I am just a brain-dead loony, but personally I prefer to be able to >> shut down or reboot my system without having to type a password. If you >> do not like this behavior you might have to learn how to define >> polkit rules. > > For the interested reader, see > /usr/share/polkit-1/actions/org.freedesktop.login1.policy > > org.freedesktop.login1.power-off has the following defaults > > <defaults> > <allow_any>auth_admin_keep</allow_any> > <allow_inactive>auth_admin_keep</allow_inactive> > <allow_active>yes</allow_active> > </defaults> > > As has already been mentioned, active, local users can shutdown/reboot > the system without requiring a password. This is intended behaviour (for > the reasons already mentioned) and can indeed be overridden by custom > polkit rules. It is an improvement to have a consistent (central) way to configure this behavior. It is probably a "good thing" to allow users with physical access to reboot/shutdown a desktop/laptop system. It is probably not a preferred solution for a multi-user/server system. One user group can say to the other "go an change the default policy", or the installer can pick the "the right thing to do" based on the installation profile... Regards, Menelaos Maglis
[toc] | [prev] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2017-12-08 13:40 +0100 |
| Message-ID | <uUq6B-40S-5@gated-at.bofh.it> |
| In reply to | #189668 |
On Fri, Dec 08, 2017 at 10:17:36AM +0100, Menelaos Maglis wrote: > > It is an improvement to have a consistent (central) way to configure > this behavior. > > It is probably a "good thing" to allow users with physical access to > reboot/shutdown a desktop/laptop system. > > It is probably not a preferred solution for a multi-user/server system. > It is a definitely a bad thing to silently change/break an existing configuration. That is really the problem that I have with this while issue that was brought up. I get that it is a "sensible" default to allow users on the console (TTY or via DM) permission to reboot the machine. However, when an admin has configured the system to disallow that sort of thing, it is frustrating to have a new thing come along and not respect the configuration. It is even more frustrating when the fact that the new thing ignores the configuration is not even documented where one would expect it (i.e., the Debian release notes in this case). Regards, -Roberto -- Roberto C. Sánchez
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2017-12-08 20:10 +0100 |
| Message-ID | <uUwc1-842-5@gated-at.bofh.it> |
| In reply to | #189671 |
Roberto C. Sánchez wrote: > That is really the problem that I have with this while issue that was > brought up. I get that it is a "sensible" default to allow users on the > console (TTY or via DM) permission to reboot the machine. However, when > an admin has configured the system to disallow that sort of thing, it is > frustrating to have a new thing come along and not respect the > configuration. It is even more frustrating when the fact that the new > thing ignores the configuration is not even documented where one would > expect it (i.e., the Debian release notes in this case). This is also my problem with systemd and the main reason to either deny it or use it with caution. This is also typical to some of the developers standing behind it. Which is one more reason regards
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2017-12-07 01:10 +0100 |
| Message-ID | <uTRVf-79B-11@gated-at.bofh.it> |
| In reply to | #189609 |
On Wed 06 Dec 2017 at 22:52:17 (+0100), Urs Thuermann wrote: > Yesterday, my 10 years old son logged into my laptop running Debian > jessie using his account, and curiously asked if he is allowed to try > the /sbin/reboot command. Knowing I have a Linux system as opposed to > some crappy Win machine, I replied "sure, go ahead and try". Seconds > later I was completely shocked when the machine actually rebooted... That's a lot of typing! I just type Ctrl-Alt-Backspace Ctrl-Alt-Del to reboot, or tap the power button to shut down. I've also noticed that I don't need to type any password to close the lid. Presumably your son has progressed beyond mischievously holding down the power button. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Eric S Fraga <e.fraga@ucl.ac.uk> |
|---|---|
| Date | 2017-12-07 08:30 +0100 |
| Message-ID | <uTYN4-33Y-11@gated-at.bofh.it> |
| In reply to | #189609 |
[Multipart message — attachments visible in raw view] — view raw
On Wednesday, 6 Dec 2017 at 22:52, Urs Thuermann wrote: > Yesterday, my 10 years old son logged into my laptop running Debian > jessie using his account, and curiously asked if he is allowed to try > the /sbin/reboot command. Security issues etc. aside, I love the fact that your 10 year old is asking such a question! -- Eric S Fraga via Emacs 27.0.50, org 9.1.4
[toc] | [prev] | [next] | [standalone]
| From | David Baron <dbaron770@gmail.com> |
|---|---|
| Date | 2017-12-07 08:50 +0100 |
| Message-ID | <uTZ6p-3bI-1@gated-at.bofh.it> |
| In reply to | #189609 |
On יום רביעי, 6 בדצמבר 2017 22:52:17 IST Urs Thuermann wrote: > Yesterday, my 10 years old son logged into my laptop running Debian > jessie using his account, and curiously asked if he is allowed to try > the /sbin/reboot command. Knowing I have a Linux system as opposed to > some crappy Win machine, I replied "sure, go ahead and try". Seconds > later I was completely shocked when the machine actually rebooted... > > Of course, my son doesn't have any special privileges, no entry in > /etc/sudoers, etc. But then I see > > $ ls -l /sbin/reboot > lrwxrwxrwx 1 root root 14 Apr 8 2017 /sbin/reboot -> /bin/systemctl > $ ls -l /bin/systemctl > -rwxr-xr-x 1 root root 538904 Apr 8 2017 /bin/systemctl > $ dpkg -S /bin/systemctl > systemd: /bin/systemctl > > The /bin/systemctl binary is not suid root, so I assume[1] it > communicates to systemd which then reboots the machine without > checking what user the request comes from. > > I wonder how can such a severe bug make it into a Debian stable > distribution? And is this just an insane default setting on Debian's > side or is it yet another instance of brain-dead systemd behavior? > > Searching the man pages I couldn't find a way to fix this. How can > that be stopped? > > [1] Of course, this is not docuemented in systemctl(1) as usual with > systemd. Also, according to the man page, systemctl must be > called with a "COMMAND" argument which /sbin/reboot doesn't do. > Obviously, systemctl looks at the name it was called and somehow > uses that as command. The admin shall guess about this. > > > urs I find I need to use "sudo" to shutdown or reboot. That is using those (pseudo?) commands. Maybe their scripts check before going to sysemctl
[toc] | [prev] | [standalone]
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
Back to top | Article view | linux.debian.user
csiph-web