Hi, you can export revelation data to an xml file:
<?xml version="1.0" encoding="utf-8" ?>
<revelationdata version="0.4.7" dataversion="1">
<entry type="shell">
<name>foo</name>
<description></description>
<updated>1170341697</updated>
<field id="generic-hostname">foo</field>
<field id="generic-domain">com</field>
<field id="generic-username">bar</field>
<field id="generic-password">nfebDm2B</field>
</entry>
</revelationdata>
Now you could create an XSLT file filtering by name, creating a new XML
file which you could import using revelation.
Its manual, but might be a workaround. Not sure how much work this will
create or save though.
regards
Stefan
schönfeld / in-medias-res wrote:
> Hi,
>
> Stefan Völkel schrieb:
>> Hi,
>>
>> a workaround might be using XSLT, which would require the unencrypted
>> xml file somewhere.
>
> please do explain this maybe-workaround. Cause i cannot see how XSLT can
> be a workaround to not having the functionality to export a single entry
> instead of the whole directory. A workaround is to export it to XML and
> edit it. But thats not practibable if you do have about several hundreds
> of accounts in your directory.
>
> Best Regards
>
> Patrick
>
--
Stefan Völkel mobile: +49.170.79177.17
Millenux GmbH phone: +49.711.88770.300
Lilienthalstraße 2 phone: +49.89.608665.27
70825 Stuttgart-Korntal fax: +49.711.88770.349
-= linux without limits -=- http://linux.zSeries.org/ =-
signature.asc
Description: OpenPGP digital signature
