Fedora-Fr - Communauté francophone Fedora - Linux

Planet de Fedora-Fr : la communauté francophone autour de la distribution Linux Fedora

A propos

Cette page est actualisée toutes les heures.

Cette page est une sélection de blogs autour de Fedora. Fedora-Fr.org décline toute responsabilité au sujet des propos tenus par les auteurs des blogs de ce planet. Leurs propos sont leur entière responsabilité.

Le contenu de ce planet appartient à leurs auteurs respectifs. Merci de consulter leur blogs pour obtenir les licences respectives.

Mot-clefs : Revelation

Une CLI pour Revelation

Pierre-Yves Chibon


Une petite interface en ligne de commande pour Revelation.

French version (English version)

Revelation 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é.

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).

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.

Voir le contenu du fichier:

$ ./revelationcli.py revelation.db --showtree
  | \_ test1
  | \_ test2
  | \_ folder1
  |   | \_ folder2
  |   |   | \_ test4
  |   |   | \_ test2
  |   | \_ test3

Voir les information à propos d'un mot de passe:

$ ./revelationcli.py revelation.db test4
  Name : test4
  Database : test

Voir toutes les informations à propos d'un mot de passe (y compris le mot de passe lui même):

$ ./revelationcli.py revelation.db test4 --show
  Name : test4
  Password : HYoJx7W8
  Database : test

Le projet est pour le moment disponible à : http://project.pingoured.fr/revelationcli/

Voyons si ça vaut le coup de le développer plus que ça ;-)


Pierre-Yves Chibon

The ideas I would like to do/see.

Une petite liste d'idées que je voudrais faire/voir.

English format

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.

There is what I have been thinking of:

  • R2spec 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.
  • 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 Fedora-R-devel mailing-list and it is something I would like to help as I don't think I'd have time to do it myself.
  • Revelation 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.
  • 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 pkgdb.
  • Make yum-utils 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 import yumutils and use the code easily.
  • ABRT 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.

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?

If there are people interested about them, maybe I could make some time ;-)