Re: [gcmd-dev] history

[Uwe Scholz]

Hi,

haha, "digital middle finger" - I like that one, Ken! :-D

It is funny that you guys discuss the different places of config files
of gnome commander. This is actually something I am currently working
on.

Historically, there have been config files in ~/.gnome2/ (generated by
usage of the outdated gnome-config library(*)) and others in
~/.gnome-commander/ with home-grown file formats as well as
the xml file ~/.gnome-commander/gnome-commander.xml. For me it looked
like cabbage and turnips!

To get rid of gnome-config, since version 1.6 gnome-commander is using
gKeyFiles, stored in ~/.gnome-commander/, and also it uses dConf(**)
which stores its database in ~/.config/dconf/user. I was not in favor
of storing everything in the xml file, because the code for doing this
is hard to maintain and it also uses gnome-config which will be dropped
by Linux distributions like Debian in the future.

When you start gnome commander 1.6 or later the first time it will
migrate most of the old configuration files into the new formats (not
the xml!). But for security reasons I decided to leave the old files at
their place, renaming them to "*.deprecated". If you feel that the
migration went well, i.e. you don't miss any data and there is no
strange behavior, just delete those files: they aren't needed anymore.
Gnome commander will not delete them by itself.

Michael: I encourage you to update from 1.4.8 to any other version
between 1.6.0 and 1.8.1 as it will not be possible to update from 1.4.8
to 1.9.0 with automatic migration of the very old file formats of
devices and fav-apps in ~/.gnome-commander used in 1.4.x. I have to
throw out old code for cleaning up the mess... :-(

(*)
https://developer.gnome.org/libgnome/stable/libgnome-gnome-config.html

(**)
https://en.wikipedia.org/wiki/Dconf

Best wishes
Uwe

Am Mon, 19 Nov 2018 14:59:07 +0000 schrieb kht-lists:
>
> Hello again Michael,
> 
> My main OS is CentOS 7 and the g-c package is available in the
> nux-dextop repo. I followed these instructions
> https://www.linuxhelp.com/how-to-install-gnome-commander-1-8-1-on-ubuntu-17-04
> when I built g-c for use on an Ubuntu Mate 18.04 virtual machine.  I
> then managed to build a .deb package (un-signed, un-official etc. for
> personal use) which I was then able to copy to another virtual
> machine to do the installation. I did not want to put all the
> development packages on that VM. If you are interested I would be
> happy to provide the .deb package to you. No guarantee of course!
> Just let me know.
> 
> In my installations of g-c I generally make these changes:
> 
> Single click to open items
> [ ] Don's start a new instance is UNchecked
> change color scheme to "Deep blue"
> 
> The keyboard shortcut to "Open connection" is changed to Crtl-S (I
> guess I liked to remember "connect to Server") I have 3 "devices"
> created on my main workstation install. These refer to mount points
> such as /data
> 
> I have some applications associated with mime types. This is
> described on the g-c web site under Tips and tricks for Gnome
> Commander.
> 
> I believe that is all that I have changed.
> 
> There appears to be no g-c related subdirectory nor file under
> ~/.config
> 
> In the folder ~/.gnome-commander I find:
> 
> devices
> fav-apps
> gnome-commander.xml
> devices.deprecated
> fav-apps.deprecated
> (folder) plugins (which is empty)
> 
> As to remote connections... I had a major issue with that several
> years ago.  If I made a remote connection from g-c and saved it...
> g-c saved the password in PLAIN TEXT. Not good!  I then learned how
> to setup keys using seahorse (default gnome keyring tool). Now I can
> make an ssh connection from a terminal or from g-c without being
> prompted for credentials. g-c takes advantage of the stored keys as
> well.
> 
> g-c now stores the connections in ~/.gnome-commander.xml in this
> format
> 
>               <Connection name="t16" uri="sftp://address@hidden/";
> auth="2"/> <Connection name="t14" uri="sftp://address@hidden/"; auth="2"/>
>               <Connection name="t23" uri="sftp://address@hidden/";
> auth="2"/>
> 
> Much better!
> 
> For what it is worth, the way gnome handles keys and ssh connections
> needs some work. This is not a g-c issue but it will trip up g-c as
> well as trying to connect from a terminal.
> 
> As I would describe it, when I issue the command "ssh t16" (t16 being
> the name of the target host in /etc/hosts) gnome will connect to that
> machine using the appropriate IP address from /etc/hosts. In order to
> authenticate gnome uses my username and then tries every key I have
> stored locally until it finds one which will work.
> 
> The target host will get tired of this game after 5 or 6 bad keys and
> will then give my computer the digital middle finger "too many failed
> attempts" or something like that.  In order to have more than 5 keys
> stored locally I need to edit the /etc/ssh/sshd.conf file on each of
> my target machines and change (or add) this parameter with a number
> greater than the number of keys I have stored.
> 
> # Authentication
> MaxAuthTries 15
> 
> This is fine for a home network but in a corporate environment it has
> obvious issues.
> 
> That is all I have to offer at the moment. Please let me know if
> there is anything else I can look for to assist you.  I might also
> point out that there is a g-c users mailing list. You might want to
> ask your questions there as well (although I suspect that most folks
> subscribe to both lists as I do.)
> 
> Ken
> 
> p.s. Corresponding with a mailing list from my web mail client IS a
> pain. When I replied to YOUR email to the list, the web mail client
> inserted the list address as the TO. I had to go back and find your
> address, copy it, reply again and paste in your address.  I need to
> call my kid sister who used to moderate some mailing lists back when
> the Internet was the Internet - before all the Web stuff.  I think
> she used pine as her email program. Perhaps she can explain mailing
> lists to me. :-)
> 
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, November 18, 2018 6:07 PM, Michael <address@hidden>
> wrote:
> 
> > Hi Ken,
> >
> > I'm still with 1.4.8 from Debian testing as i lacked the time to
> > csv compile at some point; so maybe there was a major change. Or
> > did you simply not change any preference yet ?
> >
> > Anyway with my version, the gnome-commander file in .gnome2
> > contains some valid preferences; If i delete it, then for example
> > my color and font layoout is gone. But not the 'programs' and
> > devices and bookmarks AFAICS.
> >
> > I'm not quite sure how it works but it seems, the configuration
> > gets merged with ~/.gnome-commander/gnome-commander.xml, which
> > should be the 'new style'. For example, "Remote Connection" seems
> > to be stored in the xml but "New Connection" is stored in the
> > legacy file in gnome2.
> >
> > Both files seem to be written at app shutdown; if either of both is
> > missing, it gets recreated.
> >
> > Anyway, i'd need to take care about both with my version, or
> > upgrade.
> >
> > Just to make sure, you don't have any gcmd related configuration in
> > ~/.config either ? Because this would be the 'new style' location,
> > where all apps some day should store their confs. But many don't
> > yet.
> >
> > btw. nice idea to just block recently-used by write permissions.
> > But there's still a lot more noisy candidates. Essetially, you have
> > to look through all app data folders.
> >
> > gcmd-devel mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/gcmd-devel  



-- 
Die Frauen bringen jedes Abenteuer um seinen Duft, indem sie dem
flüchtigen Erlebnis Dauer gewähren wollen.
                -- Billy Wilder