CUPS Plenary Joint PWG / Open Printing Summit - May 2021 Michael R Sweet (Lakeside Robotics) Before We Begin
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
A Practical UNIX Capability System
A Practical UNIX Capability System Adam Langley <[email protected]> 22nd June 2005 ii Abstract This report seeks to document the development of a capability security system based on a Linux kernel and to follow through the implications of such a system. After defining terms, several other capability systems are discussed and found to be excellent, but to have too high a barrier to entry. This motivates the development of the above system. The capability system decomposes traditionally monolithic applications into a number of communicating actors, each of which is a separate process. Actors may only communicate using the capabilities given to them and so the impact of a vulnerability in a given actor can be reasoned about. This design pattern is demonstrated to be advantageous in terms of security, comprehensibility and mod- ularity and with an acceptable performance penality. From this, following through a few of the further avenues which present themselves is the two hours traffic of our stage. Acknowledgments I would like to thank my supervisor, Dr Kelly, for all the time he has put into cajoling and persuading me that the rest of the world might have a trick or two worth learning. Also, I’d like to thank Bryce Wilcox-O’Hearn for introducing me to capabilities many years ago. Contents 1 Introduction 1 2 Terms 3 2.1 POSIX ‘Capabilities’ . 3 2.2 Password Capabilities . 4 3 Motivations 7 3.1 Ambient Authority . 7 3.2 Confused Deputy . 8 3.3 Pervasive Testing . 8 3.4 Clear Auditing of Vulnerabilities . 9 3.5 Easy Configurability . -
Beej's Guide to Unix IPC
Beej's Guide to Unix IPC Brian “Beej Jorgensen” Hall [email protected] Version 1.1.3 December 1, 2015 Copyright © 2015 Brian “Beej Jorgensen” Hall This guide is written in XML using the vim editor on a Slackware Linux box loaded with GNU tools. The cover “art” and diagrams are produced with Inkscape. The XML is converted into HTML and XSL-FO by custom Python scripts. The XSL-FO output is then munged by Apache FOP to produce PDF documents, using Liberation fonts. The toolchain is composed of 100% Free and Open Source Software. Unless otherwise mutually agreed by the parties in writing, the author offers the work as-is and makes no representations or warranties of any kind concerning the work, express, implied, statutory or otherwise, including, without limitation, warranties of title, merchantibility, fitness for a particular purpose, noninfringement, or the absence of latent or other defects, accuracy, or the presence of absence of errors, whether or not discoverable. Except to the extent required by applicable law, in no event will the author be liable to you on any legal theory for any special, incidental, consequential, punitive or exemplary damages arising out of the use of the work, even if the author has been advised of the possibility of such damages. This document is freely distributable under the terms of the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License. See the Copyright and Distribution section for details. Copyright © 2015 Brian “Beej Jorgensen” Hall Contents 1. Intro................................................................................................................................................................1 1.1. Audience 1 1.2. Platform and Compiler 1 1.3. -
Gutenprint 5.0 User's Manual and Release Notes
Gutenprint 5.0 User's Manual Robert Krawitz March 4, 2007 Gutenprint 5.0 User's Manual Copyright © 2000-2007 Robert Krawitz Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation with no invariant sections, no Front-Cover texts, and no Back-Cover texts. Gutenprint 5.0 is licensed in its entirety under the terms of the GNU General Public License. The CUPS code (in src/cups) is licensed under the terms of the GNU General Public License version 2; the balance of the code is licensed under the terms of the GNU General Public License version 2 or any later version published by the Free Software Foundation. EPSON, ESC/P, and Stylus are registered trademarks of Seiko Epson Corp. ESC/P2 is a trademark of Seiko Epson Corp. All other product names are trademarks and/or registered trademarks of their vendors. 2 Gutenprint 5.0 User's Manual 03/04/2007 Table of Contents 1) Introduction............................................................................................................................................5 1.1) What is Gutenprint?.......................................................................................................................5 1.2) History of Gutenprint.....................................................................................................................5 1.2.1) The early years: Gimp-Print 3.x and 4.0................................................................................5 -
Cups-Filters-Ippusbxd-2018.Pdf
cups-filters The non-Apple part of CUPS, maintained by OpenPrinting ippusbxd Standards-conforming support for IPP-over-USB printers Till Kamppeter, OpenPrinting Introduction • cups-filters takes up everything from CUPS which Mac OS X does not need (CUPS 1.6.x) Started end of 2011 by OpenPrinting, overtaking most of CUPS’ filters Switched filters over from PostScript-centric to PDF-centric workflow cups-browsed introduced end of 2012, to introduce browsing of DNS- SD-advertised remote CUPS queues, as CUPS dropped its own broadcasting/browsing • In 7 years of development cups-filters improved a lot Auto-create print queues for IPP network and IPP-over-USB printers, especially driverless printing, not competing with CUPS’ own temporary queues. Mobile printing support: No printer setup tool needed, auto-setup of printers, driverless, cups-browsed auto-shutdown Load-balanced printer clusters, with client-side or server-side queueing of jobs Do legacy CUPS broadcasting/browsing to work with old CUPS on remote machines Filters support Ghostscript, Poppler, and MuPDF as PDF interpreter Filters support all PDLs for driverless printing: PDF, Apple Raster, PWG Raster, and PCLm 2 Role of cups-browsed • CUPS auto-generates its own temporary queues to point to remote IPP/CUPS printers, why continue cups-browsed? Printer clustering (like the former Implicit Classes) . Configurable: Automatic (by equal remote queue names) and manual (by cups-browsed.conf) . Load balancing of clustered queues . Auto-selection of destination printer by job and job settings (planned) Fine-grained filtering of which remote printers are available . Not only servers/IP addresses, but also service names. -
Assistance with Self-Administered Medications 2 Contact Hours
Chapter 8: Assistance With Self-Administered Medications 2 Contact Hours Learning objectives Identify and interpret the components of a prescription label. Describe conditions that require additional clarification for “as List and explain the procedures for assistance with oral and topical needed” prescription orders. forms of medications (including ophthalmic, otic and nasal forms), Identify medication orders that require judgment, and may prevent including the “five rights” of medical administration. the CNA from assisting residents with medication. Identify and define the side effects for medication classes and Explain and list types of information and details that must be discuss procedures to follow if residents experience side effects or reported on the medication observation record. adverse reactions. List the requirements and procedures for medication storage and disposal. Introduction The Florida statutes (revised in 2016) are the laws that govern of the 2016 Florida Statutes. This means that some material assistance with self-medication. According to the state[1]: in the 2016 edition may not take effect until January 1, 2017. Legislative changes to the Florida Statutes, effective up to and Amendments effective on January 2, 2017, or later, will appear as including January 1, 2017, are treated as current for publication footnotes. Title XXX: Chapter 429: Social welfare assisted care communities 429.256 Assistance with self-administration of medication. c. Placing an oral dosage in the resident’s hand or placing the 1. For the purposes of this section, the term: dosage in another container and helping the resident by lifting a. “Informed consent” means advising the resident, or the the container to his or her mouth. -
Sockets in the Kernel
Linux Kernel Networking – advanced topics (6) Sockets in the kernel Rami Rosen [email protected] Haifux, August 2009 www.haifux.org All rights reserved. Linux Kernel Networking (6)- advanced topics ● Note: ● This lecture is a sequel to the following 5 lectures I gave in Haifux: 1) Linux Kernel Networking lecture – http://www.haifux.org/lectures/172/ – slides:http://www.haifux.org/lectures/172/netLec.pdf 2) Advanced Linux Kernel Networking - Neighboring Subsystem and IPSec lecture – http://www.haifux.org/lectures/180/ – slides:http://www.haifux.org/lectures/180/netLec2.pdf Linux Kernel Networking (6)- advanced topics 3) Advanced Linux Kernel Networking - IPv6 in the Linux Kernel lecture ● http://www.haifux.org/lectures/187/ – Slides: http://www.haifux.org/lectures/187/netLec3.pdf 4) Wireless in Linux http://www.haifux.org/lectures/206/ – Slides: http://www.haifux.org/lectures/206/wirelessLec.pdf 5) Sockets in the Linux Kernel ● http://www.haifux.org/lectures/217/ – Slides: http://www.haifux.org/lectures/217/netLec5.pdf Note ● Note: This is the second part of the “Sockets in the Linux Kernel” lecture which was given in Haifux in 27.7.09. You may find some background material for this lecture in its slides: ● http://www.haifux.org/lectures/217/netLec5.pdf TOC ● TOC: – RAW Sockets – UNIX Domain Sockets – Netlink sockets – SCTP sockets. – Appendices ● Note: All code examples in this lecture refer to the recent 2.6.30 version of the Linux kernel. RAW Sockets ● There are cases when there is no interface to create sockets of a certain protocol (ICMP protocol, NETLINK protocol) => use Raw sockets. -
CUPS on Freebsd
CUPS on FreeBSD Chess Griffin <[email protected]> Revision: b62d4babfd FreeBSD is a registered trademark of the FreeBSD Foundation. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the “™” or the “®” symbol. 2020-12-23 17:30:15 +0000 by Guangyuan Yang. Abstract An article about configuring CUPS on FreeBSD. Table of Contents 1. An Introduction to the Common Unix Printing System (CUPS) ........................................................... 1 2. Installing the CUPS Print Server .................................................................................................. 1 3. Configuring the CUPS Print Server .............................................................................................. 2 4. Configuring Printers on the CUPS Print Server ............................................................................... 2 5. Configuring CUPS Clients ........................................................................................................... 3 6. CUPS Troubleshooting .............................................................................................................. 3 Index ........................................................................................................................................ 5 1. An Introduction to the Common Unix Printing System (CUPS) CUPS, the -
Third-Party Licenses Ezeep
Licensing Terms of Additional Components Supplied by Third- Party Manufacturers “ezeep for Azure” ................................................................................................................................1 “ezeep Connector / ezeep Connector PS” ...........................................................................................1 “ezeep Connector Mac” .......................................................................................................................4 “ezeep print App macOS” ....................................................................................................................4 “ezeep for Azure” “ezeep Connector / ezeep Connector PS” “Microsoft Visual C++ 2013 Runtime Libraries”, “Microsoft Visual C++ 2017 Runtime Libraries” Appendix 1 Microsoft Visual C++ 2013 Runtime Libraries MICROSOFT SOFTWARE LICENSE TERMS MICROSOFT VISUAL C++ REDISTRIBUTABLE FOR VISUAL STUDIO 2013 These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft updates, supplements, Internet-based services, and support services for this software, unless other terms accompany those items. If so, those terms apply. BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE. IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE PERPETUAL RIGHTS BELOW. 1. INSTALLATION AND USE RIGHTS. You may install and use any number of copies of the software on your devices. 2. SCOPE OF LICENSE. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the soft- ware only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the soft- ware that only allow you to use it in certain ways. -
A Brief Technical Introduction
Mac OS X A Brief Technical Introduction Leon Towns-von Stauber, Occam's Razor LISA Hit the Ground Running, December 2005 http://www.occam.com/osx/ X Contents Opening Remarks..............................3 What is Mac OS X?.............................5 A New Kind of UNIX.........................12 A Diferent Kind of UNIX..................15 Resources........................................39 X Opening Remarks 3 This is a technical introduction to Mac OS X, mainly targeted to experienced UNIX users for whom OS X is at least relatively new This presentation covers primarily Mac OS X 10.4.3 (Darwin 8.3), aka Tiger X Legal Notices 4 This presentation Copyright © 2003-2005 Leon Towns-von Stauber. All rights reserved. Trademark notices Apple®, Mac®, Macintosh®, Mac OS®, Finder™, Quartz™, Cocoa®, Carbon®, AppleScript®, Bonjour™, Panther™, Tiger™, and other terms are trademarks of Apple Computer. See <http://www.apple.com/legal/ appletmlist.html>. NeXT®, NeXTstep®, OpenStep®, and NetInfo® are trademarks of NeXT Software. See <http://www.apple.com/legal/nexttmlist.html>. Other trademarks are the property of their respective owners. X What Is It? 5 Answers Ancestry Operating System Products The Structure of Mac OS X X What Is It? Answers 6 It's an elephant I mean, it's like the elephant in the Chinese/Indian parable of the blind men, perceived as diferent things depending on the approach X What Is It? Answers 7 Inheritor of the Mac OS legacy Evolved GUI, Carbon (from Mac Toolbox), AppleScript, QuickTime, etc. The latest version of NeXTstep Mach, Quartz (from Display PostScript), Cocoa (from OpenStep), NetInfo, apps (Mail, Terminal, TextEdit, Preview, Interface Builder, Project Builder, etc.), bundles, faxing from Print panel, NetBoot, etc. -
SATO CUPS Driver for Linux User Manual
SATO CUPS Driver for Linux User Manual Edition 2.26.0 March 2021 Software License Agreement PLEASE READ THE FOLLOWING TERMS AND 9. SATO Corporation warrants that for ninety (90) days CONDITIONS BEFORE USING THIS PRODUCT. BY after delivery, the Software will perform in accordance INSTALLING THE PRODUCT, YOU THEREBY INDICATE with specifications published by SATO Corporation, and YOUR ACCEPTANCE OF THESE TERMS AND that the distribution media will be free from defects in CONDITIONS. SHOULD YOU DISAGREE WITH ANY OF material and workmanship. SATO Corporation does not THE TERMS OR CONDITIONS LISTED BELOW, warrant that the Software is free from all bugs, errors PROMPTLY REMOVE ALL FILES RELATED TO THIS and omissions. PRODUCT FROM YOUR HOST PLATFORM AND RETURN 10. Your exclusive remedy and the sole liability of SATO THE PRODUCT TO SATO CORPORATION. Corporation in connection with the Software is 1. You explicitly agree to accept a non-exclusive license to replacement of defective distribution media upon their use the Software identified on the distribution media return to SATO Corporation. SATO Corporation will solely for your own customary business or personal not be liable for any loss or damage caused by delays purposes. Your local and national laws govern this in furnishing a Software Product or any other Agreement. performance under this Agreement. 2. Henceforth, “Software” shall refer to the digitally SATO Corporation does not warrant that the functions encoded, machine-readable data and program. The contained in the Software will meet your requirements or term “Software Product” includes the Software that the operation of the Software will be uninterrupted or identified on the distribution media, including any error-free. -
Software Engineering Session 7 – Main Theme Business Model
Software Engineering Session 7 – Main Theme Business Model Engineering Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda 11 IntroductionIntroduction 22 BusinessBusiness ModelModel RepresentationRepresentation 33 BusinessBusiness ProcessProcess ModelingModeling 44 CapturingCapturing thethe OrganizationOrganization andand LocationLocation AspectsAspects 55 DevelopingDeveloping aa ProcessProcess ModelModel 66 BPMN,BPMN, BPML,BPML, andand BPEL4WSBPEL4WS 77 BusinessBusiness ProcessProcess InteroperabilityInteroperability 88 SummarySummary andand ConclusionConclusion 2 What is the class about? Course description and syllabus: » http://www.nyu.edu/classes/jcf/g22.2440-001/ » http://www.cs.nyu.edu/courses/spring10/G22.2440-001/ Textbooks: » Software Engineering: A Practitioner’s Approach Roger S. Pressman McGraw-Hill Higher International ISBN-10: 0-0712-6782-4, ISBN-13: 978-00711267823, 7th Edition (04/09) » http://highered.mcgraw-hill.com/sites/0073375977/information_center_view0/ » http://highered.mcgraw- hill.com/sites/0073375977/information_center_view0/table_of_contents.html 3 Icons / Metaphors Information Common Realization Knowledge/Competency Pattern Governance Alignment Solution Approach 44 Agenda 11 IntroductionIntroduction 22 BusinessBusiness ModelModel RepresentationRepresentation 33 BusinessBusiness ProcessProcess ModelingModeling 44 CapturingCapturing thethe OrganizationOrganization andand LocationLocation AspectsAspects 55 DevelopingDeveloping aa ProcessProcess -
Flatpak a Desktop Version of Containers
Flatpak a desktop version of containers Alexander Larsson, Red Hat What is Flatpak? A distribution-independent, Linux-based application distribution and deployment mechanism for desktop applications distribution-independent ● run on any distribution ● build on any distribution ● Any version of the distribution Linux-based ● Flatpak runs only on Linux ● Uses linux-specific features ● However, needs to run on older kernel ● Current minimum target – RHEL 7 – Ubuntu 16.04 (Xenial) – Debian 9 (Stretch) Distribution mechanism ● Built in support for install ● Built in support for updates ● Anyone can set up a repository Deployment mechanism ● Run apps in a controlled environment – “container” ● Sandbox for improved security – Default sandbox is very limited – Apps can ask for more permissions Desktop application ● Focus on GUI apps ● No root permissions ● Automatically integrates with desktop ● App lifetimes are ad-hoc and transient ● Nothing assumes a “sysadmin” being available How is flatpak different from containers Filesystem layout Docker requirements ● Examples: – REST API micro-service – Website back-end ● Few dependencies, all hand-picked ● Runs as a daemon user ● Writes to nonstandard locations in file-system ● Not a lot of integration with host – DNS – Port forwarding – Volumes for data ● No access to host filesystem ● Updates are managed Docker layout ● One image for the whole fs – Bring your own dependencies – Layout up to each app ● Independent of host filesystem layout Flatpak requirements ● Examples – Firefox – Spotify – gedit