** Branch linked: lp:ubuntu/sblim-wbemcli
--
should escape backslash character in CimXml::unescapeXml()
https://bugs.launchpad.net/bugs/384721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package sblim-wbemcli - 1.6.1-0ubuntu1
---
sblim-wbemcli (1.6.1-0ubuntu1) lucid; urgency=low
* New upstream release, fixes LP: #384721
* Removed patches, all included upstream as of 1.6.1.
* Updated debhelper dependency and Standards-Version to fix
Fixed in 1.6.1, package needs an update
--
should escape backslash character in CimXml::unescapeXml()
https://bugs.launchpad.net/bugs/384721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Fix is in progress upstream.
** Changed in: sblim-wbemcli (Ubuntu)
Importance: Undecided = Low
** Changed in: sblim-wbemcli (Ubuntu)
Status: New = Triaged
--
should escape backslash character in CimXml::unescapeXml()
https://bugs.launchpad.net/bugs/384721
You received this bug
Given the sensitivity of escaping code in general, could you submit it on
the SBLIM bugtracker so that the issue gets reviewed and discussed by
upstream developers ?
Done,
https://sourceforge.net/tracker/?func=detailaid=2805214group_id=128809atid=712784
Furthermore, do you see an easy
$ wbemcli gi
'http://user:p...@hostname/root/cimv2:Win32_Share.Name=test;'
hostname:5988/root/cimv2:...,Caption=test\Test\,Descriptiontest...
Some typo in the above output (missing = after Description),
$ wbemcli gi 'http://user:p...@hostname/root/cimv2:Win32_Share.Name=test;'
** Also affects: sblim via
http://sourceforge.net/support/tracker.php?aid=2805214
Importance: Unknown
Status: Unknown
--
should escape backslash character in CimXml::unescapeXml()
https://bugs.launchpad.net/bugs/384721
You received this bug notification because you are a member of
Thanks for reporting this bug !
Given the sensitivity of escaping code in general, could you submit it on the
SBLIM bugtracker so that the issue gets reviewed and discussed by upstream
developers ?
http://sourceforge.net/tracker/?group_id=128809atid=712784
If you can't, I'll open it myself,
