Since the bookcase in our living room is is reaching its maximum capacity, we're moving from traditional books to e-books.
My wife already has the Sony PRS-T2 e-reader, and this week, I bought the Kobo Glo
for myself. The reason for choosing the Kobo Glo is that it has an
illuminated screen (which you can turn on and off). So it enables me to
read in the dark. No need for an additional light. It does drain the
battery faster if you enable the integrated light. Not as fast as I
thought initially, but compared to the battery life of the Sony reader,
the difference is significant (weeks instead of months).
This
post won't review the Kobo Glo itself. There are numerous other reviews
online available. So, if you're looking for an in-depth review, please
follow this link and pick one of the search results.
This post goes into the e-book management for the e-reader. Especially on how to sort and display series (e.g. the
Jack Reacher books by Lee Child).
Even though the post describes the management for the Kobo (Glo), it's
possible as valid for other e-readers. The (textual) information was
gathered from several sources on the Internet (and added as a source of
that information).
This week, I found the following mail in my mailbox. Not really sure what the scam is, but I'm sure it's gonna cost me money....
(Letter to the President or Brand Owner, thanks)Dear President,
We
are a domain name registration and protection agency in Asia. I have
something to confirm with you. We formally received an application on
July 16,2013 that a company which self-styled"Togh International
Co.,Ltd"were applying to register"redelijkheid"as their Brand Name and
some domain names through our firm.
Now we are handling this
registration, and after our initial checking, we found the name were
similar to your company's, so we need to check with you whether your
company has authorized that company to register these names. If you
authorized this, we will finish the registration at once. If you did not
authorize, please let us know within 7 workdays, so that we will handle
this issue better. Out of the time limit we will unconditionally finish
the registration for"Togh International Co.,Ltd".Looking forward to
your prompt reply.
Best Regards,
David Zhao
Tel:+86(0551)63434624
Fax:+86(0551)63434924
Address:HuiZhou Ave 999, Hefei, Anhui, China
A while back I wrote a blog post about enabling global logging on security rules. This week I applied the same technique to enable ping on all zones for testing / troubleshooting purposes.
Instead
of adding ping as a host-inbound-traffic system-service to all zones,
and if you have a couple this means some configuring, you can solve this
by adding just 3 (three) lines of config to the firewall.
Juniper entered the realm of
application firewalling since the release of Junos 11.4 (for SRX
platforms). A realm that is mainly dominated by Palo Alto (they
basically invented it) and Checkpoint, but more and more vendor's are
starting to move in on that territory.
And Juniper is one of those vendors that started to implement Application Firewalling (AppFW) on their (SRX) firewalls.
This
post will show what needs to be done to enable AppFW, and how to
configure those policies by using the J-Web interface and the CLI. The Junos software used in this exercise is version
12.1X44.4.
We had a wireless security implementation at a customer site which consisted of the following components:
The setup included a wireless lan for guest access by using the Cisco ISE guest portal functionality.
We
started by configuring the WLC's and ISE environment and having done
that everything worked as a charm. A couple of days later we we were not
able to connect to the wireless network.
The error reported in the ISE Authentications overview was:
Dynamic Authorization Failed : 11213 No responds received from Network Access Device
Since the release of Junos v12.1x44D10 for branche SRX firewalls,
Juniper added a feature called DNS-Proxy. This features enables the
Junos device as a caching DNS server with several additional options.
One of those feature is to define a Fully Qualified Domain Name (FQDN) with an IP address which overrides (if it exists) the entry in the 'official' DNS system on the Internet.
Last year I implemented an ISPConfig3 configuration
for personal use. Mainly to host some e-mail domains, and perhaps some
basic websites. This setup relatively easy to implement a should have
been a breeze to maintain.... Untill I got an email from the provider
last Tuesday, mentioning that my Linux VPS was attacking other hosts
around the world..... *GASP*.. my VPS had (most likely) been assimilated
into a botnet of some sort, and it was flooding a ton of other hosts.
This post basically describes the technique of how to deal with traffic
originating from the inside of a firewall, and directing the traffic
over the external interface IP address to a different internal zone.
First a network overview of the things used in this setup.
While exploring the
configuration options on the Juniper SRX firewall, I stumbled upon the
so-called firewall filters. These filters are not to be mistaken for the
firewall policy rules. They are something different, but can be used
for achieving similar goals.
In
my case, I wanted to see if it was possible to quickly block a list of
IP addresses (or subnets) without the hassle of creating addressbook
entries (Address Sets). My list of IP addresses consists of known hosts that participate in the criminal ZeuS network.
These IP addresses are either Command&Control servers or servers
used to transfer (captured) data to. In any case, servers you don't want
to communicate with.
The
solution on the SRX is to create a firewall filter containing the list
with hosts / networks. The filter, in my case, is applied to the
outgoing interface (fe-0/0/0).
