Re: [arch-general] Problem with cups 1.71 when restart service
Am 04.02.2014 13:31, schrieb Jelle van der Waa: > On 02/04/14 at 12:55pm, Maykel Franco wrote: >> Hi, I have problem with cups in arch. This is the log error_log the cups: >> >> >> E [04/Feb/2014:12:52:24 +0100] Unable to bind socket for address >> [v1.::1]:631 - Address already in use. >> E [04/Feb/2014:12:52:24 +0100] Unable to bind socket for address >> 127.0.0.1:631 - Address already in use. >> >> >> And the printing not works... >> >> Thanks in advanced. > > Does this happen when you start cups, can you navigate to > http://localhost:631 and will that display cups web ui? > Or is some other service running on 631? > To find a process listening on 631, try: # netstat -tnlp Cheers, ushi
Re: [arch-general] Problem with cups 1.71 when restart service
Am 04.02.2014 13:47, schrieb Maykel Franco:
> 2014-02-04 ushi :
>
>> Am 04.02.2014 13:31, schrieb Jelle van der Waa:
>>> On 02/04/14 at 12:55pm, Maykel Franco wrote:
>>>> Hi, I have problem with cups in arch. This is the log error_log the
>> cups:
>>>>
>>>>
>>>> E [04/Feb/2014:12:52:24 +0100] Unable to bind socket for address
>>>> [v1.::1]:631 - Address already in use.
>>>> E [04/Feb/2014:12:52:24 +0100] Unable to bind socket for address
>>>> 127.0.0.1:631 - Address already in use.
>>>>
>>>>
>>>> And the printing not works...
>>>>
>>>> Thanks in advanced.
>>>
>>> Does this happen when you start cups, can you navigate to
>>> http://localhost:631 and will that display cups web ui?
>>> Or is some other service running on 631?
>>>
>>
>> To find a process listening on 631, try:
>>
>> # netstat -tnlp
>>
>> Cheers, ushi
>>
>
>
> I can access http://localhost:631 works very well, but the error persist
> when restart cups service.
>
> maykel-arch /etc/cups # sudo ss -lpn|grep 631
> tcpLISTEN 0 128 :::631 :::*
> users:(("cupsd",8761,4),("systemd",1,31))
>
> Also, the print not printer...When add print:
>
> E [04/Feb/2014:12:43:22 +0100] Unable to bind socket for address
> [v1.::1]:631 - Address already in use.
> E [04/Feb/2014:12:43:22 +0100] Unable to bind socket for address
> 127.0.0.1:631 - Address already in use.
> W [04/Feb/2014:12:44:24 +0100] [CGI] Missing Product in
> /usr/share/cups/model/CNCUPSIRADV4051ZK.ppd!
> W [04/Feb/2014:12:44:24 +0100] [CGI] Missing Product in
> /usr/share/ppd/CNCUPSIRADV4051ZK.ppd!
>
> Thanks in advanced.
>
It seems that cups is running fine. Check it with
% systemctl status cups.service
Do you have the correct printer driver on your system?
Re: [arch-general] Systemd email notifications
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 13.02.2014 13:04, schrieb Paul Gideon Dann:
> Hello all,
>
> Does anyone know of any standard system for receiving notifications
> from systemd for unit state changes? I currently use Monit for the
> monitoring of many processes, and it'll e-mail me when things
> happen (e.g. a process was restarted). Since switching to systemd,
> it's felt a bit silly that for several processes, I'm having Monit
> monitor them simply because systemd is unable to tell me it
> restarted a unit. Monit isn't actually required to keep those
> processes alive as it once was, because systemd can do that.
>
> Paul
>
Hey Paul,
Check out OnFailure=
[Unit]
Description="HTTP Service"
OnFailure=mail-root@http.service
...
The mail-root@.service is a generic oneshot service that mails you
some stuff.
[Unit]
Description="Mailer"
[Service]
Type=oneshot
ExecStart=/path/to/my/mail-script %i
[Install]
WantedBy=multi-user.target
And your mail-script is somthing like...
#!/usr/bin/env sh
systemctl status "${1}.service" | \
mail -s "Failed Service: ${1}" ad...@example.com
See:
http://www.freedesktop.org/software/systemd/man/systemd.unit.html#OnFailure=
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJS/MbgAAoJEAAoDO4PlX3giMIQAL0sjwOpJ/QRYA0+stZQXONs
GPAvF75G0oxKV8D0vv6Ywr0UBq+OeuXYUWYoH4Iv+O9sKEKs3Jml8ecalLTogvr/
cx8Ux+ICdMN2O8WrLfb38Ui/Vo4I/O0te2oxlTzA1/TcFfYnyFfAoMm5JYsxAUva
aXHUJwOVVDCcaQFUHG17nzh3iKLzCGbKkVvzfcvjsWVzapbRbdnKRoOOnVfsyA6U
BO5sgLbyJ/zIFCQYxS0380YBQfG34u5wISMjBOcfTCLBubB3yemScmO8OJKIRjGM
hiKyWUtfTZrY5KQfhdN3+UcvdLU8ilv938/aI2bD1JGEvX1fWS4STsajwgKq/PoS
p1O5OHCipvNrfrkzBOKMVDYpYMWpz1OI36wD0wHqp6VcYHVDDcDkayjq0avCcEyO
6p5vDt7z3avvsyvrRYgPlMZF/Jc+pd6UeoFWahtIUbvJJlbX4wK8cZFun2QJmUL0
49ZQdNYpekNNXe9cJn6FcXMVcATPk2xhqBn2PDECQE5B1ATmzsOZ+aEyPiWemxhX
snZT1dLEZmJBFC9xg/5m1BBs0mmCY+ermpFZJniMrwFiSR9uIaastNPARfPIVUvp
rZ0r/JTPVZ0x8wMF9QXbS90zjcQ2O+bMae2BojiYEE9CdPNnacE2W0VK2uzGBWz8
/evt18eKs28cWufnC6F4
=1w4X
-END PGP SIGNATURE-
Re: [arch-general] Systemd email notifications
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 13.02.2014 16:11, schrieb Thomas Bächler: > Am 13.02.2014 16:05, schrieb Rodrigo Rivas: >> Ok... I'll take the chance to practice my DBus abilities... It is >> a bit long, but it kind of works. Just replace the print() call >> with your favourite sendmail function and you'll get a >> notification every time any of the units specified in the command >> line changes status. > > This isn't too long and it actually seems to work fine. > > I guess what Paul actually wants is a system where you would > subscribe to all services, not just some of them. This should be > possible as well with the API. > > This works pretty good. It shouldn't be that hard to monitor all units using ListUnits(). http://www.freedesktop.org/wiki/Software/systemd/dbus/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJS/OMhAAoJEAAoDO4PlX3grQAP/0TI/WjvFPmkkx7PvqRQ2Va4 Mz7hgLAfETjsB9SVZfSry/lpZ8xTrMJjYubtIAoyqvHx+nWowTAOz6toqNMOKSy/ bTTyzno1FUJ5C1NMzqcewFDEnDQuYuaK1V41Ff6qQ/HpybJNZq5wYe4mm4ATBU8U TQ7S57tg54VjsQ3QgoloWusAEw21AAtNUzqnDWS9iA2TRipk5eHoIVxRBI6ao2rZ GnNpori9Rl7Fn18qVtkA4HRc9FQg0e3DLB5YYRwvT4Z8zRhTQegujUZw4lbivvKL 1mTVqTtv/RVrt3GAft9/gqn9JhzSD0ucU+/2UciHUmKuYW3Ek1CV7bsmj8s3zggx sGt7IRTh5Ds5XKJF3fQHKkmLZKiUTBlh0hVouyCPdDbkY9HgG01MEO1HhOn4+9YV v/b2T/xLBFvgSycGwuU6yZBdqfOb6LqSSWhgTm/tqO4XqH5EuXskivSt/gGTPVmv HdVcGxeVFqUmCi0WDEdnAOlNMU5O5KxwPKEBhO4V8DjOOTvHjoIsg5CQMkrY7RNC ACEx/ZFXKPyQhksDeCOGPJ1WLDUj+EeVsew2EHCv29ilQQltgJvqk1l1zI5MD4qj +2suxy+2Nuxalgv0XoXTkFLJfqs7ee3f9EN3j6FIqOjcjv4o90xUAsEHJT1a4wEN 12sQQBTpFdjCUydCHGfD =9EOv -END PGP SIGNATURE-
Re: [arch-general] error: GPGME error: Invalid crypto engine
Am 04.04.2014 12:00, schrieb Carsten Mattner: > On Fri, Apr 4, 2014 at 11:52 AM, Thomas Bächler wrote: >> Am 04.04.2014 11:40, schrieb Carsten Mattner: >>> Same problem if I try to downgrade readline and bash >>> >>> :: File /var/cache/pacman/pkg/readline-6.3-3-x86_64.pkg.tar.xz is >>> corrupted (invalid or corrupted package (PGP signature)). >>> Do you want to delete it? [Y/n] n >>> error: bash: missing required signature >>> :: File /var/cache/pacman/pkg/bash-4.3-3-x86_64.pkg.tar.xz is >>> corrupted (invalid or corrupted package (PGP signature)). >> >> Use pacman -U to downgrade readline+bash from your cache (this skips >> signature verification by default). You may even have to log out and in >> again. >> >> If you are paranoid, verify both packages with pacman-key -v before >> installing them (I think that one should still work, as opposed to >> pacman+gpgme). > > pacman-key -v bash-4.3-3-x86_64.pkg.tar.xz > ==> Checking bash-4.3-3-x86_64.pkg.tar.xz ... > gpg: symbol lookup error: /usr/lib/libreadline.so.6: undefined symbol: UP > ==> ERROR: The signature identified by bash-4.3-3-x86_64.pkg.tar.xz > could not be verified. > > sha256sum bash-4.3-3-x86_64.pkg.tar.xz > c02d4486ffd345b83868afa5f8ff61ac720e96559ac1b8bb84051625401364c0 > sha256sum readline-6.3-3-x86_64.pkg.tar.xz > fc31861827cc94578ae69158312e605d2ffb26f1658e47406659f75f2bcc7196 > > Wouldn't it be great if I could check the file checksum of bash at > https://www.archlinux.org/packages/core/x86_64/bash/? > > Can you at least confirm the checksums to be the same on your machine? > Looks good to me: sha256sum /var/cache/pacman/pkg/bash-4.3-3-x86_64.pkg.tar.xz c02d4486ffd345b83868afa5f8ff61ac720e96559ac1b8bb84051625401364c0 sha256sum /var/cache/pacman/pkg/readline-6.3-3-x86_64.pkg.tar.xz fc31861827cc94578ae69158312e605d2ffb26f1658e47406659f75f2bcc7196 Cheers, ushi
Re: [arch-general] Why is it dangerous to run makepkg as root?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 17.05.2014 14:40, schrieb Roland Tapken: > Hi, > > I'm using arch for about half a year on a few systems, but every > time I install something from aur I'm asking myself one question: > > Why is it considered dangerous to run makepkg as root? > > My first guess was that the PKGBUILD usually comes from an > untrusted source and may contain code to attack my system (copy > personal data or install a rootkit or something like that). But on > the other hand, this file tells makepkg how to build the package > that will be installed as root, so if the author of the PKGBUILD > has bad purposes he will just put that code into the created > package. > > The second idea is that this advice should prevent the script from > *accidentally* damage my system. But this could be prevented by > using fakeroot (which is disabled when calling makepkg with > --asroot according to the manpage) or chroot. And actually the > proper advice in this case should be to execute makepkg using a > user dedicated for this, as for most arch users it would be worse > if their personal file get deleted as if the system becomes > unbootable. > > Regards, > > Roland > Hey Roland, there is a general security principle called "Principle of least privilege", which roughly says, that one should give a user/process/... only the minimum of privileges it neads to accomplish its tasks. makepkg does not need root privileges to build packages, so do not give those to it. makepkg does a lot of crazy things - downloading stuff, excuting scripts and complex programs (compilers, ...) - a single bug in one of those can render your system unusable, when executed as root. I think your idea of a dedicated user is great and would implement the principle mentioned above even better. [0] https://en.wikipedia.org/wiki/Principle_of_least_privilege Cheers, ushi -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTd13uAAoJEAAoDO4PlX3gjLMP/iR+JhKPygx49kFTNktgEbt7 r97BJcHUgPnglRl+w7LjHOJYSYRuNt7FclDK5l4iK0Kog0yrBqohL2wVsIa/ehTF jm/npxpjD0RWtr8nKSTyujlB/deVCV+TiHao+NiRbDFhkORhx8R7ohAw3pgwG8j6 vXkWpZ3NbOxx7G76xXd9YF9dqCFEddIFZ2gFgXaOgaRuMWAe5SdpW1fvpyRcv37v QJdbnzlQoafkTCZKF98inuf2lJKTYBHfaOZJsh3Q5KUS1a6a/qBIvqNQdWNPu1la FtBwwEQ3ku5XeldLi2D0wH4ZRsSBsqCxjXqav/PDyxUDBiTmfBllAToq6o4mGsCM zPCc/P7JvLMNIwMSxf6rXg8lEEIUP867Srx91hY5hdQeINfS1BoX67vq+5FuI5+Q voBfwxl+nSVPdeYydg12xsF91LNW1gUgSd6nVDHcOZX1gPxjZvA3Qin6EYf50pP7 8qVuxzp8qboxmsECKRZgMaAzenGBK482hGjPIkhgQ/n+uU46tGOHlmY1E4QstCoo rzovvzelN0bRdphsClYGmoT4gm/Axbnbhti4WkXYjVjfz8RK6yujV5b3VIdkoPM5 QWJdrbW5wb2Mm2Rvi9UUSqXy6LvK89d0ue2Nu/P4WubbUhq4ZcfKii2UeqJH5fk3 ahUmNW9MEiYJcGXpEoxH =pbJr -END PGP SIGNATURE-
Re: [arch-general] Why is it dangerous to run makepkg as root?
Am 17.05.2014 22:08, schrieb Bardur Arantsson: > On 2014-05-17 21:50, Roland Tapken wrote: >> Hi Bardur, >> >>> Maybe I've missed something reading through this thread, but *assuming* >>> (yeah, I know) that packages can't run arbitrary scripts at install time >>> (which I think is a valid assumption for pacman), >> >> Is this so? I don't know since I've only scratched the surface of arch until >> now. But I'm not quite sure about this, since, for example, there must be a >> way to add new users like http after installing apache. How should this be >> done without a post-install-script? > > I always thought that "this package needs users X,Y and Z" was handled > via some metadata in the package description, not via scripts per se. > Maybe I'm wrong on that too. Such things are handled via install scripts[0], called by pacman when (un)installing/upgrading packages... and yes, packagers can put arbitrary code in there. (postfix exmaple[1]) >> >>> Of course an attacker can still (via the build executables) delete all >>> the files you actually care about ($HOME) or install trojans into your >>> $HOME/bin (etc.), but still... If you discover such a comprosmise you'd >>> "only" have to delete your $HOME and restore from backup[0], whereas a >>> root compromise would require a full reinstall of everything. >> >> Even if your assumption about pacman is correct: Just let the malicious >> PKGBUILD write a file into /etc/cron.d/, /etc/systemd or something like that >> and you're doomed. No need for privilege escalation. >> > > Ah, yes. True, of course. I knew I'd missed something! :) > > Regards, > > [0] https://wiki.archlinux.org/index.php/PKGBUILD#install [1] https://projects.archlinux.org/svntogit/packages.git/tree/trunk/install?h=packages/postfix Cheers
[arch-general] libgit2 v0.21.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey list, can somebody explain, why libgit2-0.21.0-1 was replaced by libgit2-1:0.20.0-1? I already patched my projects to work with v0.21.0. What was the reason and when can i expect to get v0.21.0 again? Cheers, ushi -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJTpWVuAAoJEAAoDO4PlX3goZcP/iYo5023mG8+QAcpQ4hdY6Te IvbGS1OLeFeB9K7G3OhFS0kuRqSLVZ5AwoDOp+MlfRbcDzNVhpQ1Iz+2NsY1JEL1 yaLjpIYgT7KVgOkojkMHk0xJfISnFTA+v4igPzVEBOyBRAdwnxUikyps75cLvrP4 iKQ/7ybCQXlfibj7+dtn1FHg4C2LQ8TgnzW8fMZ3jWTuBfawxTwKYCCRZYnIdAaL 2VcLxih2cvaihwHTQJTF1V9XtLeT7Yc0HlacIGmRTrQKLTwwKQjY9wnQbx+ZD2Jb PqYCdKMdXaqEjWjVZNw3gnTfrmZ6LxVZeUKi2TS04uLq+BKtoyh2bWXX5G6Z5Ivt 9d6ZuF0OZaswYuRzp5pHf4M4V4pEKPCoodTS6eNpz8qFu5M/v7Rv3/6Ab6AxsI5u f8so204RbwhhPnDalB4pm6cVOXaLhXHy+uPXLW8ajkbqTRxGBJSzQAv6jPOnd75L d7sAVH++OfAzxbz1/kj1bN15Ucq1BjrRtPLL2sqDPlwwJu1e3EaI/Cn5zPHez8qL X4C5QfT7ldYN501RntlEeP5qIZ6eEGL2wJymb9qIPUlkUVp9Vh6IvacpoGbSpwZQ HMENinzTItIRZC/K2IZvPHcGFbPx0jKdIj43hzy9ieHBh62dNcP8mKa5ovLXUKu8 2aBFHYDQ57Z3UI7+ESI4 =voM5 -END PGP SIGNATURE-
Re: [arch-general] libgit2 v0.21.0
Am 21.06.2014 13:32, schrieb Karol Blazewicz: > On Sat, Jun 21, 2014 at 12:58 PM, ushi wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hey list, >> >> can somebody explain, why libgit2-0.21.0-1 was replaced by >> libgit2-1:0.20.0-1? >> > > See > https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/libgit2&id=8056a567f5806c0993b32320e5f00aff499c6b3c > >> I already patched my projects to work with v0.21.0. What was the >> reason and when can i expect to get v0.21.0 again? > > v21 is back already: > https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packages/libgit2&id=837b70d680873904f8530b7f48b20c74e0459adb > Thank you very much.
Re: [arch-general] gnome videos 3.12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 24.06.2014 00:53, schrieb Mark Lee: > On 06/23/2014 01:14 PM, Rasmus wrote: >> Eduardo Machado writes: > >>> Hi, >>> >>> after the last upgrade of gnome (including it's video >>> software), this video app has no menu. When i click on the >>> configurations button it does not show the menu for the >>> configurations. >>> >>> Anyone with the same problem or now how to work around? > >> Assuming you are using Gnome-Shell you can click the Videos-icon >> on the top-bar. There's a Preference-item. > >> AFAIK, the Gnomish3 way of accessing global preferences is this >> one. > >> Cheers, Rasmus > > > Did you try pressing the upper left hand corner icon? > > Regards, Mark > I had a similar problem and discovered that my (gtk- or shell-)theme was outdated. Update your themes or try it with the default gnome theme. Cheers, ushi -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJTqSqfAAoJEAAoDO4PlX3gp80P/ioQ9CHtU5gdSEZvSRAkesau XbQ5An23TCOPkRKLhP2gmX+3Yf71RUPVjwrazaQxNCMmaUmz95xYvliFiW0n1Xx2 9gMUxLWpfPr4aD8hAKW53vqjMeZb6PVj64vvJ3C2G41PwGIDItnfbGO6yhueay8g U7Mqj1avSjjKPB+Wj57/MKBq1Gny5C36L9w/P0wamjNpvxIO5JAUrtb5pDc2/FWe VL9KUYeSnQ1RE+ne74RBSZRCct2EaiLEQ2Y1XaXBw8r1+NyoHrLbZwwLc+ELAHS9 OYiMwe9lDcV1P3rIuMFl0ZVyyLRCZHxMWfpwm2QwD7TqLOyoWUxMGabcdQvbgq1X q+6ICKDN7tyWZG2sMaQy3HUBO/V9xiCI6fHeUYeHlHZMiorliom0xPBoT/XpoTTy mNgrPayJpAdNyJfBhVc0O10+CojCGQRzenRIbw/kso5VCgOK6RvPxfHqffySlYrE lGqSRv3vzrTCI8xEh9qUy+eM9S4MtHe7FVSSUniLvR1TBKqopaDKwU4ZtVF8Z3/P Ed6mfMReKx/h0xo+C6EV0vTZd6PBI8rnrsVRgy2n76OaD4AB/meX6A0qGhYjzJ3r uj6b9+p0kAs3ph3cQJKVXl5NlQkBNu87wk3/fjn0yGrAyQCdNJ1ybc+5iK0LQwq4 ceuNCdKX+lvIR5qau2nk =kEjV -END PGP SIGNATURE-
Re: [arch-general] svntogit 500/missing branches
Am 31.03.2013 10:21, schrieb Chris Down: > Sorry, missed the error message: > > Premature end of script headers: cgit.cgi > > > On 31 March 2013 16:15, Chris Down wrote: > >> Is it just me, or is svntogit returning 500 frequently? When it does >> return a real page from cgit (which seems to be about 50% of the time), it >> is missing lots of branches and generally just displays nothing if you're >> looking at, say, the log for linux-lts (what I first was looking for when I >> encountered this). >> >> Sorry if this was already posted elsewhere, I didn't see it on -dev-public >> or -general. >> There is an open bug report in Flyspray: https://bugs.archlinux.org/task/34467
Re: [arch-general] The "new" opensmtpd package
Am 17.04.2013 13:28, schrieb Hugo Osvaldo Barrera: > Hi, > > All of a sudden, this morning, after running pacman -Syu, I found myself > incapable of sending emails from several of my machines. > I had noticed not warnings, or errors, and, after tracking the issue > for a while, it turns out the problem was the new opensmtpd package in > [community], which had replaced my own one (present in AUR). > > I've been maintaining an opensmtpd package in AUR for a long time now > (it was recently renamed to "opensmtpd", but I had maintaing it under the > previous name since it's early development, which I follow very closely). > > One of the problems with the new package in [community], is that it's > build configuration differs SO MUCH from the defaults (and my own > package), that their settings are incompatible. I belive this goes > against the Arch way, which is to stay as close as possible to upstream. > > Also, the one in [community] has explicit flags that actually reduce > security (for what reason, I wonder?). > > At first, I though I'd contact the author, but I couldn't find out > how. The PKGBUILD does not include the maintainer's email, and he's not > listed as a TU or Dev. > > Finally, I'm a bit surprised as to how this happened. I planned to > propose to move my own package from AUR to [community] at some point, > but not yet, since it only has 7 votes (way less than what the wiki > describes neccesary). Secondly, I'm confused as to how this is done. If > there's a package in AUR, isn't that moved into [community] instead of > writing a brand new one? > > Please don't take this as a rant of "You broke my email setup!", > but rather as a "Hey, this isn't very transpart to the community; how > do these thing happen? How do I contact the maintainer? What was the > procedure to get this package into [community]? Is there any way I can > participate in it's maintenence?" > > Thanks, > Here is the email of the packager. % pacman -Si opensmtpd ... Packager: Sébastien Luttringer ... The output is broken when running with LC_ALL=C.
Re: [arch-general] [signoff] linux-3.8.11-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 02.05.2013 19:24, schrieb Tobias Powalowski: > Hi guys, please signoff 3.8.11 series for both arches. package is > not in testing, please grab it from here: > http://dev.archlinux.org/~tpowa/linux/ > > This will move to [core] directly, because 3.9.0 is in [testing]. > > greetings tpowa > signoff x64_86. No problems on my old lenovo 3000. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJRgxOUAAoJEAAoDO4PlX3gxzsQAKyjLH5Dd9y14n7GPjwm/UNG gsRgfRWXtTCvew9Ci0hok27WvhpJoz2JpkVOcXV6LbZENH4ulALGweKBq9yucjK5 b3QPj8mwy0Q2p3UC+ae7x3xkL4ZfodiKKd8zbeMa5TpU70yhtG9tXOZP3WGqBz8d KFsuGXCXdzmyHodO1wU4WIQgRzK3l717T91kSHuoudPomZIXaNaQn0mIW+K7nv61 DVYjECe0eTf41vnEI7gYO81SmKqyU8V3OoAVerWR+pJIHmvcNB7BBgjsvOIBTzi+ lEJUNzKJ6KD1P2AQ8vpEighxqJ4fwcg6+g6jKZ5vUWZG6ubJcqpphoanoVd02Fi7 8EoOqKuFpMDjS7amFJDlT10D5tCRW5Ji2GJVB2SO/57Xus1eEzRvp/ipR1OfF3UY RUhzDbJSx08myreumevNnW3r9ZUZES3tXk/XOh+wBO4vf+4bDCufdA+EjtiBJE2V EeoxVcWHUqG4CKHoqLT0PVSI9J6DYmK1taZMN2WQjcywmO2r5dx1gqs+/7mCqITi YyFHCUBZxg/KblMe5k9W51JpI779R3awKBT6AKjxHTl0BjpYLwct2E4tN9ju2mIF FBNeHL7FB29GPNO9Or0SxHYGDHQI6s4qIxfL3BAIUQpV+2LMvYM+T72IE/LV7I4X Mh4dHkmBcZpqxlSqRjA7 =6cPz -END PGP SIGNATURE-
