Raspberry Pi: Some first steps to do

As I played around with the Raspberry Pi I saw that the VI editor was not working as it should. You were not able to use the cursor keys and the backspace key correctly. The reason is that normally Linux has installed VIM and not the original VI. So I first updated VI with the following command:

[codesyntax lang=”text”]

sudo apt-get install vim

[/codesyntax]

After that I installed the Midnight Commander as I find it more comfortable than just using the command line:
[codesyntax lang=”text”]

sudo apt-get install mc

[/codesyntax]

As my Pi will be reachable via the Internet  I do not want to have the standard user “pi” enabled. So I created a new user which also does not have sudo rights (in case someone gets access to my user password he still will need to have the root password in order to get root rights). So I used the following commands:
[codesyntax lang=”text”]

sudo adduser newuser 
sudo passwd root 
logout

[/codesyntax]

Now login again as user “newuser” and then change to root and disable the user “pi”:

[codesyntax lang=”text”]

su
usermod -L pi

[/codesyntax]

Now define an alias for the “ls” command to display files and directories in the long format and wih some color coding. For that edit the files “/home/newuser/.bashrc” and “/root/.bashrc” and add the following lines at the end:
[codesyntax lang=”text”]

alias ls='ls --color=auto'
alias ll='ls -la'

[/codesyntax]

By the way: To use the graphical programs of the Pi, you can start the LXDE-Panel with the command “lxpanel”. You will need a local XServer and XWindows redirection for that (I am using the great tool MobaXterm for that).

“Headless setup” of my Raspberry Pi 2 Model B

Yesterday my first Raspberry Pi 2 Model B arrived (I am glad that I have waited so long because I now could get the newest, faster version :-)).

I bought a package with the Pi, a power adapter and a small case and also a 32 Gb Micro SD card. I also ordered an USB Wifi Adapter (which has not yet arrived).

Here are my steps to get started with a “headless” installation (without a monitor or keyboard attached):

(more…)

“Plugin resource not found” error occurs when using Administration Console for Content Platform Engine (ACCE)

As I had that issue twice already and forgot the solution, I write it down here now 🙂

The issue is, that a search operation in Filenet Admin Console (ACCE) hangs if your browser language is set to a non-english language. Just set English as the default browser language and everything works again.

In SystemOut.log you see a message like that:

[codesyntax lang="text"]
ERROR [WebContainer : 7] - method name: determineBadClassRetry principal name: P8AdminT Global Transaction: false User Transaction: false Exception Info: Class "" not found. com.filenet.api.exception.EngineRuntimeException: FNRCE0002E: E_BAD_CLASSID: Class "" not found.
[/codesyntax]

This issue is already documented in that technote:

http://www-01.ibm.com/support/docview.wss?uid=swg21662794

IBM Connections with external Users: Bug in profiles_functions.js

I had the following problem with external users in Connections 5. The customer used a function for the “displayName” instead of a LDAP property value like “cn” resulting in the following lines in “map_dbrepos_from_source.properties”:

[codesyntax lang=”text”]

displayName={func_decorate_displayName_if_visitor}
displayNameLdapAttr={func_compute_dn}
decorateVisitorDisplayName= - External User
mode={func_map_ext}

[/codesyntax]

The function “func_map_ext” is a self-written function which just returns “external” so that all imported users will be handled as external ones.

While running a sync or populate job to import external users, the TDI job threw the following error message:

[codesyntax lang=”text”]

2015-02-12 18:02:22,244 ERROR [com.ibm.di.log.FileRollerAppender.5b5e0f8c-90a4-4b5f-a19e-0d3c6cc7777a] - CLFRN0104E: Failure during evaluation of mapping function for displayName. Exception is: Error while parsing script of eval() method, text func_map_ext}("displayName");

[/codesyntax]

It took some time to realize that function “func_decorate_displayName_if_visitor” in “profile_functions.js” is buggy.

In this function there was a mixup between the evaluation of the function for the “displayName attribute” and the function specified by the “mode” attribute. To fix that bug you need to change the following lines in “profile_functions.js”:

OLD:

[codesyntax lang=”javascript”]

if ((displayNameLdapAttrVal.length >= 3) && (modeVal.charAt(0) == "{"))
{
    var dispFunctionName = modeVal.substring( 1, displayNameLdapAttrVal.length - 1);

[/codesyntax]

 

NEW:

[codesyntax lang=”javascript”]

if ((displayNameLdapAttrVal.length >= 3) && (displayNameLdapAttrVal.charAt(0) == "{"))
{
   var dispFunctionName = displayNameLdapAttrVal.substring( 1, displayNameLdapAttrVal.length - 1);

[/codesyntax]

If you change these lines then you also can use a function for”displayNameLdapAttr”.

Security hole in Firefox and Chrome allows leaking of IP address

A security hole in Firefox and Chrome  allows websites to determine a web user’s real IP address, even when using a VPN:

“Firefox and Chrome have implemented WebRTC that allow requests to STUN servers be made that will return the local and public IP addresses for the user. These request results are available to javascript, so you can now obtain a users local and public IP addresses in javascript. This demo is an example implementation of that.

Additionally, these STUN requests are made outside of the normal XMLHttpRequest procedure, so they are not visible in the developer console or able to be blocked by plugins such as AdBlockPlus or Ghostery. This makes these types of requests available for online tracking if an advertiser sets up a STUN server with a wildcard domain.”

See more details here on this page.

https://torguard.net/blog/browser-security-vulnerability-may-allow-real-ip-leak/

On this site you can check if your broser is affected. With your VPN connected browse to this website and you should see your real IP address in addition to your VPN provider address:

https://diafygi.github.io/webrtc-ips/

How to fix:

For Google Chrome download and install this extension to disable WebRTC.

For Firefox goto “about:config” and set the configuration setting “media.peerconnection.enabled” to “false”.