Most of these function are identical.
Only difference were basically debugging message but now
with a proper tests are less important.
The mechname field is used to differentiate between first step and
following ones.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 156 +++--
Instead of having half state in RedSASL and half in RedSASLAuth
move everything in RedSASLAuth. This also reduces memory usage
when we are using SASL but we finish the authentication step.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 129 ++
Instead of having half state in RedSASL and half in RedSASLAuth
move everything in RedSASLAuth. This also reduces memory usage
when we are using SASL but we finish the authentication step.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 129 ++
Try different connections with different tricky names.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 82 +---
1 file changed, 71 insertions(+), 11 deletions(-)
diff --git a/server/tests/test-sasl.c b/server/tests/test-sasl.c
index 41bc
Asynchronous code jumping from a file to another is tedious to read
also having code handling the same stuff in two files does not look
a good design.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 121 +---
server/red-stream.h | 11 +---
The server on failure can just disconnect the client or report the
error. The error report can be done using new protocol 2 or just
a number (like protocol 1).
Detect the failure report to make possible to check it.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 118 ++
Create a thread that emulates a client and starts SASL authentication
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 237 ++-
1 file changed, 236 insertions(+), 1 deletion(-)
diff --git a/server/tests/test-sasl.c b/server/tests/test-sas
All SPICE protocol is little endian, there's no agreement on other
endian and currently we support only little endian so make sure
this will work even possibly running on a big endian machine.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 28
1 file change
Most of these function are identical.
Only difference were basically debugging message but now
with a proper tests are less important.
The mechname field is used to differentiate between first step and
following ones.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 156 +++--
Check some functions are called in a given sequence.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/server/tests/test-sasl.c b/server/tests/test-sasl.c
index 0e4c633c..85332974 100644
--- a/server/tests/test-sa
Not currently working, is defining SASL functions used by the code.
As the symbols defined in the objects have more priority than the ones
defined by the libraries these function take precedence compared to
system library.
Signed-off-by: Frediano Ziglio
---
configure.ac | 1 +
serv
All SPICE protocol is little endian, there's no agreement on other
endian and currently we support only little endian so make sure
this will work even possibly running on a big endian machine.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 28
1 file change
Asynchronous code jumping from a file to another is tedious to read
also having code handling the same stuff in two files does not look
a good design.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 121 +---
server/red-stream.h | 11 +---
The server on failure can just disconnect the client or report the
error. The error report can be done using new protocol 2 or just
a number (like protocol 1).
Detect the failure report to make possible to check it.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 114 ++
Use some flags to specify which behaviour to change and different test
cases to test them.
Some cases specify when client stop sending data at different steps of
the process.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 171 ++-
1 file
SASL authentication code were a bit dodgy to see.
The series have 2 parts:
- a test for SASL code;
- some code refactory.
Test is not that straightforward, maybe some code should be put in
different files. On the other end I don't think the code that is
mocking SASL will be reused in other tests.
Hi,
On 01/08/2018 03:17 PM, Christophe Fergeau wrote:
On Mon, Jan 08, 2018 at 04:05:30PM +0800, 王杰东 wrote:
When my virt-viewer spice clients are in net-A , and the hypervisor server with
spice is in net-B , and a server is in both net-A and net-B
How can i use virt-viewer to connect th vms on
Hi
On 01/08/2018 11:47 AM, Frediano Ziglio wrote:
Use custom playbin sink instead of just appsink.
In order to allow playbin to choose decoders that requires
more complex pipelines (e.g. pipeline that requires color
space conversion & uses gl memory).
The new sink composed as such:
... ! autovi
Hi,
On 01/04/2018 11:26 AM, Christophe Fergeau wrote:
On Sun, Dec 31, 2017 at 05:46:24PM +0200, Snir Sheriber wrote:
Use custom playbin sink instead of just appsink.
In order to allow playbin to choose decoders that requires
more complex pipelines (e.g. pipeline that requires color
space conve
On Mon, Jan 08, 2018 at 04:05:30PM +0800, 王杰东 wrote:
> When my virt-viewer spice clients are in net-A , and the hypervisor server
> with spice is in net-B , and a server is in both net-A and net-B
> How can i use virt-viewer to connect th vms on hypervisor server ?
>
> https://access.redhat.com/
On Mon, Jan 08, 2018 at 04:47:26AM -0500, Frediano Ziglio wrote:
> >
> > Use custom playbin sink instead of just appsink.
> > In order to allow playbin to choose decoders that requires
> > more complex pipelines (e.g. pipeline that requires color
> > space conversion & uses gl memory).
> > The new
>
> Hey,
>
> Here are 2 build fixes for FreeBSD which were filed in bugzilla ([1] and
> [2]). They look good to me, so I'll push them in a few days if nobody
> objects in the mean time.
>
> Christophe
>
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=104524
> [2] https://bugs.freedesktop.org
From: Ting-Wei Lan
FreeBSD has OpenSSL installed in base, but .pc files are not available.
We can still successfully build spice-gtk by setting SSL_CFLAGS and
SSL_LIBS variables manually, but openssl will still be recorded to
Requires.private field of spice-client-glib-2.0.pc, causing problems fo
Hey,
Here are 2 build fixes for FreeBSD which were filed in bugzilla ([1] and
[2]). They look good to me, so I'll push them in a few days if nobody
objects in the mean time.
Christophe
[1] https://bugs.freedesktop.org/show_bug.cgi?id=104524
[2] https://bugs.freedesktop.org/show_bug.cgi?id=104525
From: Ting-Wei Lan
sys/acl.h works on both FreeBSD and Linux, so we should use it instead
of acl/libacl.h, which only works on Linux.
FreeBSD puts ACL functions in libc, so we should check whether ACL
functions are available in libc before doing the check with -lacl.
https://bugs.freedesktop.or
>
> Use custom playbin sink instead of just appsink.
> In order to allow playbin to choose decoders that requires
> more complex pipelines (e.g. pipeline that requires color
> space conversion & uses gl memory).
> The new sink composed as such:
> ... ! autovideoconvert ! gldownload ! appsink
Addi
Instead of having half state in RedSASL and half in RedSASLAuth
move everything in RedSASLAuth. This also reduces memory usage
when we are using SASL but we finish the authentication step.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 129 ++
Most of these function are identical.
Only difference were basically debugging message but now
with a proper tests are less important.
The mechname field is used to differentiate between first step and
following ones.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 156 +++--
All SPICE protocol is little endian, there's no agreement on other
endian and currently we support only little endian so make sure
this will work even possibly running on a big endian machine.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 28
1 file change
The server on failure can just disconnect the client or report the
error. The error report can be done using new protocol 2 or just
a number (like protocol 1).
Detect the failure report to make possible to check it.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 111 ++
Asynchronous code jumping from a file to another is tedious to read
also having code handling the same stuff in two files does not look
a good design.
Signed-off-by: Frediano Ziglio
---
server/red-stream.c | 121 +---
server/red-stream.h | 11 +---
Create a thread that emulates a client and starts SASL authentication
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 237 ++-
1 file changed, 236 insertions(+), 1 deletion(-)
diff --git a/server/tests/test-sasl.c b/server/tests/test-sas
Check some functions are called in a given sequence.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/server/tests/test-sasl.c b/server/tests/test-sasl.c
index 0e4c633c..85332974 100644
--- a/server/tests/test-sa
Use some flags to specify which behaviour to change and different test
cases to test them.
Some cases specify when client stop sending data at different steps of
the process.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 232 ++-
1 file
SASL authentication code were a bit dodgy to see.
The series have basically 3 parts:
- some minor fixes;
- a test for SASL code;
- some code refactory.
The fixes were handling issues discovered looking at code and writing
the tests.
Test is not that straightforward, maybe some code should be put i
Try different connections with different tricky names.
Signed-off-by: Frediano Ziglio
---
server/tests/test-sasl.c | 77 ++--
1 file changed, 68 insertions(+), 9 deletions(-)
diff --git a/server/tests/test-sasl.c b/server/tests/test-sasl.c
index 41bcf
Not currently working, is defining SASL functions used by the code.
As the symbols defined in the objects have more priority than the ones
defined by the libraries these function take precedence compared to
system library.
Signed-off-by: Frediano Ziglio
---
configure.ac | 1 +
serv
When my virt-viewer spice clients are in net-A , and the hypervisor server with
spice is in net-B , and a server is in both net-A and net-B
How can i use virt-viewer to connect th vms on hypervisor server ?
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/
38 matches
Mail list logo
