DOCSLIB.ORG

The Pityfull State of Linux Desktop Security

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Pityfull State of Linux Desktop Security The Pityfull State of Linux Desktop Security Martin Gr¨aßlin QtCon 03. September 2016 Let's start with fun stuff: X11 default Keylogger on X11 Use XInput 2.1 or later Select for RawKeyPress and RawKeyRelease events Filter those through xkbcommon Delivers all events! Even if another X client grabbed input (e.g. locked the screen) The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin But keyloggers don't matter (to me)! default Some evil things keyloggers can do Get your password when screen is locked Get your password when using su/sudo/kdesu/kdesudo Get your bank account number and pin Get your facebook password Get your GPG passphrase Get your ssh-key passphrase The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin More fun stuff: inject key events default Hijack Dolphin running as root Demonstrated to Dolphin and Kate developers in January Opens embedded Konsole and starts typing in it see https://marc.info/?l=kfm-devel&m=145192452218315&w=2 Code at: git://anongit.kde.org/scratch/graesslin/exploit-dophin-root-x11.git How does it work? Notifications about windows of other applications Read information about windows of other applications (e.g. PID) Inject input events The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin What can applications do against that? default Never run as root! Graphical application shall not run as root Add checks for root and terminate Don't wait till Q(Gui)Application is constructed, you might already be owned Don't show a graphical warning that it's not allowed to run as root, that's too late Delegate to KAuth if a task needs to be performed as root But FREEDOM! Users have to be able to shoot themselves in the foot and edit /etc/fstab in Kate running as root! The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin There are more problems on X, aren't there? default Xcomposite and Damage extensions Screenshot in the simple way Get a notification whenever a window changes content Get the XPixmap for free Take over rendering and replace X rendering You just explained the basics of X11 compositing... Allows recording everything you do in every application Can render the desktop in different ways, e.g. remove a window The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Let's combine to make real fun stuff default Phishing Get screenshot of browser Put a window exactly above the address bar Use XTest extension to send broser to http://evilbank.com Render to fake address bar window that user is on https://bank.com The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Wayland will fix it default The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Nope, sorry it won't default The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Wayland does fix some aspects default Sane protocol No information about other applications No window properties at all No way to inject input events No way to screenshot No way to position windows manually No way to eavesdrop on input events Clipboard not broadcasted The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin So it's also fixed with KWin/Wayland? default KWin adds additional protocols which break it Injecting input events possible for kdeconnect Information about windows exposed to Plasma Protocoll to allow windows to position themselves The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin We can fix those protocols default Introduce a security layer Ideas are floating around for quite some time There is Wayland Security Model Authentication protocol suggestion Authorize based on pid, uid, gid, etc. But only moves the trust issue around How to trust the Plasmoid which accesses window information? But it won't fix the root problem The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin The Linux security mantra default If it runs, it is trusted! The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin How did we get here? default X11 is too broken Once a client is connected to Xserver it had to be trusted Examples No point in securing lock screen if another client can just disable the lock screen No point in protecting against keylogger if X allows key logging The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin We concentrated on the wrong areas default Prevent malicious application to get into system in first place Prevent malicious application to become root The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Beeing root is not what matters today default The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin And what about getting malware into the system? default We as a community don't take security serious \Beware of hacked ISOs if you downloaded Linux Mint on February 20th!" \Manjaro forgot to upgrade their SSL certificate, suggest users get around it by changing their system clocks" \We regularly receive bug reports from users with very old versions of WebKit, who trust their distributors to handle security for them and might not even realize they are running ancient, unsafe versions of WebKit." \Therefore, browsers built upon the webkit, qtwebkit and khtml engines are included in Jessie, but not covered by security support. These browsers should not be used against untrusted websites." The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Let's look at us! default QtWebEngine 5.7 based on Chromium 49 with security backports up to 51 No update since then What about the 48 security issues fixed in Chromium 52.0.2743.82? And where can I see which issues are valid for QtWebEngine? Other engines QtWebKit still used Khtml still used The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Can we trust our software? default Our distributed software? Not all git tags are signed Not all tar balls are signed Info page on download.kde.org is not using https Software at runtime? KPackages are not signed KPackages are loaded without integrity check Local overwriting of desktop files possible Local overwriting of KPackages possible The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin How to exploit? default Write access to home directory is sufficient Drive-by download vulnerability in browser Or any other application exposed to the internet Best targets $HOME/.profile $HOME/.bashrc $HOME/.config/autostart $HOME/.pam environment The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin LD PRELOAD and friends default Startup process Shell scripts are sourced Env variables are set for all processes Allows to load custom binary data into all or dedicated processes Process have no idea that they are tampered with Session might be owned before the first Plasma script/binary is executed The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin What can one do if one is running in the session? default Some examples Install a key logger into KWin/Wayland (example code on git.kde.org) Replace polkit-kde-authentication-agent and wait for the user to enter password ptrace applications to get their secrets Eavesdrop on DBus The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin How to fix this mess? default The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Linux Kernel can help us to fix that! default Linux security modules and syscall filtering AppArmor SELinux libseccomp Taime your application Disallow write access, if it doesn't need it Disallow network access, if it doesn't need it Use AppArmor to restrict the DBus calls your app is allowed to do The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Disallow ptrace default Where we added it KWin (Wayland) Polkit-kde-authentication-agent Lock screen kcheckpass kdesu(do) Many distributions do that by default We should not wait for distros to fix that! The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Change startup default Prevent env variable hacks! Distros need to stop sourcing $HOME/.pam environment Login managers need to stop sourcing bashrc and friends No sourcing of env variables before session starts At least get the session started in secure way Yes, I know that this will break our dev workflows. The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Containers to the rescue! default Flatpaks and Snaps a solution? Don't allow writing to home E.g. filesystem portal Limit access to DBus Libertine: One X server per X application The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Bringing back the trust! default If it runs, it's trusted for real New session startup without sourcing env scripts Signing of KPackage (plasmoids, kwin scripts, etc.) Security relevant interfaces (e.g. taskmanager) only available for signed packages All user applications running in sandboxes Remember: sandbox is no excuse to not add security to other areas! The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Authenticate our apps to the user default The lock screen problem Is it the lock screen? or a random fullscreen application looking like the lock screen? Authenticate password prompts to user A shared secret between user and password prompt Dedicated key combo for password prompts (c.f. ctrl+alt+del) User Account Control The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin Better password asking experience default Problems with password dialogs Application does not set ptrace protection Windowing system does not know it's asking for password Focus stealing is possible window stacking order attacks possible Password asking service Plasma provides password dialog Application requests a password Service provides password back The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin A Mission! default Wayland gives us the possibility to have a secure desktop, let's do it! The Pityfull State of Linux Desktop Security | Martin Gr¨aßlin.
Load more

Recommended publications
  • Ultumix GNU/Linux 0.0.1.7 32 Bit!
    Welcome to Ultumix GNU/Linux 0.0.1.7 32 Bit! What is Ultumix GNU/Linux 0.0.1.7? Ultumix GNU/Linux 0.0.1.7 is a full replacement for Microsoft©s Windows and Macintosh©s Mac OS for any Intel based PC. Of course we recommend you check the system requirements first to make sure your computer meets our standards. The 64 bit version of Ultumix GNU/Linux 0.0.1.7 works faster than the 32 bit version on a 64 bit PC however the 32 bit version has support for Frets On Fire and a few other 32 bit applications that won©t run on 64 bit. We have worked hard to make sure that you can justify using 64 bit without sacrificing too much compatibility. I would say that Ultumix GNU/Linux 0.0.1.7 64 bit is compatible with 99.9% of all the GNU/Linux applications out there that will work with Ultumix GNU/Linux 0.0.1.7 32 bit. Ultumix GNU/Linux 0.0.1.7 is based on Ubuntu 8.04 but includes KDE 3.5 as the default interface and has the Mac4Lin Gnome interface for Mac users. What is Different Than Windows and Mac? You see with Microsoft©s Windows OS you have to defragment your computer, use an anti-virus, and run chkdsk or a check disk manually or automatically once every 3 months in order to maintain a normal Microsoft Windows environment. With Macintosh©s Mac OS you don©t have to worry about fragmentation but you do have to worry about some viruses and you still should do a check disk on your system every once in a while or whatever is equivalent to that in Microsoft©s Windows OS.
    [Show full text]
  • Kde-Guide-De-Developpement.Web.Pdf
    KDE Published : 2017-06-26 License : GPLv2+ 1 KDE DU POINT DE VUE D'UN DÉVELOPPEUR 1. AVEZ-VOUS BESOIN DE CE LIVRE ? 2. LA PHILOSOPHIE DE KDE 3. COMMENT OBTENIR DE L'AIDE 2 1. AVEZ-VOUS BESOIN DE CE LIVRE ? Vous devriez lire ce livre si vous voulez développer pour KDE. Nous utilisons le terme développement très largement pour couvrir tout ce qui peut conduire à un changement dans le code source, ce qui inclut : Soumettre une correction de bogue Écrire une nouvelle application optimisée par la technologie KDE Contribuer à un projet existant Ajouter de la fonctionnalité aux bibliothèques de développement de KDE Dans ce livre, nous vous livrerons les bases dont vous avez besoin pour être un développeur productif. Nous décrirons les outils que vous devrez installer, montrer comment lire la documentation (et écrire la vôtre propre, une fois que vous aurez créé la nouvelle fonctionnalité !) et comment obtenir de l'aide par d'autres moyens. Nous vous présenterons la communauté KDE, qui est essentielle pour comprendre KDE parce que nous sommes un projet « open source », libre (gratuit). Les utilisateurs finaux du logiciel n'ont PAS besoin de ce livre ! Cependant, ils pourraient le trouver intéressant pour les aider à comprendre comment les logiciels complexes et riches en fonctionnalités qu'ils utilisent ont vu le jour. 3 2. LA PHILOSOPHIE DE KDE Le succès de KDE repose sur une vue globale, que nous avons trouvée à la fois pratique et motivante. Les éléments de cette philosophie de développement comprennent : L'utilisation des outils disponibles plutôt que de ré-inventer ceux existants : beaucoup des bases dont vous avez besoin pour travailler font déjà partie de KDE, comme les bibliothèques principales ou les « Kparts », et sont tout à fait au point.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Knowing Knoppix/Print Version - Wikibooks, Open Books for an Open World
    Knowing Knoppix/Print version - Wikibooks, open books for an open world Knowing Knoppix/Print version Knowing Knoppix The current, editable version of this book is available in Wikibooks, the open-content textbooks collection, at http://en.wikibooks.org/wiki/Knowing_Knoppix Permission is granted to copy, distribute, and/or modify this document under the terms of the Creative Commons Attribution-ShareAlike 3.0 License. Contents 1 Introducing Knoppix 1.1 Introducing Knoppix 1.1.1 What is Knoppix? 1.1.1.1 Linux that runs from CD 1.1.1.2 Can be installed on a Hard Disk or a USB key 1.1.1.3 How it works 1.1.1.4 Safe to run 1.1.1.5 Personal 1.1.1.6 Free 1.1.2 What you can do with Knoppix 1.1.2.1 Learn Linux 1.1.2.2 Rescue and test 1.1.2.3 Use and explore 1.1.2.4 Network 1.1.3 Where Knoppix comes from 1.1.4 Knoppix is Free Software 1.1.5 Limitations 1.1.5.1 No warranty 1.1.5.2 CD means slow 1.1.5.3 Not everything works 1 von 71 Knowing Knoppix/Print version - Wikibooks, open books for an open world 1.1.5.4 RAM intensive 1.1.6 What is included in Knoppix? 1.1.7 What is Linux? 1.1.7.1 A little history 1.1.7.1.1 How GNU grew 1.1.7.1.2 It's a GNU world! 2 Knoppix for the first time 2.1 Knoppix for the first time 2.1.1 Overview 2.1.2 Hardware requirements 2.1.3 Starting Knoppix 2.1.3.1 The first stage 2.1.3.2 The second stage 2.1.4 The first stage 2.1.4.1 Getting to the boot prompt 2.1.4.2 Help at the boot prompt 2.1.4.2.1 Quick help 2.1.5 The second stage 2.1.5.1 Starting Knoppix proper 2.1.5.2 Which keyboard/language? 2.1.5.3 Automatic hardware detection
    [Show full text]
  • Učebnice GNU/Linuxu -.:RDMS
    Učebnice GNU/Linuxu ze dne 29.5.2006 rozšířené vydání 1 Učebnice GNU/Linuxu Každý začátek je těžký a obtížný, zvláště nemáte-li po ruce někoho zkušenějšího, kdo by vám radil a předával své zkušenosti. Operační systém GNU/Linux je velmi rozsáhlý a má místy velmi odlišné ovládání například oproti MS Windows. Proto je lepší přečíst si o něm knihu, která by vám prozradila jeho taje a zákoutí. Pak proniknete do jeho filozofie, naučíte se ovládat svůj počítač skutečně efektivně a rozšíříte své obzory. Našim cílem je poskytnout vám základní informace, které vám usnadní pochopení GNU/Linuxu. Na trhu existuje spousta kvalitních knih na toto téma. V rubrice Recenze jich pár najdete, kompletní seznam je dostupný na linux.cz. Nicméně pokud teprve začínáte, nemusíte chtít investovat do koupě knihy, nemluvě o času stráveném na cestě do knihkupectví a zpět. Taková kniha přes své nesporné kvality může navíc časem zastarat nebo obsahovat chyby. Proto jsme se rozhodli usnadnit cestu ke GNU/Linuxu a připravili jsme tuto online učebnici Linuxu. Tuto učebnici napsali a spravují čtenáři portálu www.abclinuxu.cz a je dostupná pod licencí GNU Free documentation licence. Můžete si ji zdarma přečíst, stáhnout, vytisknout atd. Každý čtenář má možnost sám opravit text, chybu či překlep nebo doplnit čerstvé údaje. Nebojte se tuto možnost využít. Více o tomto projektu na jeho stránkách. Své názory nebo rady nám můžete sdělit v diskusním fóru. Jak nám můžete pomoci: • pište chybějící obsah nebo doplňte informace • opravujte překlepy a pravopisné chyby, sjednocujte sloh • doplňujte odkazy na zajímavé články a informace • umístěte na své stránky odkazy na učebnici Doufáme, že se vám bude učebnice líbit a že vám zpříjemní cestu k poznání GNU/Linuxu.
    [Show full text]
  • Anubis-Linux (V.2)
    Welcome to Anubis-Linux (v.2) – a programming/networking/security -oriented remastered version of SimplyMEPIS – A gentle introduction to Linux for (ex-)Windows® users. DISCLAIMER/LICENSE Anubis-Linux is a distribution based on SimplyMEPIS. Being a remaster means that MEPIS LLC doesn't support it and its development in any way. The original MEPIS License and documentation are preserved in docs.MEPIS.zip and info.MEPIS.zip for informational purposes. Anubis-Linux contains cryptographic software that is forbidden under U.S. law to be exported to and used in certain countries. Please inform yourself on the matters particular to the region where you live in. Anubis-Linux is provided AS-IS. No guarantees, and no warranties whatsoever (expressed or implied) are given regarding Anubis-Linux's correct functioning or fitness for a particular purpose. The authors of Anubis-Linux shall not be held liable in case of any kind of damage whatsoever (i.e. data loss) induced or caused by the use of Anubis-Linux. This is experimental software. You use Anubis- Linux at your own risk. By installing, running or otherwise using Anubis-Linux, you must understand, agree to and comply with the above terms. Otherwise do not use Anubis-Linux. The documentation and software in Anubis-Linux are freely redistributable but licensed varyingly. Please check their individual licenses for more information. All trademark/copyright rights are property of their respective owners. Linux is a registered trademark of Linus Torvalds. Debian is a registered trademark of Software in the Public Interest Inc. MEPIS and the MEPIS Logo are registered trademarks of MEPIS LLC.
    [Show full text]
  • 3D Accelerated Games, 305–08 3D Accelerated Video
    Index 3D accelerated games, Bookmark tab, 66 CDs 305–08 Boot diskettes, 29 burning, 274–81. See also 3D accelerated video cards Boot loaders, 18 K3b 3D support, testing for, Boot order, changing, 11 ripping, 271–74. See also 305 Boucher, Marc, 123 Grip acceleration, testing with Bricklin, Daniel, 203 storage capacity, 279 gears program, 305–06 Buddy lists, 139–40 Centered Maxpect, 81 Bugs, reporting, 182, 183 Channels, 178, 181 Abiword, 201 Bulwer-Lytton, Edward Charts and graphs Address books, 150–51 George, 185 labels, assigning rows and Administrative user (root) Burning CDs, 274–81. See columns as, 210 password, 28, 31, 34, 38 also K3b merging cells, 212 printer installations, 116 Burn-Proof technology, 279 moving and resizing, 212 software, installing and Bzip2 archive, 104 selecting and deselecting compiling, 94, 98 cells, 210 .alpha.rpm, 97 tabbed pages, placement AltaVista search engine, 163 Calc on, 210 AOL Instant Messenger, AutoPilot functions, types, previewing and se- 135, 136 206–07 lecting, 211 Application Starter, 49–50 averages, calculating, Click-N-Run service, 95 Arcade games, 294–97 205–07 Codecs, 285 Artists Guide to the GIMP cell range, specifying, 206 CodeWeavers, 19 (Hammel), 260 cells, sizing, 205 CodeWeavers CrossOver aRts driver, 266 charts, creating, 210–12. Plugin, 284 Atlantik, 300 See also Charts and Command line commands. Attachments, sending email, graphs See also Shells 152 closing and opening files, 3D support, testing for, aumix, 263 207 305 AutoPilot feature (Writer), fonts, changing, 205 the ampersand
    [Show full text]
  • Linux Newbie Administrator Guide.Pdf
    Linux Newbie Administrator Guide (LNAG) LINUX NEWBIE ADMINISTRATOR GUIDE ver. 0.193 2002−12−14 by Stan, Peter and Marie Klimas The latest version of this guide is available at http://sunsite.dk/linux−newbie. Copyright (c) by Peter and Stan Klimas. Your feedback, comments, corrections, and improvements are appreciated. Send them to [email protected] This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0, 8 or later http://opencontent.org/openpub/ with the modification noted in lnag_licence.html. Intro. We are relative Linux newbies (with Linux since Summer 1998). We run mostly RedHat and Mandrake −> the solutions might not be directly applicable to other Linux distributions (although most of them probably will be). Hope this helps; we try to be as practical as possible. Of course, we provide no warranty whatsoever. If you spotted a bad error or would like to contribute a part on a topic of your choice, we would like to hear from you. General description of this Guide. A complete reference for new Linux users who wish to set up and administer their own Linux home computer, workstation and/or their home or small office network. The answers are meant to be simple, with just sufficient detail, and always supported with a readily usable example. The work is still in progress, but we hope the Guide can be helpful already. We welcome your corrections, advice, criticism, links, translations, and CONTRIBUTIONS. Pls note that there are no ad banners on our pages. Conventions: <> = single special or function key on the keyboard.
    [Show full text]
  • KDE Stack Overview and How It All Fit Together High Level? Low Level? It’Ll Be Both My Friend!
    KDE Stack Overview and How It All Fit Together High Level? Low Level? It’ll be both my friend! Kevin Ottens Akademy 2021, June 18th whoami • Started to use KDE with 1.0-beta1 in 1997 • Procrastinated until 2003 to finally contribute code • Fell in love with the community back then • Kept doing things here and there. most notably helped with: – kdelibs – KDE Frameworks architecture – the KDE Manifesto – Community Data Analytics • Part of the enioka Haute Couture family • Living in Toulouse KDE Stack Overview and How It All Fit Together 2| Our Goals for Today • Increase our general knowledge of the “KDE Stack” – As such it will be mostly high level views – Don’t worry there will be a few code snippets though • Get a feel for how extensive it all is – Can’t be exhaustive though, would take days and be pointless – We’ll try to cover at least the most important/pervasive pieces • Develop an idea of the integration points between all those pieces – Obviously has an impact on what we decided to cover or not – Also means we’ll have to go with lower level topics from time to time • Disclaimer: Your head might spin, this is to be expected – It is a lot to absorb in one go – Ask questions along the way before you feel lost KDE Stack Overview and How It All Fit Together 3| Our Goals for Today • Increase our general knowledge of the “KDE Stack” – As such it will be mostly high level views – Don’t worry there will be a few code snippets though • Get a feel for how extensive it all is – Can’t be exhaustive though, would take days and be pointless – We’ll
    [Show full text]
  • PDF Herunterladen
    Siduction Handbuch siduction Team 2021-07-27 1 siduction Manual INHALTSVERZEICHNIS Inhaltsverzeichnis 1 Willkommen 10 1.0.1 Allgemeines ........................ 10 1.0.2 Copyright Rechts- und Lizenzhinweise ........... 11 1.0.3 Haftungsausschluss .................... 11 1.1 Das siduction-Team ....................... 12 1.1.1 Credit für siduction 2021.2.0 ................ 12 1.1.1.1 Core Team .................... 12 1.1.1.2 Art Team ..................... 12 1.1.1.3 Code Ideen Unterstützung Handbuch ....... 12 1.1.1.4 Credit für das original manual Team ....... 12 1.2 siduction Hilfe .......................... 14 1.2.1 Das siduction-Forum ................... 14 1.2.2 Das siduction-Wiki .................... 14 1.2.3 IRC - interaktiver Livesupport ............... 14 1.2.4 siduction-paste ...................... 15 1.2.5 Nützliche Helfer im Textmodus .............. 16 1.2.6 siduction IRC-Support im Textmodus ........... 17 1.2.7 Surfen im Internet im Textmodus ............. 19 1.2.8 inxi ............................ 19 1.2.9 Nützliche Links ...................... 20 2 Quickstart 21 2.1 siduction Kurzanleitung ...................... 21 2.1.1 Essenzielle Kapitel .................... 21 2.1.2 Zur Stabilität von Debian Sid ............... 22 2.1.3 Der siduction-Kernel ................... 22 2.1.4 Die Verwaltung von Softwarepaketen ........... 22 2.1.5 Aktualisierung des Systems - upgrade ........... 23 2.1.6 Konfiguration von Netzwerken ............... 24 2.1.7 Runlevels - Ziel-Unit .................... 25 2.1.8 Weitere Desktopumgebungen ............... 25 2.1.9 Hilfe im IRC und im Forum ................ 25 3 ISO s 26 3.1 Inhalt der Live-ISO ........................ 27 3.1.1 Hinweis zur Software auf dem Live-ISO .......... 27 2 siduction Manual INHALTSVERZEICHNIS 3.1.2 Varianten der ISO ....................
    [Show full text]
  • Inqlude How to Contribute About the Qt Library Archive Search
    a h lp Home A How to get libraries #inqlude How to contribute About The Qt library archive Search The goal of Inqlude is to provide a comprehensive listing of all existing libraries for developers of Qt applications. If you are creating applications using the Qt toolkit, and are looking for libraries, components or modules to use, Inqlude is the place where you find all information and pointers to get started. This is a young project, we are still collecting information, and are building up the web site and the tools around it. If you would like to get involved, read more about how to contribute, or go to the mailing list inqlude.kde.org to directly talk to us. See you there. Stable libraries | Development versions | Unreleased | Commercial | All attica Open Collaboration Services API avahi-qt Qt4 Bindings for avahi, the D-BUS Service for Zeroconf and Bonjour baloo Baloo is a file indexing and searching framework bluez-qt Qt wrapper for BlueZ 5 DBus API cutereport Report solution diff-match-patch Diff, Match and Patch libraries for Plain Text echonest Qt library for communicating with The Echo Nest enginio-qt Enginio client library for Qt platfom. Provides both Qt C++ and QML APIs to client applications. exaro Report engine extra-cmake- Extensions for software using the CMake build system modules frameworkintegration Workspace and cross-framework integration plugins gcf Generic component framework glc-lib Library for high performance 3D applications based on OpenGL jreen XMPP client library kactivities Runtime and library to organize
    [Show full text]
  • Installing Linux Applications for the First Time
    Preparing Today for Linux Tomorrow Installing Linux Applications for the First Time A Linux White Paper Abstract Although I have used and supported operating systems for many years (since before the IBM PC, in fact), when I began this project Linux was brand new to me. So it was with a mixture of eagerness and trepidation that I approached my assignment: Install Linux® and write about my experiences. (A companion paper, available from the same sources as this one, discusses installing the operating system itself.) At first it sounded simple. After all, I have installed every version of DOS, Microsoft® Windows® and IBM® OS/2® that has ever existed up to this point (including quite a few beta versions along the way). However, they all have many things in common, thus simplifying the learning process: command names, directory structures, file and directory naming conventions and so on. Once the operating system is up and running, the next step is to find and install applications for it. That is the subject of this paper: Where to find Linux applications and how to go about downloading and installing them. For someone new to Linux, this is not as simple as it may sound. Note: There probably are many terms used in this paper that are unfamiliar if you are new to Linux. You may find the white paper called A Brief Linux Glossary for Windows Users, available from the same sources as this paper, to be a useful reference. 1 Preparing Today for Linux Tomorrow Contents Abstract .................................................................................................................................................. 1 Introduction ............................................................................................................................................ 3 Where Are They Hiding All Those Linux Applications?....................................................................
    [Show full text]