Le blog de pingou - Tag - RevelationLe blog de pingou, ses actualités sur Fedora, ses RPMs, ses tests, son Linux... :-)
Pingou's weblog, his fedora's news, his RPMs, his tests, his Linux... :-)2022-02-17T10:46:15+01:00pingouurn:md5:66db5ce1ed1a80cb2f424695b4bb7780DotclearUne CLI pour Revelationurn:md5:3fde0b6266f3fd919830016679ac103f2011-09-14T15:53:00+01:002011-09-14T15:53:00+01:00Pierre-YvesGénéralFedora-frPythonRevelationTerminal<p><img src="https://blog.pingoured.fr/public/source.png" alt="source.png" /></p>
<p>Une petite interface en ligne de commande pour Revelation.</p> <p><strong><em>French version</em></strong> (<a href="http://blog.pingoured.fr/index.php?post/2011/09/14/CLI-for-revelation">English version</a>)</p>
<p><a href="http://oss.codepoet.no/revelation/">Revelation</a> est un logiciel qui vous permet de gérer vos mot de passe comme vous le souhaitez. Vous pouvez les organiser en list ou par catégorie avec des dossiers, et le tout est sauvegarder dans un fichier chiffré.</p>
<p>Je l'utilise depuis quelques temps mais bon, je ne souhaite pas me promener tous les jours avec le dit fichier sur une clé USB (même si celle-ci est chiffrée elle-même).</p>
<p>Du coup j'ai écrit une petite interface en ligne de commande qui permet d'interroger une base de donnée de Revelation par ssh.</p>
<p>Voir le contenu du fichier:</p>
<pre>$ ./revelationcli.py revelation.db --showtree
Password:
Database:
| \_ test1
| \_ test2
| \_ folder1
| | \_ folder2
| | | \_ test4
| | | \_ test2
| | \_ test3</pre>
<p>Voir les information à propos d'un mot de passe:</p>
<pre>$ ./revelationcli.py revelation.db test4
Password:
Name : test4
Database : test</pre>
<p>Voir toutes les informations à propos d'un mot de passe (y compris le mot de passe lui même):</p>
<pre>$ ./revelationcli.py revelation.db test4 --show
Password:
Name : test4
Password : HYoJx7W8
Database : test</pre>
<p>Le projet est pour le moment disponible à : <a href="http://project.pingoured.fr/revelationcli/">http://project.pingoured.fr/revelationcli/</a></p>
<p>Voyons si ça vaut le coup de le développer plus que ça ;-)</p>CLI for revelationurn:md5:bcb29e8845ac25ef07fd9979a484979c2011-09-14T15:46:00+01:002011-09-14T14:53:47+01:00Pierre-YvesGénéralFedora-planetPythonRevelationTerminal<p><img src="https://blog.pingoured.fr/public/source.png" alt="source.png" /></p>
<p>A small CLI for the password manager tool, revelation</p> <p><strong><em>English version</em></strong> (<a href="http://blog.pingoured.fr/index.php?post/2011/09/14/Une-CLI-pour-Revelation">French version</a>)</p>
<p><a href="http://oss.codepoet.no/revelation/">Revelation</a> is a very nice password management tool, I have been using it for a while and I quite like it.</p>
<p>However, you don't always want to have it on your computer but you would prefer to be able to query it through ssh or so. At least it is my case :-)</p>
<p>I therefore wrote a small CLI in python which relies on revelation's API to browse and retrieve password from a revelation database.</p>
<p>Show the content of the database:</p>
<pre>$ ./revelationcli.py revelation.db --showtree
Password:
Database:
| \_ test1
| \_ test2
| \_ folder1
| | \_ folder2
| | | \_ test4
| | | \_ test2
| | \_ test3</pre>
<p>Show information about one password:</p>
<pre>$ ./revelationcli.py revelation.db test4
Password:
Name : test4
Database : test</pre>
<p>Show all the information about one password (included the password itself):</p>
<pre>$ ./revelationcli.py revelation.db test4 --show
Password:
Name : test4
Password : HYoJx7W8
Database : test</pre>
<p>The project is for the moment at: <a href="http://project.pingoured.fr/revelationcli/">http://project.pingoured.fr/revelationcli/</a></p>
<p>Let's see if it is interesting enough to make it more open :-)</p>My TODOsurn:md5:6aa7af30b6e3cbab429891a7445129462011-05-09T08:11:00+01:002011-05-09T07:28:27+01:00Pierre-YvesGénéralABRTFedoraFedora-planetPythonRRevelationyum<p>The ideas I would like to do/see.</p>
<p>Une petite liste d'idées que je voudrais faire/voir.</p> <p><strong><em>English format</em></strong></p>
<p>The good point of spending 2 weeks without touching a keyboard is that it gives you ideas on what you want to do or see done.</p>
<p>There is what I have been thinking of:</p>
<ul>
<li><a href="https://fedorahosted.org/r2spec/">R2spec</a> is a tool to create spec file, and now rpm, for R packages. It has quite evolve since I first write it and my python knowledge for sure has changed. I therefore would like to clean it and rewrite it to a more logical and hopefully cleaner code.</li>
</ul>
<ul>
<li>cran2rpm, this is a tool to generate the order in which the R packages should be built for a given repo. This would be used with R2spec to generate RPMs for the whole CRAN or Bioconductor. There has been some thoughts about it on the <a href="https://admin.fedoraproject.org/mailman/listinfo/r-devel">Fedora-R-devel</a> mailing-list and it is something I would like to help as I don't think I'd have time to do it myself.</li>
</ul>
<ul>
<li><a href="https://bitbucket.org/erikg/revelation/wiki/Home">Revelation</a> is a password management tool. If I had time I would like to remove its warnings and even implement a pgp encryption for the database. At some point I started to rewrite it but it would be simpler to just work on revelation rather than rewrite everything.</li>
</ul>
<ul>
<li>pkgdb-cli would be a tool to query the package database of Fedora. It would give you the version of the package in the different repo, the owner of the package on the different branches and if possible maybe it could also handle ACL request. So basically a CLI version of <a href="https://admin.fedoraproject.org/pkgdb/">pkgdb</a>.</li>
</ul>
<ul>
<li>Make <a href="http://yum.baseurl.org/wiki/YumUtils">yum-utils</a> a python library. At the moment most of yum-utils' code are simple python file, I was thinking that making it a python library would be nice as it would allow people to <em>import yumutils</em> and use the code easily.</li>
</ul>
<ul>
<li><a href="https://fedorahosted.org/abrt/">ABRT</a> report upstream. This is something I have been thinking about but I never shared it nor did I check if the discussion already happened, but I was thinking that there cases were one would like ABRT to report its bug to the bug tracker of the project rather than Fedora's bugzilla. I was thinking that there could be a plugin system on ABRT with a plugin for each bug tracker system (trac, bugzilla, google code...) and a small database containing for each packages concerned the url of the bug tracker, its system and username and password. When a bug would be detected, ABRT would check if the package is present in the database, if it is, then the bug is opened against this bug tracker otherwise it is opened in Fedora's bugzilla.</li>
</ul>
<p>So there are my few ideas. I don't know whether they are good nor if I will have time to work on them. But what do you think about them?</p>
<p>If there are people interested about them, maybe I could make some time ;-)</p>