Prized Season software

Learning ispell and newer aspell.

Installed main binaries at /usr/local/bin/

-rwxr-xr-x 1 805992 Apr 21 11:22 libaspell.so.15.1.0
lrwxrwxrwx 1 19 Apr 20 23:46 libaspell.so.15 -> libaspell.so.15.1.0
-rwxr-xr-x 1 130468 Apr 21 11:22 aspell
-rwxr-xr-x 1 5472 Apr 21 11:22 prezip-bin

At /usr/local/lib/aspell-0.60/

-rw-r--r-- 1 13848 Apr 20 23:50 iso-8859-1.cset
-rw-r--r-- 1 30875 Apr 20 23:50 iso-8859-1.cmap
-rw-r--r-- 1 692320 Apr 20 23:57 pt_PT.rws
-rw-r--r-- 1 284 Apr 20 23:57 pt_PT_repl.dat
-rw-r--r-- 1 73 Apr 20 23:57 pt_PT.multi
-rw-r--r-- 1 113 Apr 20 23:57 pt_PT.dat
-rw-r--r-- 1 41456 Apr 20 23:57 pt_PT_affix.dat
-rw-r--r-- 1 100 Apr 21 00:03 standard.kbd

Built dictionaries at /pub/test/aspell-0.60/

Languages used:

• aspell6-en-7.1-0
• aspell6-pt_PT-20070510-0

Firstly I have compiled aspell application, and actually installed it manually in the directories referred above.
You can build your own dictionaries using aspell-lang-20101122.tar.gz, or similar.
I just used aspell6-en and aspell6-pt and built them into /usr/local/lib/aspell-0.60/

HTML 5 progress has been slow and cumbersome.

http://mindprod.com/jgloss/html5.html

About Unicode / international standards (new entities):
http://mindprod.com/jgloss/htmlentities.html#SPECIALCHARACTERS


This is a DRAFT.

This essay talks about newly proposed standard for CDDB3:
http://moreira.dnsalias.org/home/henrique/doc/CDDB3_essay-revision02.pdf

sysvinit are the mainstream tools to get Linux up and running.

I have spent a considerable time to see where the code source packages / tarballs would be.

Finally:
ftp://ftp.cistron.nl/pub/people/miquels/software/

Utilities such as runlevel, and most important init (!), are written by Miquel van Smoorenburg, miquels@cistron.nl.

This fellow has a considerable repository at ftp://ftp.cistron.nl/pub/people/miquels/


Let's pick runlevel, for simplicity: it has a fingerprint of around 3 Kbytes, and it uses

#include

mainly.

setutent

...rewinds the pointer of utmp (usually at /var/run/utmp) file.
Then the line containing "ut->ut_type==RUN_LVL", ut->ut_pid%256 is shown -- after the previous running level (prev = ut->ut_pid / 256). The run-level are actually two octets at utmp (the previous is the high-order byte, the current running level is the low-order byte).

New xpfweb-v2.8 is released, named xpfweb-v2.8.2:

• http://libunicode-plus.sourceforge.net/repository/xpfweb_v2x/
  

Contains small updates and fixes.
The download package on the SourceForge is not ready yet.

Check this forum item.

SMTP plain-text authentication is still used amongst ISPs.
The basic idea is someone who wants to send a message via SMTP, needs to be authenticated first.
Username and password are encoded (typically via Base64).

liblowstream has capabilities to encrypt / decrypt to simetric encodings, such as:

• Blowstream (R)
  or
  
• Base64

Let's focus on SMTP authentication now:

• ASCII-0d (NUL) username
• ASCII-0d (NUL) password

These two, in sequence, form the object to be encoded to plain Base64, to what we call below userpassencd.
The SMTP starts then with authentication, as follow:
AUTH PLAIN userpassencd

For instance, supose your username and password are:

• user1@com.xy
• yourPasswd

The "object to be encoded" is [00]user1@com.xy[00]yourPasswd
(each [00] is actually ASCII-0d).

The plain-text authentication to send is then marked bold:

test_blowstream a E example.bin
Input had 24 bytes, output has: 32 (convertCode=0)
AHVzZXIxQGNvbS54eQB5b3VyUGFzc3dk

If you use the liblowstream library, all you have to do is underlined on the piece of C++ code on the right.

One of the interesting things on Left hand-side blocking lists (LHSBL, refer to wiki.openrbl.org/wiki/LHSBL) is they are far more effective rejecting ham, than normal / conventional tools used to fight spam.

They are far more restricted.
I got impressed when running SpamAsssassin against a genuine message arrived at my box from LinkedIn.
I thought SpamAssassin would classify it right away as spam, but it didn't. The reason is explained below, after the impressive report by SpamAssassin:

Content analysis details: (-8.3 points, 6.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-4.0 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium
trust
[208.111.172.106 listed in list.dnswl.org]
0.0 HTML_MESSAGE BODY: HTML included in message
-4.3 RCVD_IN_BSP_TRUSTED RBL: Sender is in Sender Score Certified (trusted
relay)
[Return Path SenderScore Certified (formerly]
[Bonded Sender) - ]

LinkedIn is white-listed at Sender Score Certified.

The picture shows a brief analysis, from top to bottom, left to right, as follow:

• checking the incoming announced relays at my MTA; this output has email addresses blurred, to avoid harvesting;
• "bondedserver": explained how to use these white-lists; like any other RBL, they are DNS based;
• bottom left, an excerpt of the message;
• bottom right: checking the respective MTA (the arriving IP at my box) is white-listed;
• in this example we have used IP 208.111.172.106 (gnetinfo hostaddr 208.111.172.106 returns mail12-a-ab.linkedin.com, and mail12-a-ab.linkedin.com has address 208.111.172.106).