Javlog @cacek.cz

It took me some time to get Lexmark CX410 network scanning working on my Ubuntu (16.04 LTS). Scanning programs were not able to discover the device even if the correct driver was installed. So here are some troubleshooting steps, you can try if you also experience some problems with the network scanning. Download and install the driver Download network scan driver for CX410 from Lexmark support page support.lexmark.com install it: sudo dpkg -i lexmark_network-scan-linux-glibc2_12212015_x86_64.deb And now add the secret ingredient . Link the installed drivers to a proper location : sudo ln -s /usr/local/lexmark/unix_scan_drivers/lib/sane /usr/lib/sane Installation verification $ scanimage -L device `lexmark_nscan:libnet/SPECIFY_DEVICE' is a Lexmark Network Scanner device `lexmark_nscan:libnet/0021B76D22F6' is a Lexmark Lexmark CX410de Ethernet Scanner```

Hooray, we have already a simple way to enable Elytron accross all the default server profiles. The JBoss CLI script was added to the application server distribution! You can find it in the docs/examples/enable-elytron.cli file. Download the WildFly nightly build as was shown in the last entry and then let's just execute the CLI script: bin/jboss-cli.sh --file=docs/examples/enable-elytron.cli That's it :)

Steps to enable Elytron in WildFly nightly builds. There is an ongoing effort to bring a new security subsystem Elytron to WildFly and JBoss EAP. For some time a custom server profile named standalone-elytron.xml  existed beside other profiles in standalone/configuration directory. It was possible to use it for playing with Elytron. The custom Elytron profile was removed now.  The Elytron subsystem is newly introduced to all standard server profiles. The thing is, the Elytron is not used by default and users have to enable it in the subsystems themselves. Let's look into how you can enable it. Get WildFly nightly build # Download WildFly nightly build wget --user=guest --password=guest https://ci.wildfly.org/httpAuth/repository/downloadAll/WF_Nightly/.lastSuccessful/artifacts.zip # unzip build artifacts zip. It contains WildFly distribution ZIP unzip artifacts.zip # get the WildFly distribution ZIP name as property WILDFLY_DIST_ZIP=$(ls wildfly-*-SNAPSHOT.zip)...

Po loňské pauze se mi opět podařilo dostat na ne konferenci jOpenSpace, která probíhala o víkendu 7.-9.10. kousek od Pelhřimova. V průběhu víkendu měl každý z účastníků vyhrazených 10 minut aby osvětlil (lightning talk formou) své téma. Já jsem prezentoval projekt  Sunstone , kterému jsem se věnoval v uplynulém roce v souvislosti s testováním JBoss EAP v cloudech a v Dockeru. Program konference na  svém blogu shrnul Jarda Holaň, takže já zmíním jen krátce co mě zaujalo a jaký jsem měl z celého víkendu dojem. Bezpečnost Mile mě překvapilo, že několik prezentací bylo zaměřeno na bezpečnost a její testování. Já jsem si při nich do svého TODO-listu připsal položky: projít si WebGoat (deliberately insecure web application maintained by OWASP) vyzkoušet Burp Suite na penetrační testování Headhunteři V pátek při večeři probíhala zajímavá diskuse s klukama ze společnosti Zeebra Recruiting, kteří nám dali nahlédnout pod pokličku svého zaměstnání. Mluvilo se o tom,...

If you realize at some point of your bright Azure future you don't remove VM disks correctly (like me in JCLOUDS-1170 ) you'll probably want to do a storage account clean up. Here is, how I did it on my linux desktop using Azure CLI. As I wanted to keep some private OS images which were located in the storage account too, I moved them first into a newly created storage container. # Prerequisities installed azure-cli (I personally use the latest docker image microsoft/azure-cli with the tool) installed jq tool for parsing JSON # Set up STORAGE_ACCOUNT=" PutYourStorageAccountNameHere " STORAGE_KEY=" PutYourStorageAccountAccessKeyHere " # Move/backup OS images to a new container # create new storage container for OS image blobs azure storage container create -a $STORAGE_ACCOUNT -k "$STORAGE_KEY" os-images # linux images to be kept for IMG in eap-7-rhel-7.2 eap-7-rhel-7.2-service; do ORIG_BLOB=$(azure vm image show...

This entry describes one of possible ways how to create SSH-able Windows image with JBoss EAP 7 installed on MS Azure cloud (classic VM mode - asm). It's written mostly as commands with some comments - use your imagination (or a boring documentation), when you're not sure what does it do. If you use these step, then do it carefully - it disables the firewall for instance! Don't forget to change the USER_PASSWORD value! # Prerequisites # Azure CLI - install and configure classic mode # install either Azure CLI for your system or use Docker image provided by Microsoft # sample script for the Docker version: https://gist.github.com/kwart/ffd6dc34bb8d5e297bc34ce10764bfe6 # login and configure classic mode azure login azure config mode asm # Create Azure storage account (with container for the image) # Create VM from public Windows image # name of virtual machine used to prepare new OS image export AZURE_HOST=eap7-prepare # target image name export ...

Use following script to create rule, which disables wifi if the ethernet cable connection is up. The solution is based on this stackoverflow article . sudo cat > /etc/NetworkManager/dispatcher.d//99-disable-wifi-if-not-needed <<EOT #!/bin/bash if [ "$1" = "enp0s25" ]; then case "$2" in up) nmcli radio wifi off ;; down) nmcli radio wifi on ;; esac fi Replace the enp0s25 with the correct "cable" interface if needed.