Linux Format forumsHelp, discussion, magazine feedback and more2015-08-02T18:35:10+00:00http://www.linuxformat.com/forums/feed.php2015-08-02T18:35:10+00:002015-08-02T18:35:10+00:00http://www.linuxformat.com/forums/viewtopic.php?t=17027&p=116922#p116922Statistics: Posted by nelz — Sun Aug 02, 2015 6:35 pm
]]>2015-08-02T17:32:24+00:002015-08-02T17:32:24+00:00http://www.linuxformat.com/forums/viewtopic.php?t=17027&p=116921#p116921but it was not available in binary form on Mageia 4 neither is it on Mageia 5 (just reviewed).I tried compiling it from source and overcame a couple of dependency issues before becoming stuck at this point:

[root@albury simon-0.4.1]# ./build.sh-- Found Qt-Version 5.4.0 (using /usr/bin/qmake)CMake Error: The following variables are used in this project, but they are set to NOTFOUND.Please set them or make sure they are set and tested correctly in the CMake files:QT_QT_INCLUDE_DIR used as include directory in directory /home/alan/Programs/simon-0.4.1/build/CMakeFiles/CMakeTmp

]]>2015-08-01T21:08:56+00:002015-08-01T21:08:56+00:00http://www.linuxformat.com/forums/viewtopic.php?t=17025&p=116919#p116919You can try running ssh with -vvv but you may get more useful information from the logs on the server. SSH in from a wired connection and follow the logs while trying to connect from the wireless system. It may help to change the LogLevel in /etc/ssh/sshd_config to VERBOSE and restart the server.

This happens when the client is on wi-fi, but not when it is wired to the network. Clearly, it's got nothing to do with the keys - sorry about that - but why would a wi-fi connection (suddenly) behave like that?

It would be nice to know what belongs to which DE so that I can get rid of XCE4 and ensure that Unity behaves. Starting to wonder if I shouldn't have done this the other way around and added low latency kernels to Ubuntu 14.04, but I was afraid thatere would be too much configuration involv ed to get Jack and the other bits working properly.

]]>2015-08-01T10:26:52+00:002015-08-01T10:26:52+00:00http://www.linuxformat.com/forums/viewtopic.php?t=17023&p=116916#p116916The font characters do appear in some tools - but not others. Font Manager, Character Map and LibreOffice Writer disagree about which characters they can preview for me - only Writer's Special Characters tool previews them all. I cannot enter them into my text processor, and if I copy-paste from Writer they revert to their Latin equivalents.

I wondered if the problem was because my desktop uses Unicode and these fonts are incompatible. Many "dingbats" (standardised pretty things other than language characters) are actually in the Unicode standard, so I installed Erler Dingbats, which is Unicode. (BTW it has a free-use license but does not allow redistribution so distros and apps can't bundle it in. You have to download it yourself from http://www.ffdingbatsfont.com/erler/ErlerDingbats.zip )

Writer handles this just fine too. And they even appear correctly in my text editor - my Unicode desktop works, hooray! However I have to copy-paste them from Writer.

Font Manager and Character Map still barf on them - boo! So the mystery there remains.

fede wrote:Today one of them was denied access with a message about failed key matching (things were fine until yesterday, when we had our Internet access went down until this morning). Looking at .ssh/authorized_keys it turns out that this particular computer has two different entries (I don't really know how that happened). I thought (ac

If your public/private keys don't match then the remote host won't tell you that the keys don't match (that would be giving away too much info to a potential hacker, i.e. "Hi Hacker, you guessed the right username so stick with it and try another ssh key or password") it will just give you an access denied message. The only scenario I can think of where it will tell you that a key doesn't match is if the host key on the remote server has changed, in which case ssh is warning you that the machine you think you're connected to isn't the one that you have previously stored the key for, though when this happens it usually asks if you want to accept the new key and proceed (though I think this behavior can be disabled by ssh options). This can happen for a number of reasons, such as resinstalling ssh on the remote server, moving the IP address onto another server, or some miscreant spoofing the address of your server and it's not the one you're trying to reach. When you ssh into a remote machine it stores the remote host's key in your .ssh/known_hosts file, so check the entries in there, and do a "ssh-keyscan remotemachinename" and see if the host key returned by that is in your known_hosts file.

]]>2015-07-31T09:07:05+00:002015-07-31T09:07:05+00:00http://www.linuxformat.com/forums/viewtopic.php?t=17025&p=116911#p116911While you are booted from the live CD, have a look in the system log on the server to see if any reason is given fr refusing access. It is also worth checking the ownership and permission of the file, it must be own by the user you are trying to login as and the permissions should be 0600.

]]>2015-07-30T23:54:09+00:002015-07-30T23:54:09+00:00http://www.linuxformat.com/forums/viewtopic.php?t=17024&p=116909#p116909Statistics: Posted by nelz — Thu Jul 30, 2015 11:54 pm
]]>2015-07-30T23:53:34+00:002015-07-30T23:53:34+00:00http://www.linuxformat.com/forums/viewtopic.php?t=17025&p=116908#p116908I thought I could delete the whole double record and start from scratch, but I am not sure if that's safe (and, besides, am I correct in assuming that the record is delimited by ssh-dss ... ending in == user@host?). Any suggestions? Thank you.

P.S.: turns out this problem came up with all laptops connecting via Wi-Fi. My desktop, which is Ethernet connected is communicating just fine. I suppose that the failure to do POP access via STARTLS (SSL works) is strictly related. Is it maybe time to erase the whole .ssh/authorized_keys file and start afresh? Thanks