blog.layer2.org » web http://blog.layer2.org A technical blog Sun, 23 May 2010 00:15:21 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Use ffmpeg to extract first image out of FLV http://blog.layer2.org/2007/12/03/use-ffmpeg-to-extract-first-image-out-of-flv/ http://blog.layer2.org/2007/12/03/use-ffmpeg-to-extract-first-image-out-of-flv/#comments Mon, 03 Dec 2007 05:10:48 +0000 solipsistic http://blog.layer2.org/2007/12/03/use-ffmpeg-to-extract-first-image-out-of-flv/ I found at least one other person trying to find a way to extract a JPG snapshot out of a flash video using ffmpeg.

The above article suggests using ffmpeg to extract a PNG, and then convert that to a JPG (since the JPG will be much smaller). Instead, just use the correct arguments to ffmpeg:

ffmpeg -i movie.flv-vcodec mjpeg -vframes 1 -an -f rawvideo -s 320x240 movie.jpg

With -vcodec mjpeg the important argument.

]]> http://blog.layer2.org/2007/12/03/use-ffmpeg-to-extract-first-image-out-of-flv/feed/ 0 Serve home directories to internal IPs only with lighttpd http://blog.layer2.org/2007/11/04/serve-home-directories-to-internal-ips-only-with-lighttpd/ http://blog.layer2.org/2007/11/04/serve-home-directories-to-internal-ips-only-with-lighttpd/#comments Mon, 05 Nov 2007 01:47:39 +0000 solipsistic http://blog.layer2.org/2007/11/04/serve-home-directories-to-internal-ips-only-with-lighttpd/ Recently, I decided I wanted to share home directories via HTTP to everyone on my home network. This is an easy way to share files with Windows machines where you don’t have any type of sshfs-like support. The problem was that this file/web server also faces the Internet. Obviously I don’t want to share our personal files to anybody who cares to look. After a bit of playing, I came up with this configuration:

$HTTP["remoteip"] != "192.168.1.0/24" {
  $HTTP["url"] =~ "^/~" {
    url.access-deny = ( "" )
    dir-listing.activate = "disable"
  }
}

This allows any host with an IP in the 192.168.1.1-254 range view any URL that begins with /~username. It denies everyone else with a 403 – Forbidden message. Note that for some reason, listing the conditions in the opposite order (url first, remoteip second) did not produce the correct results.

Finally, make sure that you have both the appropriate modules enabled:

server.modules += ( "mod_access", "mod_userdir" )
]]> http://blog.layer2.org/2007/11/04/serve-home-directories-to-internal-ips-only-with-lighttpd/feed/ 0 Who the heck is 142.166.3.122 and 142.166.3.123 (radianrss-1.0)? http://blog.layer2.org/2007/10/15/who-the-heck-is-1421663123-radianrss-10/ http://blog.layer2.org/2007/10/15/who-the-heck-is-1421663123-radianrss-10/#comments Tue, 16 Oct 2007 03:05:54 +0000 solipsistic http://blog.layer2.org/2007/10/15/who-the-heck-is-1421663123-radianrss-10/ I’ve been perusing through my logs lately and found the user agent “radianrss-1.0″ numerous times. I’d never heard of this program (maybe an RSS reader?), so I did a google search. The only commentary I found was this post speculating that 142.166.3.123 was possibly involved in the compromise of katester.net.

Interestingly enough, the rest of the search results are the traffic statistics pages of various Wordpress blogs around the Internet. There doesn’t seem to be a clear answer for what “radianrss” is, or why 142.166.3.122-123 is constantly indexing all of my blog posts.

[evian]$ grep "142.166.3.123" access.log
142.166.3.123 - - [15/Oct/2007:01:02:23 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14022 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:01:52:14 -0700] "GET /feed/atom/ HTTP/1.1" 200 36826 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:03:36:42 -0700] "GET /feed/atom/ HTTP/1.1" 200 36826 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:04:02:18 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14023 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:06:23:53 -0700] "GET /2007/10/06/the-new-ubuntu-is-coming-already/ HTTP/1.1" 200 10915 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:07:00:07 -0700] "GET /2007/10/07/apt-get-does-have-an-option-for-automatic-security-updates/ HTTP/1.1" 200 12223 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:07:01:49 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14023 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:07:57:22 -0700] "GET /2007/10/08/use-mozilla-firefox-under-wine-to-reach-those-windows-only-sites/ HTTP/1.1" 200 13046 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:09:06:34 -0700] "GET /2007/10/12/rails-ruby-scriptconsole-has-tab-completion/ HTTP/1.1" 200 16010 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:09:17:26 -0700] "GET /feed/atom/ HTTP/1.1" 200 13032 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:09:27:21 -0700] "GET /feed/atom/ HTTP/1.1" 200 36826 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:10:02:07 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14022 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:10:17:18 -0700] "GET /2007/10/14/slow-ssh-logins-in-ubuntu-feisty-704/ HTTP/1.1" 200 12895 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:12:46:43 -0700] "GET /2007/10/13/use-ps2pdf-to-create-pdfs-from-any-linux-application/ HTTP/1.1" 200 11739 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:13:01:23 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14022 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:13:03:56 -0700] "GET /2007/10/14/slow-ssh-logins-in-ubuntu-feisty-704/ HTTP/1.1" 200 12882 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:14:32:48 -0700] "GET /feed/atom/ HTTP/1.1" 200 36826 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:15:08:14 -0700] "GET /feed/atom/ HTTP/1.1" 200 36825 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:15:08:21 -0700] "GET /2007/10/14/slow-ssh-logins-in-ubuntu-feisty-704/ HTTP/1.1" 200 12894 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:15:08:26 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14014 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:16:01:29 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14023 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:16:03:03 -0700] "GET /2007/10/14/slow-ssh-logins-in-ubuntu-feisty-704/ HTTP/1.1" 200 12882 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:18:29:20 -0700] "GET /2007/10/14/slow-ssh-logins-in-ubuntu-feisty-704/ HTTP/1.1" 200 12901 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:18:29:21 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14008 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:18:47:46 -0700] "GET /feed/atom/ HTTP/1.1" 200 36826 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:19:01:27 -0700] "GET /2007/10/14/if-youre-not-already-start-using-dd-wrt/ HTTP/1.1" 200 14028 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:19:02:41 -0700] "GET /2007/10/14/slow-ssh-logins-in-ubuntu-feisty-704/ HTTP/1.1" 200 12896 "-" "radianrss-1.0"
142.166.3.123 - - [15/Oct/2007:19:49:08 -0700] "GET /feed/atom/ HTTP/1.1" 200 36818 "-" "radianrss-1.0"

This is traffic just from today – less than 24 hours! Looking back a little further I also found

142.166.3.123 - - [14/Oct/2007:17:35:13 -0700] "GET /2007/10/14/slow-ssh-logins-in-ubuntu-feisty-704 HTTP/1.1" 200 450 "-" "Java/1.5.0_11"

which has decided to use Java 1.5 as its user agent string.

I’m curious to know why this IP address is retrieving all of my (and others’) Wordpress blog(s), and why so frequently. Its not like the page has changed between each retrieval. Have you found this IP address in your logs, the “radianrss-1.0″ user agent string, or anything else of interest?

]]> http://blog.layer2.org/2007/10/15/who-the-heck-is-1421663123-radianrss-10/feed/ 14