Posts

Showing posts from September 20, 2009

Explaining About Bittorrent Encryption

I remember I downloaded a torrent with KTorrent in my Slackware-Linux box, thinking that everything is alright, but that was in the office. After I downloaded that source, which is an ISO file, I told my boss to share that I did download an updated version of that file. Then he look at me and ask me disparagingly, "Are you downloading it securely or using encryption?". I ask myself, "dang, what did I do?" and stuck in a moment, geeze! We'll he told me to download anything since our internet is faster than a DSL. Okay, cut the crap! I'm not digressing here. So I did a research about encryption and other stuffs with Bittorrent and this will be explained! I read some articles " How To Encrypt BitTorrent Traffic ", " BitTorrent Encryption Confuses the BPI, ISPs and Journalists Who Don’t Research ", and " BitTorrent Encryption Myths " and learned that encryption doesn't do anything about hiding user's end information or even

Removing of Multiple Files with Exception Using "rm" command in Linux

Now I get into this point. I remember I did some simple command, back then, by using " rm " command in Linux. Try searching in the net but none of it provides me the answer. The goal was that, I have a directory named, "reports" with lots of files/directories/sub-directories inside it, and try to delete all of them but with exclusion of the files that starts with the word "report-" (ex. report-2009-10-19.html). I thought the command issued in my shell $> rm -rf $(ls reports/|grep -e '[^report-*]') would enable me to delete the files but it seems it doesn't work. My expectation was the files that does not start with "reports" word will be deleted. Then I read the manual of rm ("man rm" in bash), I found that the -v would select those non-matching lines. Now, issuing the commands in my shell $> cd reports $> rm -rf $(ls .|grep -v '[report-*]') enables me to delete the files that starts with the word "r

Connecting Samba 3 from Linux to Mac OS X Leopard

I'm so befuddled yesterday until I figured it out that it works from Mac OS X to Mac OS X Leopard with Samba 3. I thought my smb.conf doesn't work. Now, Linux to Mac OS X was hard because I thought, I must ran smbpasswd to provide password for the username I have to used. I was thinking that Mac OS X's Samba configuration directs the use to able to check on the user's of the machine with it's account information (username and password of the Mac OS X Leopard machine). It does able me to authenticate and access my folder via that Mac OS X machine. I found this article also, seems we have the same issue faced. http://discussions.apple.com/thread.jspa?threadID=2086667