Rickroll in the Terminal

This is a mostly useless blathering but since I got a good laugh out of it, I wanted to index this bit of fun and share it because that is what you do, right? Share nonsense on the Internet? Isn’t that why they invented the thing?

I was watching “Adrian’s Digital Basement” on YouTube and caught site of a device that had a repeating Rickroll animation. At first, I couldn’t remember what it was called and nearly hurt my thinking muscle in trying to remember it. After a bit of searching, I found a YouTube video of the actual music video of the “RickRoll”. So then I thought, I wonder if someone made this to run in the terminal. Sure enough, that is a thing.

I found this GitHub page here:

https://github.com/keroserene/rickrollrc/

I was incredibly amused.

Here is my warning and disclaimer, don’t ever copy some random text from the internet into a terminal and just run it. That is not in any way a good idea. Since I do lots of things that aren’t good ideas, I have done this and from what I can tell, it hasn’t destroyed my system.

To view a pixelated Rickroll in the terminal run this command:

curl -s -L https://raw.githubusercontent.com/keroserene/rickrollrc/master/roll.sh | bash

If you would like to share this with a friend and don’t want to give away what it is and surreptitiously get this person to run it in there terminal, use this command:

curl -s -L http://bit.ly/10hA8iC | bash

The obfuscation of the URL will aid in the process of “Rickrolling” your buddy… in the terminal.

As the GitHub site suggests, you could turn it into a script and further hide your true intentions when helping someone else out. Oh the fun that could be hand by wearing out a joke that was never that funny to begin with.

Final Thoughts

I totally realize that the “funny” of the Rickroll has long since passed on but this still gives me a chuckle and someday, someday, you can use it again on an unsuspecting technological enthusiast. I can think of all kinds of ways to shoe horn it in to the next time I give someone some advice.

References

Adrian’s Digital Basement YouTube Video with Rickroll in the background
Rickroll in it’s full Standard Definition Glory
Rickrollrc on GitHub

openSUSE + LibreOffice Conference 2020

openSUSE + LibreOffice Conference 2020

oSLO 2020 kicked-off on Thursday 15 October at 10h00 UTC with an opening address by The Document Foundation's Chairman, Lothar Becker.

openSUSE + LibreOffice Conference 2020
Screenshot from the opening session at the oSLO Conference

The conference was due to happen in Nuremberg, Germany, but because of the pandemic the plan was changed and the event went fully online. Three sessions ran simultaneously in virtual rooms. Two rooms hosted the short & long talks while the third room hosted the workshops.

During the opening session, as more people kept joining, the platform started to show signs of high load. People reported issues with the audio quality and some said that the page was not loading at all. Thanks to the Telegram group dedicated to the oSLO Conference communications, issues were being promptly reported and handled. Within a matter of minutes the organizers arranged to move the all sessions to The Document Foundation's Jitsi instance. The latter worked like a charm. The organizers and volunteers who helped in the swift transition did a great job.

openSUSE + LibreOffice Conference 2020
Jitsi instance provided by The Document Foundation

The conference room 1 easily held more than 80 participants at one time and there was no degradation in the quality of audio/video.

Getting started with Podman

I had my talk on Podman scheduled at 13h30 UTC on the first day of the conference. It went fine, except my poor timing of not being able to wrap it up as a short talk of 15 mins. I'll improve next time. 😉

I shared my slides on speakerdeck.com right after the talk.

Beer hour 🍺

The second day was even more fun. I hopped into the conference chat room from time to time to have a chit-chat with friends. It was not the same as having a geek talk over a beer during the conference after parties, but I was glad to see friends from the other side of the planet. I was happy to see that they are doing well.

openSUSE + LibreOffice Conference 2020
Where is Mauritius?

At one time during the beer chat, I was talking to two conference participants, one was from Taiwan and the other from Bulgaria. It is always funny to see people's reaction on how small Mauritius is compared to the other countries. Well, I am proud of the tiny dot in the middle of the ocean. 🇲🇺

Meet the openSUSE Board

The last session in the room 1 of the conference, on the second day, was held by the openSUSE Board members.

openSUSE + LibreOffice Conference 2020
openSUSE Board - October 2020

They provide updates and statistics about the project over the past year and tell us a bit about what the Board is planning for the future.

openSUSE + LibreOffice Conference 2020
What happened since last openSUSE Conference?

It is also the time when openSUSE members can ask questions.

The session was scheduled at 21h00 UTC which was 01h00 in the morning (the next day) for me. I was tired but I enjoyed the session. I jumped into the conversation when there was a comment about having a diverse representation on the Board with people from different parts of the world. I commented as an official of the Election Committee, encouraging members from all parts of the world to step up & run as candidate or nominate someone for the next Board election.

See you next year!

Italo Vignoli, founding member of The Document Foundation, during the closing keynote of the openSUSE + LibreOffice Conference (oSLO 2020), asked participants to share comments on how to improve the conference experience. He pointed out that this might not be the last virtual conference, considering the pandemic, although we all would love to have a physical conference soon.

Kudos to the organizers and volunteers for a successful conference. 👏

WTTR.in | Weather Forecast in the Terminal

In the spirit of using this site as my public facing notebook. I sharing with you and future me, what might be, the most beautiful terminal based weather forecast application wttr.in. Rather than babble endlessly about all my reasons for my love for the terminal, I am going to link you here to my Tmux blathering.

There is nothing to install, unless you don’t have curl but that is pretty standard fare on a modern Linux distribution. If you do not have curl, please consult your distribution instructions on getting it installed as with openSUSE it is there automatically.

I also want to note, most people, normal people, will just glance at their phone and be done with it. I, however, am not most normal people as the mobile form factor is not my favorite place to do anything.

How to Use It

Since there is nothing to install, this is a down and dirty on how you use it. You can get all the details by going to the project GitHub site and learn much more about its extended features, extensive options, and details of its inner workings.

The easiest way to view this weather information can be done just by navigating to the the website which will display the information in your browser. This is not personally interesting to me but possibly the best options available for viewing the weather.

http://wttr.in/

The more fun way to view the weather is right there in the terminal. Open you favorite terminal emulator or drop down into a TTY and it works.

This is all you have to do and it will just give you weather information.

curl wttr.in

It will use your IP to get the weather near you. For most people, this will probably be good enough.

For those that use a VPN may find that this doesn’t work for them. In this case you will have to specify the specific location where you want the weather forecast. Spectacularly, you can use the city name or the postal code. For example

curl wttr.in/kalamazoo

works just as well as

curl wttr.in/49001

Something of note, cities in the USA or across the world are not exactly unique. If I wanted the weather of Portage, MI and just typed

curl wttr.in/portage

I would get Portage, Indiana, presumably because it may be geographically closer to my location than Portage, Michigan. To be more specific, the appropriate syntax is this:

curl wttr.in/portage+michigan

Display Units

WTTR.in is set to default to your regional unit format but this can be over ridden. This can be done with adding ?u for USCS used in the United States or ?m for the rest of the world. An example of how that would be used to get metric in the United States.

curl wttr.in/kalamazoo?m

Final Thoughts

What is very cool about this, up to date weather information is readily available to any computer with a terminal, internet connection and curl which is what makes this very interesting and useful to me. It is a service that does not limit or wall off anything. It is there to be used.

I am only scratching the very surface of this incredibly versatile terminal weather application. It should be noted that because it is a terminal application and is extensible, you can very much make it more than just a basic text-based output. For my purposes, today, this is all I want but with a little imagination, marvelous things can be done with it.

This small blathering is very much for me, as I do recall this application from years back but have since forgotten the details about it. In my not so recent searching for terminal weather applications didn’t present this information so this is my gift to you and future me.

References

WTTR.in Project GitHub Page
Tmux Desktop on openSUSE Linux
Terminal Weather in the Browser

Oct 17th, 2020

Noodlings | No Linux for 10 Days

20th Noodling, just like the previous, delivered inconsistently!

The 20th cookie sized podcast, but not one of those oatmeal raisin type of cookies, more like something with chocolate chips.

Chinese food containers are a feat of clever engineering. Most people just toss them in the bin once they are done with them but if you stop to look at how they are folded together from wax coated paper, you have to smile and marvel at the ingenuity of this clever, nesting box.

Element | Matrix Chat Client

The Element client makes using Matrix quite enjoyable. Previously, using Matrix was a bit of a lack-luster, almost a science experiment kind of feel to it. Sure, it worked but it didn’t have the polish and great user experience I have using Telegram. I can say, with much confidence, using Element feels like a real product. It feels just as good as any other messaging client. It is still early days for me so it’s still all new and exciting.

Send and Receive Text Messages SMS with Element

Amiga Fast File System Return to Linux Kernel

A component of the Linux kernel for the Amiga Fast File system had been broken that deals with the basic permission bits, protection bits in Amiga OS. The Linux Kernel would only set bits but never delete them.

Max Staudt is the developer that noted this issue and submitted a fix “for good” such that this won’t be an issue in the Linux Kernel any more. He said, “…Linux a nd classic AmigaOS can coexist in the most peaceful manner.”

Linus Torvalds appears to have agreed and the code made it into rc4 of version 5.9 which is slated to be release this month, October 2020.

This is great news for those of us that are vintage tech enthusiasts.

VisualBoy Advance

I was in a situation where I was away from home for an extended period of time. As a result I was separated from my old tech which means authentic hardware to do the more retro style of gaming that I enjoy. While away, I had a hankering for some GameBoy fun to unwind at the end of the day. The application I found, which I ultimately installed from the Snap Store was VisualBoy Advance. The big take away on why this is a great application for playing GameBoy and GameBoy Advance games is the ease of use and how highly configurable it is.

Dell Inspiron 20 3048 Black Screen Repair

Power outage left me with a computer where the LED on the side would show activity but there wasn’t even a flicker on the screen itself. It was out, completely black, no light whatsoever.

Ultimately the issue came to a faulty power supply which tells me that I need to take the time to put in some sort of UPS to protect it in the future. This isn’t the first time I have had issues with this computer as a result of power fluctuations.

No Linux for 10 Days

In my time away from my normal life, I was in a situation where I was without Linux for almost two weeks. I hear of people that consider time away from tech as being “refreshing”. I wouldn’t consider that the case at all but it was enlightening. Using “analog” methods for recording information is super inefficient but it did force me to work on my hand writing as it is atrocious.

Secondly, having to use Windows 10 to do “digital work” was so frustrating, I will say, the points of frustration were not all the fault of Windows 10 but it did make me greatly despise using tech. It confirmed that if Linux went away and I was forced to use Windows 10, I just wouldn’t.

BDLL Followup

There was a discussion about the perfect distribution that dominated the majority of the the conversation. I can easily say that openSUSE fits as the perfect distribution. There isn’t much I would change about it. The only thing I can think is a little polish in Tumbleweed as such that it becomes real easy to do distribution updates, preferably, using Zypper.

openSUSE Corner

openSUSE + LibreOffice Conference

Going on now is the openSUSE + LibreOffice virtual conference. There is one day left but you have to register before participating as to keep out spammers. There are two virtual rooms where talks are given and a workshop room to hack on LibreOffice. Thinking about this, there is an element missing from the event. There isn’t a virtual hall way to get lost in and have random conversations about of topic subjects. Maybe Next time?

It’s nice to see that virtual conferences are still happening. Just because the world has hit a rather large bump, not all the wheels have fallen of of the wagon.

Join our team and help us improve the openSUSE learning experience!

openSUSE is a project that has many parts to it and with the very lively and thriving community, some things can become untidy. The project has multiple distributions, although Leap and Tumbleweed get more of the mind share, things can become a bit overwhelming for someone new to start poking around the openSUSE spaces.

This is why a group of volunteers have taken up the task of improving the learning experience for users regardless of their experience level. We want to make sure that new users can best identify solutions for their requirements and experienced users have the detailed documentation that is easy to access and update.

Any help is welcome for writing, editing, peer-reviewing, video production and testing.

Tumbleweed Roundup

  • 20201008 moderate 90
    • MozillaFirefox (80.0 -> 81.0.1)
    • inkscape
    • kdeconnect-kde
    • libzypp (17.25.1 -> 17.25.2)

https://review.tumbleweed.boombatower.com/

Computer History Retrospective

Computer Chronicles – Super Computers (1984)

Oldest computing machine is the abacus

Massive Parallel architectures was the key feature of these massive super computers. It is interesting to see that the super computer technology of this time is essentially the architecture that would later be adopted by the average home computer, to include your mobile device.

These computers were rated at over 100 million calculations per second. I wanted to get some kind of a baseline comparison to a modern Threadripper but getting actual “calculations per second” isn’t a thing with modern benchmarks. I would be interested in see how one of the old Cray super computers of the mid-1980s would compare to the average gaming desktop computer of today. It’s worth a wonder.

Parallel processing was a big thing with these super computers but the rate of improvement had slowed down and the discussion boiled down to the next breakthrough coming in changing the way things are done and different algorithms to take advantage of greater speed increases.

It was initially by government grants that breakthroughs in super computers came about and once better understanding and more applications were developed for the super computer did the commercial applications jump on board to better simulate a 3D world for testing such as the automotive and oil industry. Ultimately, making the process of being profitable much quicker.

Barriers at the time is building better algorithms to map on a computer’s architecture while at the same time, modifying the architectures to work with the algorithms. There was such a massive number of changes and experimentation in this time. The US and Japanese manufacturers were competing against each other at the super computer level. Both governments investing in the private sector to help with R&D costs. Really a spectacular time in the history of computing.

Final Thoughts

Take some time to appreciate some of the marvels around you. Even something as ubiquitous as a to-go container has an incredible story behind it. Someone or many someones spent many hours engineering the shape and the design of the thing as well as the many hours or perhaps years it took to perfect the manufacturing process. We often take for granted the wonderful luxuries we have.

openSUSE Tumbleweed – Review of the week 2020/42

Dear Tumbleweed users and hackers,

This week, the openSUSE/LibreOffice conference has started, but Tumbleweed did not let itself be stopped by that. During this week, we have seen 5 snapshots being published (1008, 1009, 1011, 1012, and 1014).

The most relevant changes included:

  • Mozilla Firefox 81.0.1
  • Linux kernel 5.8.14
  • LibreOffice 7.0.2rc2
  • GNOME 3.36.7
  • KDE Applications 20.08.2
  • KDE Frameworks 5.75.0
  • KDE Plasma 5.20.0

This is mostly as announced last week about the upcoming things. This leaves us currently with these major changes left in planning/staging:

  • GNOME 3.38.1 (mozjs78 has since been improved, but is not yet available in Tumbleweed)
  • Mesa 20.2 (The transparency issues seem to be fixed in combination with Plasma 5.20.0, so it’s shaping up well)
  • openssl 1.1.1h (neon (gh#notroj/neon#38 issue still valid, but the maintainer debugged and accepted the test failures)
  • openssl 3.0 (long-term; no progress in the last few weeks)
  • RPM 4.16: steady progress made with package fixes.
  • nasm 2.15.4: breaks dav1d, firefox, and thunderbird (which both ship embedded dav1d)
  • libmicrohttpd 0.9.71: breaks pcp and libyui
  • jsoncpp 1.9.4: breaks libyui

Oct 16th, 2020

YaST Team posted at 05:00

Digest of YaST Development Sprint 110

In this sprint, the YaST Team has been working on a wide range of topics. You can find more details in this list that we have prepared for you:

Nested Items in Tables

As usual, we are already working on the following sprint. We will publish another report, including some interesting details in roughly two weeks. Until now, stay tuned and have a lot of fun!

Modern Computer in a Commodore 64 Shell

Of sorts.

The Commodore 64 was my first computer and there is something about the classic, beige bread-bin shape that brings a kind of retro-excitement. I have many fond childhood memories of flicking the switch on the side of the case where I was greeted with that “Ready” prompt and the blinking cursor on the light gray field… You see, I had a 13 inch, wood grain black and white TV that I mostly used with this fine machine. Only on special occasions did I get to enjoy it full color on the family TV in the living room. When I did though, that blue screen would fill the room with near endless possibilities of electric joy and hours of entertainment. There hasn’t ever really been an experience quite as exhilarating, as a child then when I learned how to input those load commands and hear the 1541 disk drive come to life with the warm sound of heads seeking over the spinning disk. To this day, when I use that disk drive, it takes me back to those bleak winder days where I would cozy up to hot cocoa and Commodore 64 delight.

Although, today, I do keep a real Commodore 64 running and use it from time to time, often wish there was a modernized version of that bread-bin shell so that I could enjoy a flavor of computer goodness performing “modern” computational work loads. It almost came to pass, some years back as there was a project from Commodore USA where you could buy a computer that ran a modified version of Linux to look and feel a bit like the Commodore 64. I searched far and wide to get one of these cases to build myself a modern computer in the style of the Commodore 64. Why? Mostly… just because of the smiles that the computer brought me and the smiles I would like to continue to have, day in and day out.

As it goes, a few days ago Matt, one of my co-hosts on DLN Xtend send me this link where I was greeted with what what I assumed would remain unobtainable and I nearly fell out of my chair in excitement. It appears that an industrious entrepreneur from the UK managed to acquire the website, molds and some stock from the now defunct CommodoreUSA and is offering the sale of Commodore 64 styled enclosures.

The long term plan for My Retro Computer is to sell complete systems but the short term is to sell cases, presumably to build up some capital and take the next step. The Commodore OS that was developed by CommodoreUSA is available for download. I am not really interested in this as my it is now pretty far out of date and I much prefer to shoe-horn openSUSE on all my computer things.

Key Features

I am not going to make this an exhaustive list of every feature of this retro case. I want to keep this short and not an endless blathering of my excitement. There are three key features of this machine, as I see it:

Number 1

The retro styled case. I can see this as being the natural progression of the original Commodore 64 bread-bin case. The same basic shape but taking into account modern hardware and in this case, taking a mini-ITX motherboard, a slot for optical media on the left side and the right side having a multi-format SD card reader.

Number 2

It comes with the keyboard that is a low noise, USB, mechanical, Cherry Switch keyboard. Just based on the description, this isn’t an inexpensive keyboard. Cherry Switches are well known by the keyboard enthusiasts and although I am not a keyboard snob, I do like a quality, modern keyboard and mechanical switches are known to last longer than many other variants. The fact that they took modern components and arranged them in such a fashion that removes the annoyance of the cursor keys and gives you a full 12 Function keys along the top is very welcoming.

Number 3

Prominently displayed on the key features section on the MyRetroComputer.com site, it boasts Linux compatibility (with other things that are far less cool). Although this goes without saying, since it is nothing more than a case with accommodations for standard components, what it does mean is that this computer is “future proof.” That means, I can build it, and rebuilt it again as the component standards are essentially used in perpetuity. Standards may not be fun on the surface, but they can make for so much fun in other aspects in the sense of unleashing creativity.

What I would Do With It

I have thought a lot about setting up a workstation that would generally stay put in my “SuperCubicle.” separate from my AMD system I recently assembled. This would be a fairly low cost build and I would use the monitor I already have in place. I envision this machine to be more of a production machine that would be set up for recording, graphic design, etc. That would free up my laptop to do more mobile tasks. I would call it my “anchor system” as it were and it would fit my enthusiasm for vintage tech and my almost unhealthy obsession with openSUSE Linux all in the same package.

That Windows machine isn’t there anymore, nothing is there currently, perfect spot for this machine.

Pricing It Out

Obviously, there are cheaper ways to accomplish this that are probably more pragmatic but the joys in life are not all pragmatic at all. For instance, my Linux powered festive lights is not really practical at all from a certain perspective but it brings me a lot of joy, all year. In a similar fashion, this would bring daily fun to my desktop experience. It wouldn’t be the exact childhood experience with all the same warm sounds but it would be some of the feel along with the modern conveniences. I decided to do some digging and estimate what it would cost me to build my ultimate retro-modern computer.

Case

The case is about $250. On the surface, this doesn’t seem like a good deal but when put into perspective, it’s not so bad. A Cherry switch keyboard can range from $40 to $200 depending on the grade of switches. This is also a very custom layout with only the switches themselves being off the shelf. The rest of this is very custom. Even if we are going mid-grade here, but taking into account the very custom nature of this layout, lets say this is an $100 keyboard. Maybe it is a little on the low side, I don’t really know for sure. Take that into account that would make the case about $150 and that, to me, is reasonable, considering the niche nature of it.

Motherboard

Doing some searching, and I haven’t actually decided on a board yet. Just some quick searching, there are some gaming mother boards that are not so expensive, even some kits out there but I don’t see how I would be able to add a graphics card to this setup, so I would certainly get an AMD motherboard to take advantage of the power of the Ryzen processors with . between $60 and $80 that would fit the bill quite nicely and give me a lot of use out of it.

CPU

Since I am going with an AMD based system, so long as there is the room for a decent cooler, I am currently interested in a Ryzen 5 3400G with the RX Vega 11 integrated graphics. It should be at least 50% faster than my Dell Latitude E6440 with the i7-4900MQ. Practically speaking even better considering the cooling limitations of the laptop form factor. I am looking at about a $160 price point here.

Memory

I wouldn’t go with, at a minimum 32 GiB of RAM and I am estimating about $120 for two 16 GiB sticks of SDRAM. I would probably just get 2 sticks and leave the other two open to double the memory down the road.

Cooling

I would get a 40mm case fan and some kind which would cost around $6. The CPU cooler would have to be low profile enough to fit in this case and the options I have seen are in the price range of about $50, depending on the design.

Power Supply

Here is where I am uncertain the implementation of the power supply. Looking at the case, it almost appears that the power supply is expected to be external. The cost for internal power supplies are around $50 but here I need to do a little more research.

Operating System

This is kind of a no-brainer as I will of course use openSUSE Tumbleweed running the Plasma Desktop. There really isn’t another choice. I would have access to all my retro system emulators and productivity software so it would just, frankly be perfect for my use case. The reality is, just about any Linux distribution would be great

Final Thoughts

This Commodore 64 retro computer case plus openSUSE Linux with a little mix of DIY is a perfect mixture of Linux and vintage tech enthusiasm with a dash of my almost unhealthy obsession of openSUSE Linux. It just all comes together here.

I have often heard from some people that standards aren’t fun or standards restrict too much. I think this idea is rather absurd as it is the “restriction” of standards that give us the framework to support the freedom to create new and interesting things. Everything from this “Modern” Commodore 64 case to house standard components is cost effective because of the standard interfaces. I think we can see evidence of this everywhere. This can be everything from programming languages to graphical widget toolkits. Not to say that standards need to be static but having a solid foundation from which to build allows for wonderful and interesting creations. The Commodore 64 Retro Case is just one example of it.

References

MyRetroComputer.com Home
Commodore USA OS
https://www.xtremegaminerd.com/ryzen-cpus-with-integrated-graphics/


Syslog-ng and Security Onion

One of the most interesting projects utilizing syslog-ng is Security Onion, a free and open source Linux distribution for threat hunting, enterprise security monitoring, and log management. It is utilizing syslog-ng for log collection and log transfer and uses the Elastic stack to store and search log messages. Even if you do not use its advanced security features, you can still use it for centralized log collection and as a nice web interface for your logs. But it is also worth getting acquainted with its security monitoring features, as it can show you useful insights about your network. Best of all, Security Onion is completely free and open source, with commercial support available for it.

From this blog, you can learn how to get started with Security Onion in evaluation mode. This does not mean any limitations, just a simplified setup where all services are installed on a single host. That said, for a production environment, a distributed installation is recommended instead.

Before you begin

To install Security Onion, you need a (virtual) machine with at least 8GB of RAM and some storage space. I went with the usual 20GB storage offered by Vmware Workstation by default, but you might need more if you store more logs or want to do stress testing. Also, you need syslog-ng running on another machine to send some test logs to Security Onion.

Installing Security Onion

First, download the installer CD. The download location of the latest installer and instructions on verifying the downloaded ISO file are available at https://github.com/Security-Onion-Solutions/security-onion/blob/master/Verify_ISO.md. Once you downloaded the installer, follow the installation instructions from the Quick Evaluation page. You can test your freshly installed system by clicking the Kibana icon on the Security Onion desktop and logging in with the user name and password you just configured. Note that at this stage, you cannot reach the web interface remotely.

Before doing any further configuration, update your system. Instead of using the regular distro tools you should use “soup”, the Security Onion updater which updates not just the base operating system, but also the containers, and makes sure that everything is restarted along the way. You might need to reboot the machine at the end.

Opening ports on the firewall

By default, only port 22 (ssh) is open on the freshly installed system. To send logs from remote systems and to access the web interface from other hosts, you need to open up two ports on the firewall. Luckily, you do not have to deal with iptables directly – Security Onion has an easy to use command line tool for that.

Running “so-allow-view” lists the already open ports. Right after installation, only port 22 is listed here.

You can use the “so-allow” command to open ports. From the list, you should choose “analyst” and “syslog device” and the IP address or range where you plan to access those ports. You can add your local network in a similar format: “192.168.3.0/24”. After adding the extra ports, you should see something similar:

root@czanik-virtual-machine:~# so-allow-view

=========================================================================
UFW Rules
=========================================================================

To                         Action      From
--                         ------      ----
22/tcp                     ALLOW       Anywhere                  
514                        ALLOW       192.168.3.0/24             
22,443,7734/tcp            ALLOW       192.168.3.0/24           
22/tcp (v6)                ALLOW       Anywhere (v6)             


=========================================================================
Docker IPTables Rules
=========================================================================

To  		 Action From
--               ------ ----

Configuring syslog-ng

As a test, configure at least one additional host to send its logs to Security Onion. In syslog-ng, the following configuration forwards all local logs to Security Onion. Check your syslog-ng configuration for the name of the local log source (“src” is used on SUSE systems). Of course, the target IP address will most likely be different in your environment:

destination d_tcp {
  tcp("192.168.3.136" port(514));
};

log {
  source(src);
  destination(d_tcp);
};

Append it to syslog-ng conf, or drop it with a .conf extension in the /etc/syslog-ng/conf.d/ and reload the configuration.

Testing

Once the new syslog-ng configuration is live, you are ready for testing. A few logs from the remote system will most likely show up in Kibana within minutes, if you are patient. You can also use the “logger” command to make sure that you have some test messages:

logger this is a test
logger bla bla bla

Now, that the firewall for the web interface is open, you can check the results in two ways. Either by logging in to the Security Onion desktop and start Kibana from there, or by accessing the web interface remotely. Note that port 80 is closed, so there is no redirect to a secured port – you need to enter “https://” in front of the IP address (or host name) to access it. The opening page is available without authentication, but you will need to enter your user name and password to access Kibana.

By default, you will see a dashboard on screen, with the focus on IDS results. You can reach syslog messages by clicking the “syslog” link at the bottom of the left-hand side menu.

What is next?

Log management is just one of many features of Security Onion. You should check out others as well as they could provide you with much better insight on what is happening on your network. This blog showed you just a quick way to get started with syslog-ng and Security Onion. If you would like to use it in production, you will need more nodes and careful planning.

If you have questions or comments related to syslog-ng, do not hesitate to contact us. You can reach us by email or chat. For a list of possibilities, check our GitHub page under the “Community” section at https://github.com/syslog-ng/syslog-ng. On Twitter, I am available as @PCzanik.

Find out more about the openSUSE + LibreOffice Conference

The openSUSE + LibreOffice Conference organizers are thrilled to begin the conference and hope everyone has a great time.

To get attendees more accustomed to the event, we are publishing some resources and info that will help people joining this year’s conference.

Registration for the conference began yesterday on oslo.gonogo.live.

The Schedule for the event can be viewed on events.opensuse.org. The opening session begins at 10:00 UTC. All talks are scheduled in UTC time. The rooms of all the talks will open five minutes before the talk begins. Collabora’s Michael Meeks will deliver a keynote at 10:30 UTC. Another keynote from SUSE’s Markus Noga about the Powering of Jump will be at 14:30 UTC.

Registration

After registering, it is IMPORTANT to check your email (check spam) for a link to activate your account. Then login to the system using your full email address and password. If you get a 500 error, it’s likely your password will need to be a strong password.

Most users will default to an all sessions area after logging in where they will be able to “add” the sessions they would like to view. The sessions are listed in Alphabetical order. You will only be able to view sessions that you joined.

The events.opensuse.org site and oslo.gonogo.live site are not connected, which could be confusing. The good new is we have people at on a telegram channel and #LiboCon channel on IRC that can help people who are having an difficulties with signing up and logging in to the platform. There is also a tour option located in the upper left menu. Please take the time to go through the tour.

Join Session

After selecting the session, navigate to EVENT HOME and scroll over the presentation area. There you will see a “little green door” in the bottom left of the presentation area that will have a join session appear. This can be seen in this screenshot Join Session.

All users enter in mute. Please keep muted unless you are one of the speakers. A RED microphone means you have a hot/open mic. You can share your camera if you would like.

Leave Session

To join another session, users must leave session the session you’re in. Click on the same “little green door”, which should be yellow when you are in a session.

##Fedora and openSUSE Users Make sure you have the media codecs needed on your system. Chrome is a good browser for this for those who are using non-Linux systems. If you’re using Fedora and the conference doesn’t show video for you, set things up as described at https://fedoraproject.org/wiki/OpenH264. For openSUSE systems, check https://en.opensuse.org/SDB:Install_Packman_codecs.

LibreOffice has made a simple list of resources for the conference. Enjoy the conference and we look forward to seeing you wherever you are throughout the world and please don’t forget to use hashtag oSLO2020!