On 07/16/2012 09:12 AM, Daniel P. Berrange wrote:
On Mon, Jul 16, 2012 at 03:10:25AM +0100, agraham wrote:
On 07/16/2012 01:03 AM, malc wrote:
On Sun, 15 Jul 2012, agraham wrote:
[..snip..]
I've found the root cause and hopefully you should be able to reproduce the
issue.
There was a confi
On 07/16/2012 09:12 AM, Daniel P. Berrange wrote:
On Mon, Jul 16, 2012 at 03:10:25AM +0100, agraham wrote:
On 07/16/2012 01:03 AM, malc wrote:
On Sun, 15 Jul 2012, agraham wrote:
[..snip..]
I've found the root cause and hopefully you should be able to reproduce the
issue.
There was a confi
On Mon, Jul 16, 2012 at 03:10:25AM +0100, agraham wrote:
> On 07/16/2012 01:03 AM, malc wrote:
> >On Sun, 15 Jul 2012, agraham wrote:
> >
> >[..snip..]
> >
> >>
> >>I've found the root cause and hopefully you should be able to reproduce the
> >>issue.
> >>
> >>There was a configure option introduce
On 07/16/2012 01:03 AM, malc wrote:
On Sun, 15 Jul 2012, agraham wrote:
[..snip..]
I've found the root cause and hopefully you should be able to reproduce the
issue.
There was a configure option introduced called "--enable-mixemu".
--enable-mixemu enable mixer emulation
Try this
On Sun, 15 Jul 2012, agraham wrote:
[..snip..]
>
> I've found the root cause and hopefully you should be able to reproduce the
> issue.
>
> There was a configure option introduced called "--enable-mixemu".
>
> --enable-mixemu enable mixer emulation
Try this
diff --git a/audio/audio.
On Sun, 15 Jul 2012, agraham wrote:
> On 07/15/2012 12:21 AM, malc wrote:
> > On Sun, 15 Jul 2012, agraham wrote:
> >
> > > On 07/15/2012 12:01 AM, malc wrote:
> > > > On Sat, 14 Jul 2012, agraham wrote:
> > > >
> > > > [..snip..]
> > > >
> > > > >
> > > > > /usr/bin/qemu-kvm -usb -no-fd-bootc
On 07/15/2012 12:21 AM, malc wrote:
On Sun, 15 Jul 2012, agraham wrote:
On 07/15/2012 12:01 AM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
[..snip..]
/usr/bin/qemu-kvm -usb -no-fd-bootchk -M pc -enable-kvm -m 128 -drive
file=/Storage/Windows/Images/Clone_of_Windows-XP-x32,if=none,medi
On Sat, 14 Jul 2012, agraham wrote:
[..snip..]
>
> Just to confirm, I'm connecting via a TCP INET socket (i.e. server and client
> are different machines), your acap.ml script also allows unix: sockets, which
> one are you using?
>
The default, TCP.
--
mailto:av1...@comtv.ru
On Sun, 15 Jul 2012, agraham wrote:
> On 07/15/2012 12:01 AM, malc wrote:
> > On Sat, 14 Jul 2012, agraham wrote:
> >
> > [..snip..]
> >
> > >
> > > /usr/bin/qemu-kvm -usb -no-fd-bootchk -M pc -enable-kvm -m 128 -drive
> > > file=/Storage/Windows/Images/Clone_of_Windows-XP-x32,if=none,media=dis
On 07/15/2012 12:01 AM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
[..snip..]
/usr/bin/qemu-kvm -usb -no-fd-bootchk -M pc -enable-kvm -m 128 -drive
file=/Storage/Windows/Images/Clone_of_Windows-XP-x32,if=none,media=disk,cache=unsafe,aio=native,snapshot,format=qcow2,id=virtio-blk-pci0
-de
On Sat, 14 Jul 2012, agraham wrote:
[..snip..]
>
> /usr/bin/qemu-kvm -usb -no-fd-bootchk -M pc -enable-kvm -m 128 -drive
> file=/Storage/Windows/Images/Clone_of_Windows-XP-x32,if=none,media=disk,cache=unsafe,aio=native,snapshot,format=qcow2,id=virtio-blk-pci0
> -device virtio-blk-pci,addr=0x05,b
On 07/14/2012 11:42 PM, agraham wrote:
On 07/14/2012 11:23 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 09:09 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 06:20 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 01:55 PM, agraham w
On 07/14/2012 11:23 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 09:09 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 06:20 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 01:55 PM, agraham wrote:
On 07/14/2012 11:44 AM, malc wrot
On Sat, 14 Jul 2012, agraham wrote:
> On 07/14/2012 09:09 PM, malc wrote:
> > On Sat, 14 Jul 2012, agraham wrote:
> >
> > > On 07/14/2012 06:20 PM, malc wrote:
> > > > On Sat, 14 Jul 2012, agraham wrote:
> > > >
> > > > > On 07/14/2012 01:55 PM, agraham wrote:
> > > > > > On 07/14/2012 11:44 AM,
On 07/14/2012 09:09 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 06:20 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 01:55 PM, agraham wrote:
On 07/14/2012 11:44 AM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
[..snip.]]
I've just rebuilt QE
On Sat, 14 Jul 2012, agraham wrote:
> On 07/14/2012 06:20 PM, malc wrote:
> > On Sat, 14 Jul 2012, agraham wrote:
> >
> > > On 07/14/2012 01:55 PM, agraham wrote:
> > > > On 07/14/2012 11:44 AM, malc wrote:
> > > > > On Sat, 14 Jul 2012, agraham wrote:
> >
> > [..snip.]]
> >
> > > > > > I've ju
On 07/14/2012 06:20 PM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 01:55 PM, agraham wrote:
On 07/14/2012 11:44 AM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
[..snip.]]
I've just rebuilt QEMU 1.0 (and all of its dependencies) and it has
the same
problem (zero byte
On Sat, 14 Jul 2012, agraham wrote:
> On 07/14/2012 01:55 PM, agraham wrote:
> > On 07/14/2012 11:44 AM, malc wrote:
> > > On Sat, 14 Jul 2012, agraham wrote:
[..snip.]]
> > > > I've just rebuilt QEMU 1.0 (and all of its dependencies) and it has
> > > > the same
> > > > problem (zero bytes), so
On 07/14/2012 01:55 PM, agraham wrote:
On 07/14/2012 11:44 AM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 03:17 AM, agraham wrote:
Hi Guys,
I've written a VNC client that implements the VNC QEMU Audio
extensions.
Using QEMU 0.13 it works very very for remote sound, however
On 07/14/2012 11:44 AM, malc wrote:
On Sat, 14 Jul 2012, agraham wrote:
On 07/14/2012 03:17 AM, agraham wrote:
Hi Guys,
I've written a VNC client that implements the VNC QEMU Audio extensions.
Using QEMU 0.13 it works very very for remote sound, however after
upgrading to QEMU 1.1.0 the audio
On Sat, 14 Jul 2012, agraham wrote:
> On 07/14/2012 03:17 AM, agraham wrote:
> > Hi Guys,
> >
> > I've written a VNC client that implements the VNC QEMU Audio extensions.
> > Using QEMU 0.13 it works very very for remote sound, however after
> > upgrading to QEMU 1.1.0 the audio stream contains o
On 07/14/2012 03:17 AM, agraham wrote:
Hi Guys,
I've written a VNC client that implements the VNC QEMU Audio extensions.
Using QEMU 0.13 it works very very for remote sound, however after
upgrading to QEMU 1.1.0 the audio stream contains only bytes of zeros,
so this results in no sound on the cl
Amen!
I was beginning to wonder when we would be integrating the email reader.
It would be nice if vncviewer didn't require a "host:port", but
instead would also accept a pair of pipes.
pipes are local and can even be anonymous. host:port is at least
machine wide and can be net wide.
Jo
Christopher Olsen wrote:
Anyone here know if there is a way to append to the VNC display header?
I'm not sure I understand what you're asking. What is the VNC display
header?
Regards,
Anthony Liguori
-Christopher
If I may say something here... the original question was how to append
the VNC header, so that the VNC client-compatible RFB auth could be
supported. We all know this is not "secure", but it's a common
feature of VNC and supporting it is not a bad thing IMHO. Adding it
to QEMU is no less secure
Hi,
On Thu, 22 Feb 2007, Anthony Liguori wrote:
> Johannes Schindelin wrote:
> >
> > This invariably leads to user confusion. ("But I _did_ use encryption?
> > What do you mean, it is not encrypted, and the handshake is weak?")
> >
>
> I understand. The solution is education. The document
Johannes Schindelin wrote:
Hi,
On Thu, 22 Feb 2007, Anthony Liguori wrote:
Johannes Schindelin wrote:
On Thu, 22 Feb 2007, Luke-Jr wrote:
Yes. The authentication is not really secure. It only uses 16 bits if I
remember correctly, so even without access to , it can be
easily b
Luke -Jr wrote:
On Thursday 22 February 2007 10:35, you wrote:
I would be happy with a patch that allowed a password to be set from the
monitor. Storing a password in a file on disk is, IMHO, ugly. If no
one beats me to it, I'll probably write something up this weekend.
That doesn't
Hi,
On Thu, 22 Feb 2007, Anthony Liguori wrote:
> Johannes Schindelin wrote:
> >
> > On Thu, 22 Feb 2007, Luke-Jr wrote:
> >
> > > Yes. The authentication is not really secure. It only uses 16 bits if I
> > > remember correctly, so even without access to , it can be
> > > easily broken.
> > >
Liguori
Sent: Thursday, February 22, 2007 11:36 AM
To: qemu-devel@nongnu.org
Cc: Luke-Jr
Subject: Re: [Qemu-devel] QEMU: VNC
Johannes Schindelin wrote:
> Hi,
>
> On Thu, 22 Feb 2007, Luke-Jr wrote:
>
>
>> Is there a reason to not use the semi-standard -rfbauth
>> argumen
Johannes Schindelin wrote:
Hi,
On Thu, 22 Feb 2007, Luke-Jr wrote:
Is there a reason to not use the semi-standard -rfbauth
argument?
I would be happy with a patch that allowed a password to be set from the
monitor. Storing a password in a file on disk is, IMHO, ugly. If no
one beats
Hi,
On Thu, 22 Feb 2007, Luke-Jr wrote:
> Is there a reason to not use the semi-standard -rfbauth
> argument?
Yes. The authentication is not really secure. It only uses 16 bits if I
remember correctly, so even without access to , it can be easily
broken.
The common practice is to block afte
On Monday 19 February 2007 20:11, Johannes Schindelin wrote:
> Hi,
>
> On Tue, 20 Feb 2007, Daniel P. Berrange wrote:
> > Well there's a number of plausible options
> >
> > - Password, but using challenge/resonse (either plain or TLS channel)
> > - Simple password (assuming a TLS encypted channe
Hi,
On Tue, 20 Feb 2007, Daniel P. Berrange wrote:
> Well there's a number of plausible options
>
> - Password, but using challenge/resonse (either plain or TLS channel)
> - Simple password (assuming a TLS encypted channel)
> - Whitelist based on client TLS certificate (common name/fingerpr
On Mon, Feb 19, 2007 at 06:45:54PM -0600, Anthony Liguori wrote:
> Daniel P. Berrange wrote:
> >On Mon, Feb 19, 2007 at 06:37:39PM -0500, Christopher Olsen wrote:
> >
> >>On Monday 19 February 2007 17:52, Fabrice Bellard wrote:
> >>
> >>>On the technical side, adding OpenSSL support in the cu
On Monday 19 February 2007 19:45, Anthony Liguori wrote:
> While this is all well and good, there is still the fundamental problem
> of how does one associate credentials with a VM. The actual security
> mechanism is, IMHO, just an implementation detail.
>
> Regards,
>
> Anthony Liguori
>
Very tr
Daniel P. Berrange wrote:
On Mon, Feb 19, 2007 at 06:37:39PM -0500, Christopher Olsen wrote:
On Monday 19 February 2007 17:52, Fabrice Bellard wrote:
On the technical side, adding OpenSSL support in the current VNC
implementation is QEMU seems easy (OpenSSL has a non blocking API which
On Mon, Feb 19, 2007 at 06:37:39PM -0500, Christopher Olsen wrote:
> On Monday 19 February 2007 17:52, Fabrice Bellard wrote:
> >
> > On the technical side, adding OpenSSL support in the current VNC
> > implementation is QEMU seems easy (OpenSSL has a non blocking API which
> > can be used with the
Hi,
On Mon, 19 Feb 2007, Fabrice Bellard wrote:
> On the technical side, adding OpenSSL support in the current VNC
> implementation is QEMU seems easy (OpenSSL has a non blocking API which
> can be used with the current callback API).
Goodbye compatibility.
I mean, you _can_ just ask for brea
On Monday 19 February 2007 17:52, Fabrice Bellard wrote:
>
> On the technical side, adding OpenSSL support in the current VNC
> implementation is QEMU seems easy (OpenSSL has a non blocking API which
> can be used with the current callback API).
>
> Fabrice.
>
Good call... Let me look into that.
Daniel P. Berrange wrote:
On Mon, Feb 19, 2007 at 12:41:53PM -0500, Christopher Olsen wrote:
On Monday 19 February 2007 12:30, Daniel P. Berrange wrote:
On Mon, Feb 19, 2007 at 03:11:15AM +0100, Johannes Schindelin wrote:
Hi,
On Sun, 18 Feb 2007, Anthony Liguori wrote:
Christopher Olsen wrot
On Monday 19 February 2007 14:09, Daniel P. Berrange wrote:
> Guess you missed the 'unix' directory - I have compiled both server &
> client of VeNCrypt on Linux no trouble.
>
> > I'm gathering the problem here is that VNC is spinning off in many
> > directions... So any implementation on the QEMU
On Mon, Feb 19, 2007 at 12:41:53PM -0500, Christopher Olsen wrote:
>
> On Monday 19 February 2007 12:30, Daniel P. Berrange wrote:
> > On Mon, Feb 19, 2007 at 03:11:15AM +0100, Johannes Schindelin wrote:
> > > Hi,
> > >
> > > On Sun, 18 Feb 2007, Anthony Liguori wrote:
> > > > Christopher Olsen wr
On Monday 19 February 2007 12:30, Daniel P. Berrange wrote:
> On Mon, Feb 19, 2007 at 03:11:15AM +0100, Johannes Schindelin wrote:
> > Hi,
> >
> > On Sun, 18 Feb 2007, Anthony Liguori wrote:
> > > Christopher Olsen wrote:
> > > > Sorry I'll attempt to use the preferred patching method in the
> > >
On Mon, Feb 19, 2007 at 03:11:15AM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Sun, 18 Feb 2007, Anthony Liguori wrote:
>
> > Christopher Olsen wrote:
> > > Sorry I'll attempt to use the preferred patching method in the future..
> > >
> > > Secure vnc auth method the default built in method f
Understandable...
However I'm not sure about others and how they intend to use QEMU.. But I for
one know that I do have a use for authentication within the VNC session..
You're right that it's supposed to be a standard protocol but it doesn't
appread to be from the many different flavors of VN
Hi,
On Mon, 19 Feb 2007, Christopher Olsen wrote:
> I've done some further thought and investigation and as far as using
> QEMU inside a Unix environment, I see no reason as to why the
> authentication couldn't be tied into PAM...
Because this is supposed to be a standard protocol, meant for w
In regards to all this
Johannes... You're correct the challenge response method for authentication
inside of VNC isn't secure at all it's like locking your screen door at home
will keep most people out just not the ones who really want to get in...
I've done some further thought and investigati
Johannes Schindelin wrote:
Hi,
On Sun, 18 Feb 2007, Anthony Liguori wrote:
Christopher Olsen wrote:
Sorry I'll attempt to use the preferred patching method in the future..
Secure vnc auth method the default built in method from
We can't take a password from a command line.
Hi,
On Sun, 18 Feb 2007, Anthony Liguori wrote:
> Christopher Olsen wrote:
> > Sorry I'll attempt to use the preferred patching method in the future..
> >
> > Secure vnc auth method the default built in method from
> >
>
> We can't take a password from a command line. Supporting VNC auth is
Christopher Olsen wrote:
Sorry I'll attempt to use the preferred patching method in the future..
Secure vnc auth method the default built in method from
We can't take a password from a command line. Supporting VNC auth is
super easy otherwise. I really think we need to have a config file
Hi,
On Sun, 18 Feb 2007, Christopher Olsen wrote:
> Secure vnc auth method the default built in method from
... yes?
Ciao,
Dscho
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Sorry I'll attempt to use the preferred patching method in the future..
Secure vnc auth method the default built in method from
On Sunday 18 February 2007 19:14, Johannes Schindelin wrote:
> Hi,
>
> On Sun, 18 Feb 2007, Christopher Olsen wrote:
> > Actually I have a version 2 to my patch which I
Oops.. I really did mean to trim that patch down to just the code portions
On Sunday 18 February 2007 19:11, Johannes Schindelin wrote:
> Hi,
>
> On Sun, 18 Feb 2007, Christopher Olsen wrote:
> > I didn't see a way so here is a patch for it work on 0.9.0
>
> This is a sneaky way to introduce a
Hi,
On Sun, 18 Feb 2007, Christopher Olsen wrote:
> Actually I have a version 2 to my patch which I will forward in by
> tomorrow which allows for vnc authentication..
Which one? AFAICT there are three authentication methods, one of which is
not secure at all. Another one is no vnc authenticat
Hi,
On Sun, 18 Feb 2007, Christopher Olsen wrote:
> I didn't see a way so here is a patch for it work on 0.9.0
This is a sneaky way to introduce a whole shotload of things, among others
a copyright to your name, FreeBSD stuff, some #define's which may or may
not break things.
Judging by the l
Anthony,
Actually I have a version 2 to my patch which I will forward in by tomorrow
which allows for vnc authentication..
-Christopher
On Sunday 18 February 2007 18:08, Anthony Liguori wrote:
> Christopher Olsen wrote:
> > I didn't see a way so here is a patch for it work on 0.9.0
>
> I've got
Christopher Olsen wrote:
I didn't see a way so here is a patch for it work on 0.9.0
I've got a more generic -name patch I've been sitting on. It adds a
title for the VNC session and SDL session. If there's interest, I can
push it further ahead in my queue.
Regards,
Anthony Liguori
-
I didn't see a way so here is a patch for it work on 0.9.0
-Christopher
On Friday 16 February 2007 14:02, Christopher Olsen wrote:
> Anyone here know if there is a way to append to the VNC display header?
>
> -Christopher
--
Christopher Olsen
[EMAIL PROTECTED]
Tel: 631-676-4877
Fax: 631-249-303
59 matches
Mail list logo
