qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH for-2.4 0/5] chardev: Add IRC char driver
Date: Wed,  1 Apr 2015 14:09:12 +0200	[thread overview]
Message-ID: <1427890157-18639-1-git-send-email-mreitz@redhat.com> (raw)

This series adds a long-missing IRC character device driver to qemu. See
patch 1 for an explanation why you should have been missing it.

To make it short: IRC is a very well tested and more reliable, social,
human-friendly, and ubiquitous[1] communication interface than any of
the other character devices qemu has to offer.

"Social?", you ask? "Exactly!", I say. Again, see patch 1.

"But why do we need 'social'?" Because what is it that separates qemu
from the other well-known type-2 hypervisors? Besides simply being
better (of course!), it is free software which is written by and
maintained by a community. It is social.

Now we need to capitalize on this very fact even further, not only
embracing it in qemu development, but also in qemu usage.

Already, everyone can work on the qemu project.

In the future, everyone will be able to work with a qemu instance.

This is what this patch series embodies. The future is now.

What a time to be alive.


Oh, and don't forget the reliability and ubiquity.


Finally, there has been no encryption whatsoever in qemu's character
devices so far. For IRC, SSL is a well-known and commonly implemented
client-to-server encryption method (patch 3), and this series will
furthermore introduce a widely used and easy to implement, yet secure
enough even for military standards, end-to-end encryption (patch 4).


[1] Google search for:
     - irc: 1.27e+8 results
     - tcp: 1.08e+8 results
     - udp: 6.28e+7 results
     - telnet: 2.29e+7 results
     - stdio: 9.04e+6 results
     - "unix sockets": 1.37e+5 results


Max Reitz (5):
  chardev: Add IRC char driver
  chardev/irc: Add sockfd option
  chardev/irc: Add SSL support
  chardev/irc: Add end-to-end encryption
  Documentation: Document IRC char driver

 configure        |  43 +++-
 qapi-schema.json |  32 +++
 qemu-char.c      | 714 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 qemu-options.hx  |  28 +++
 4 files changed, 806 insertions(+), 11 deletions(-)

-- 
2.3.4

             reply	other threads:[~2015-04-01 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 12:09 Max Reitz [this message]
2015-04-01 12:09 ` [Qemu-devel] [PATCH for-2.4 1/5] chardev: Add IRC char driver Max Reitz
2015-04-01 12:09 ` [Qemu-devel] [PATCH for-2.4 2/5] chardev/irc: Add sockfd option Max Reitz
2015-04-01 12:09 ` [Qemu-devel] [PATCH for-2.4 3/5] chardev/irc: Add SSL support Max Reitz
2015-04-01 12:09 ` [Qemu-devel] [PATCH for-2.4 4/5] chardev/irc: Add end-to-end encryption Max Reitz
2015-04-01 12:09 ` [Qemu-devel] [PATCH for-2.4 5/5] Documentation: Document IRC char driver Max Reitz
2015-04-02  8:57 ` [Qemu-devel] [PATCH for-2.4 0/5] chardev: Add " Stefan Hajnoczi
2015-04-02 14:04   ` Max Reitz
2015-04-02 19:19 ` Markus Armbruster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1427890157-18639-1-git-send-email-mreitz@redhat.com \
    --to=mreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).