IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
the way we detected a client_disconnect does not work anymore with
spice-server >= 0.14.3, but there is a convienient function
that exits the spice-server on client disconnect
there is a slight behaviour change that should not make a big difference:
previously, if a user used the same '.vv' file twice, the first client
got disconnected and the second would connect
now, because the server closes on disconnect, the second client is
not be able to connect anymore
using our ui though, every click on 'shell>spice' generates a new '.vv'
file that works though (and for container shells we use dtach to mux)
i could not (in reasonable time) find out why the first client
disconnects at all, and also could not find another way to detect a
client disconnect that is similar to our previous method
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
we don't want to strip as part of installing, debhelper does that for us
while actually collecting the stripped debug symbols..
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
else the compiler guarantees alignment to 8 bytes only, but we need 1
byte to match the library's ABI.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
The disadvantage over keeping this and thus having to maintain
libspice-server ourself, a package with frequent security issues
reported, overweight the advantages. Spiceterm itself is probably not
used that much, and of that relatively small user base SASL is
probably almost non-existent.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
the only difference between
g_hash_table_insert and g_hash_table_replace is which key gets
freed/used
insert reuses the old key while replace used the new key
both insert the value or replace the value if it already exists
since the key is in the structure we allocate, we always
want to use the new key, and the old structure to be freed
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
when generating a bitmap for a character whose codepoint was above 255,
we used a cache_id of 0, malloc'd a CachedImage and inserted it into a
g_hashtable, without freeing the one which was before inserted with cache_id 0
this is circumvented by only generating a CachedImage when having
a cache_id != 0
the second leak was also with inserting into a hashtable, but there we
give the hashtable the g_free method as a value_destroy_func
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
changing most of the vt struct fields to unsigned, to avoid undefined
behaviour and use gotoxy for moving the cursor to correctly bound check
the cursor position
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
since we load the font from psf1 files, the highest utf8 codepoint we
have a fontmap for is 0xFFFF, so we use an unsigned short for the
character
but since we parse utf8 for up to 6 bytes we have to check the range, or
else we can get garbled output
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
