Wndows antivirus utility kills mail foldeers on Tnunderbird

virus which are transmitted w/o encoding cause entire mail files to be killed by stupid windows anti virus.

here is a discussion of the problem and how to cure it on various platforms.


https://wiki.mozilla.org/Thunderbird:Testing:Antivirus_Related_Performance_Issues

veracrypt build notes

building veracrypt 1.23 on arm.

https://www.veracrypt.fr/en/Documentation.html

https://www.veracrypt.fr/en/Downloads.html

A bit outdated note on how to with wxwidgets (needed for build)

change reference from 2.8 to 3.0 (which is  rev required to build veracrypt)

how-to-install-wxwidgets-on-a-linux-system

User README.md for build instructions after loading

wxwidgets sources
https://www.wxwidgets.org/downloads/

another note page for building
https://randomgooby.wordpress.com/2015/03/02/quick-tip-veracrypt-on-a-raspberry-pi-2/

after all the building, won't run on a 512mb arm systems.

--30--

configuration notes for beaglebone pocket

local link to BBB if connected (presented for convenience).
http://192.168.7.2/bone101/Support/bone101/

This will probably apply to the beaglebone black (wireless) which will be used in the Unibone project that is in the queue.

This has some number of extra complications since it has a USB OTG connection for power and also presents a USB networking adapter via that conduit to the host.

This allows for a very interesting control interface via the web, but makes it a bit tricky to
get to the internet with the pocket (since it has no network NIC).

The first few notes here are for configuring the network, setting up ssh.

The default login is debian for the system, which is default for the debian releases.

The network router / gateway address is 192.168.7.1, and 192.168.7.2 is the IP for the debian board on the other side of the USB.  On windows at least, the win 10 automagically recognized the connection, created an eth instance for the USB NDIS nic and the ip 192.168.7.1 is visible there.

Login worked to the 192.168.7.2 as advertised.

The time page below doesn't use Debian, so such as installing software must be translated to debian commands.  The page's example uses Angstrom (which is advertised on the BBB images).

Also it did not include the incantation for getting the time to be set.  ntp was not in the downloaded debian image used, so one must use some way to get  the time to set.

http://derekmolloy.ie/automatically-setting-the-beaglebone-black-time-using-ntp/

I also wanted to set the timezone.  Not sure how one would do it on the Angstrom release, but on debian, the dpkg reconfigure worked as usual.

dpkg-reconfigure tzdata

This page has info for making Windows 7 host the network connection.

https://ofitselfso.com/BeagleNotes/HowToConnectBeagleboneBlackToTheInternetViaUSB.php

Will research how to use a raspberry pi W or such linux system to host this, with possibly less foolishness with the network setup on the hosting system end.  With windows not sure how much has to be redone everytime the system starts and stops.

Also since this will be frequently used on a windows laptop, not sure whether the whole thing will survive suspend, even if the BBB pocket is turned off prior to the exercise of suspending.

Eventually setting up a raspberry pi zero as a router would be valuable as it could also present an IP and make it accessible by natting the connection used by the BBB.

***********************
Hosting system + network with a linux host:

https://elementztechblog.wordpress.com/2014/12/22/sharing-internet-using-network-over-usb-in-beaglebone-black/

The Debian OS is used for the testing which is obtained from here.
BBB console can be obtained by using the following command

ssh 192.168.7.2 -l root

In the BBB console type the following

ifconfig usb0 192.168.7.2
route add default gw 192.168.7.1

In the linux console of host system type

sudo su

#wlan0 is my internet facing interface, eth5 is the BeagleBone USB connection
ifconfig eth5 192.168.7.1
iptables --table nat --append POSTROUTING --out-interface wlan0 -j MASQUERADE
iptables --append FORWARD --in-interface eth5 -j ACCEPT
echo 1 > /proc/sys/net/ipv4/ip_forward

Incase network not accessible then type the following in BBB terminal

echo "nameserver 8.8.8.8" >> /etc/resolv.conf  

To set up a domain use the following (example uses pri domain):

domain pri
search pri
nameserver 10.192.168.1
nameserver 8.8.8.8

***********************
Other links of use:

getting started

How to Connect a BeagleBone Black to the Internet Using USB

discussion for Armbian, but some good info on USB OTG as a tether.
USB OTG as a network - Development - Armbian forum 

Announcing $25 PocketBeagle - Google Groups (link into GG discussions)

BeagleBoard.org - latest-images

eLinux org links

BeagleBoardDebian - eLinux.org

--30--

Small web page template, with auto refresh.

Small refreshing web page. 

Also note on shell infinite loop to mechanize on the server side.

By running the shell script to generate the web page,  and adding the auto refresh you have a quick and dirty way to offloading information from the server via browser and simple script.

auto-refresh-code-in-html-using-meta-tags

bash-infinite-loop

Small example from temperature

<HTML>
<HEAD>
<TITLE>Odroid temp</TITLE>
<meta http-equiv="refresh" content="5">
</HEAD>
<BODY>
WEATHER-BOARD v1.6<br>
<br>======== si1132 ========<br>
UV_index : 0.01<br>
Visible : 206 Lux<br>
IR : -1486 Lux<br>
======== bme280 ========<br>
temperature : 30.18 'C<br>
temperature : 86.32 'F<br>
humidity : 31.18 %<br>
pressure : 1010.49 hPa<br>
altitude : 113.952599 m
<br></BODY>
</HTML>

--30--

xrdp and xrdp-sesman problems

update to the xrpd sesman recently via update killed the xrdp.

bug report included below.

if necessary, have to log in and and manually start xrdp-sesman

service xrdp restart seems not to restart xrdp-sesman, so connections fail after you restart it after reboot

xrdp failed (problem connecting) when package was auto-updated

Unable to start XRDP service

#854548 xrdp sesman service fails

--30--

Adding system tray to a project c# and a console application

Need to add to references

System.Windows
System.Windows.Forms
System.Drawing

so that the Icon reference will work



            NotifyIcon tray = new NotifyIcon();
            tray.Visible = true;

            tray.Icon =
                new System.Drawing.Icon(System.Environment.GetFolderPath
                (System.Environment.SpecialFolder.Personal)
                + @"\Icon.ico");

            tray.Text = "Ice Essentials";

An Icon.ico file must exist as this example uses that method to get the "ico"-ized bitmap file for use.

If one were using windows with forms, other than a console window project to start with, the ico object could be taken from objects created for forms.  But this allows the system tray object to be created w/o that on a console type exe in c#

xinit xsession xsessionrc notes

This is a brief on xinit xsession etc.

https://unix.stackexchange.com/questions/281858/difference-between-xinitrc-xsession-and-xsessionrc


~/.xinitrc is executed by xinit, which is usually invoked via startx. This program is executed after logging in: first you log in on a text console, then you start the GUI with startx. The role of .xinitrc is to start the GUI part of the session, typically by setting some GUI-related settings such as key bindings (with xmodmap or xkbcomp), X resources (with xrdb), etc., and to launch a session manager or a window manager (possibly as part of a desktop environment).

~/.xsession is executed when you log in in graphical mode (on a display manager) and the display manager invokes the “custom” session type. (With the historical display manager xdm, .xsession is always executed, but with modern display managers that give the user a choice of session type, you usually need to pick “custom” for .xsession to run.) Its role is both to set login-time parameters (such as environment variables) and to start the GUI session.

~/.xsessionrc is executed on Debian (and derivatives such as Ubuntu, Linux Mint, etc.) by the X startup scripts on a GUI login, for all session types and (I think) from all display managers. It's also executed from startx if the user doesn't have a .xinitrc, because in that case startx falls back on the same session startup scripts that are used for GUI login. It's executed relatively early, after loading resources but before starting any program such as a key agent, a D-Bus daemon, etc. It typically sets variables that can be used by later startup scripts. It doesn't have any official documentation that I know of, you have to dig into the source to see what works.


--30--