IPP - Revision history

84.153.135.37 at 08:27, 31 January 2017

2017-01-31T08:27:31Z

Admin at 14:47, 28 January 2017

2017-01-28T14:47:38Z

Admin at 14:42, 28 January 2017

2017-01-28T14:42:56Z

Admin at 14:18, 28 January 2017

2017-01-28T14:18:20Z

Admin at 14:16, 28 January 2017

2017-01-28T14:16:15Z

Admin at 19:57, 14 January 2017

2017-01-14T19:57:41Z

Admin at 09:50, 9 January 2017

2017-01-09T09:50:05Z

Admin: Created page with "Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet..."

2017-01-09T09:34:12Z

Created page with "Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet..."

New page

Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass|accounting bypasses]].

→ ''Related aricles:'' [[Attack carriers]], [[Accounting bypass]], [[Buffer overflows]]



----

@@ Line 3: / Line 3: @@
 Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass|accounting bypasses]].
-→ ''Related aricles:'' [[Fundamentals#High-level_overview|Fundamentals]], [[Attack carriers]], [[Accounting bypass]], [[Buffer overflows]]
+→ ''Related articles:'' [[Fundamentals#High-level_overview|Fundamentals]], [[Attack carriers]], [[Accounting bypass]], [[Buffer overflows]]
 <!-- , printer language discovery and cross-site printing attacks. -->
 ----

← Older revision		Revision as of 14:47, 28 January 2017
Line 1:		Line 1:
−	[[File:IPP-deployment-channel.png\|thumb\|180px\|IPP ~~print job deployment~~]]	+	[[File:IPP-deployment-channel.png\|thumb\|180px\|Printing over IPP]]

	Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].		Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].

← Older revision		Revision as of 14:42, 28 January 2017
Line 1:		Line 1:
−	[[File:IPP-deployment-channel.png\|thumb\|~~Deployment of (malicious) print jobs via~~ IPP]]	+	[[File:IPP-deployment-channel.png\|thumb\|180px\|IPP print job deployment]]

	Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].		Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].

← Older revision		Revision as of 14:18, 28 January 2017
Line 1:		Line 1:
−	[[File:IPP-deployment-channel.png\|thumb\|Deployment of (malicious) print jobs via ~~IPPl~~]]	+	[[File:IPP-deployment-channel.png\|thumb\|Deployment of (malicious) print jobs via IPP]]

	Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].		Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].

← Older revision		Revision as of 14:16, 28 January 2017
Line 1:		Line 1:
		+	[[File:IPP-deployment-channel.png\|thumb\|Deployment of (malicious) print jobs via IPPl]]
		+
	Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].		Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].

← Older revision		Revision as of 19:57, 14 January 2017
Line 1:		Line 1:
	Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].		Between 1999 and 2005 the IETF IPP working group published various draft standards for an LPD successor capable of authentication and print job queue management. The Internet Printing Protocol (IPP) is defined in RFC2910 <ref>''[https://www.ietf.org/rfc/rfc2910.txt RFC2910: Internet Printing Protocol/1.1: Encoding and Transport]'', R. Herriot, 2000</ref> and RFC2911 <ref>''[https://www.ietf.org/rfc/rfc2911.txt RFC2911: Internet Printing Protocol/1.1: Model and Semantics]'', T. Hastings and others, 2000</ref>. IPP is an extendable protocol, for example ‘IPP Everywhere’ as specified in <ref>''[http://www.pwg.org/candidates/cs-ippeve10-20130128-5100.14.pdf IPP Everywhere]'', PWG, The Printer Working Group, 2013</ref> is a candidate for a standard in mobile and cloud printing and IPP extensions for 3D printing <ref>''[http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ipp3d10-20160824.pdf IPP 3D Printing Extensions (3D)]'', PWG, The Printer Working Group, 2016</ref> have been released. Because IPP is based on HTTP, it inherits all existing security features like [https://en.wikipedia.org/wiki/Basic_access_authentication basic]/[https://en.wikipedia.org/wiki/Digest_access_authentication digest] authentication and [https://en.wikipedia.org/wiki/Transport_Layer_Security SSL/TLS] encryption. To submit a print job or to retrieve status information from the printer, an HTTP ''POST'' request is sent to the IPP server listening on port 631/tcp. A famous open-source IPP implementation is ''CUPS'' <ref>''[http://www.cups.org/ Common Unix Printing System]'', M. Sweet</ref>, which is the default printing system in many Linux distributions and OS X. Network printers usually run their own IPP server as one method to accept print jobs. Similar to [[LPD]], IPP is a '''channel''' to deploy the actual data to be printed and can be abused as a carrier for malicious PostScript or PJL files. In this wiki, IPP itself is no further exploited except for [[Accounting bypass\|accounting bypasses]].
−

	→ ''Related aricles:'' [[Fundamentals#High-level_overview\|Fundamentals]], [[Attack carriers]], [[Accounting bypass]], [[Buffer overflows]]		→ ''Related aricles:'' [[Fundamentals#High-level_overview\|Fundamentals]], [[Attack carriers]], [[Accounting bypass]], [[Buffer overflows]]