Friday, January 29, 2016

How Science is Making Immortality a Reality

By: Laurie-Anne Vazquez 04/06/2015 12:32PM
Category: Making History
Ponce de Leon’s quest for the Fountain of Youth may be the stuff of legend, but the drive behind it — finding a cure for aging — is anything but. Humans have been trying to crack the code of immortal youth for almost as long as we’ve been alive. We’ve tried just about everything we can imagine, from magic objects and epic journeys, to human sacrifice and drinking blood (and inventing monsters that live forever by doing so). It was only a matter of time until science got involved in the quest, and it has made some very real strides toward immortality as a reality in the near future.

RECAP OF PAST SCIENTIFIC EFFORTS

Aging, at a molecular level, makes very little sense. Our bodies are constantly creating new cells and restoring our natural defenses, yet we still grow old. Entropy gets the best of us and we accept it as inevitable, even though science has made enormous strides in elongating our lifespans. Life expectancy has risen in the last century, and people in developed countries can expect to live to about 80 now, which is a marked increase from about 47 in 1900. That increase is largely due to advances in curing childhood diseases, but has resulted in a tradeoff of chronic diseases generated by old age — and the body’s entropic response to it. Heart disease, cancer, and Alzheimer’s are the biggest offenders, and treating them individually rather than taking a pill to prevent aging in the first place takes up more of our body’s resources.
Scientists are well aware of all these problems, and have tried lots of different methods to restore vitality to the human body. Restoring homeostatic capacity — or, the body’s capability to self-stabilize its systems in response to stressors like physical exertion, hot or cold weather, and bright or low light — is chief among them. At its essence, one could argue that the human body is essentially a complex biological machine, and as a machine, its advancing age is simply a mechanical problem to be treated instead of an inevitability.
And if treating that problem is as simple as keeping people healthier and free from disease as long as possible, then science has a very good chance of making that happen.
The biggest culprit keeping us from an extended lifespan is the telomerase enzyme. Discovered by Dr. Elizabeth Blackburn (who won a Nobel Prize for it), telomerase is a repeating DNA sequence at the end of a chain of chromosomes that caps each strand and tells the next one where to begin. It is responsible for telling our cells when to stop growing, and every time it caps a strand, a little part of that cell’s information on how to rebuild itself is lost. As a result, scientists are finding ways to either prevent that loss or revitalizetelomerase when it is lost in order to combat aging at the molecular level.
That said, science didn’t always know telomerase was the problem, and lots of other solutions have cropped up over time. Aviator Charles Lindbergh tried to cheat death by finding a way to replace our organs with machines, creating a machine that became the prototype for the heart-lung machine doctors utilize in modern open-heart surgery. Cloning, cyborgs, nanotech cellular repairs, and 3D printing organs from a transplant recipient’s own cells are just the latest in that line of thinking, but they still rely on replacing parts rather than stopping aging in the first place.
Science fiction writers have frequently proposed uploading the human brain into a computer to achieve immortality, and real-world science is making that possible. Known as “whole brain emulation,” scientists have taken large steps toward achieving this method of immortality, including engineering neural devices that interface with the human immune system the same ways our brain does, and creating simulated animal brains. Science fiction also gave us the idea of cryogenics, preserving the human body by lowering its metabolism to preserve resources — effectively freezing it in time — which is more a protective measure against aging than a solution. But real-world science continues providing advancements.

CURRENT SCIENTIFIC RESEARCH

Scientists at UC San Francisco have successfully reversed the effects of old age and disease in mice by infusing blood from young mice into old ones. Specifically, researchers found that blood from 3-month-old mice reversed age-related declines in memory, learning, and brain function in the brains of 18-month-old mice (the equivalent of a 70-year-old person). Researchers also found that when they injected just plasma into the old mice, they had increased stamina and motor function, and performed just like their 3-month-old peers. Scientists were even able to identify a single chemical — a protein called Creb — that acts as a master regulator in the brain and is made more active by young blood. There have actually been several drugs that reverse age-related conditions in mice. The key is that there isn’t any single drug that reverses everything about aging… and that’s what scientists are hoping to find once they begin testing with humans.
Silicon Valley is the latest hub for scientific achievement over aging. Google created Calico Labs, the California Life Company, to create age-defying drugs reversing the biology controlling our lifespan. Human Longevity Inc. is focused on creating a database of 1 million human genome sequences by 2020 to better combat diseases worsened by aging. The Palo Alto Longevity Prize awards two $500,000 prizes to “innovations that restore the body’s homeostatic capacity” and “promoting the extension of a sustained and healthy lifespan.” The stated goal of all these companies is to alleviate the complications aging wreaks on the human body in terms of disease, but the implied goal — and the one earning all the funding — is to figure out immortality.
Why is Silicon Valley involved? Successful anti-aging medicine and technology have the potential to be “the biggest industry that’s ever existed by some huge margin,” according toAubrey de Grey, Chief Scientific Officer at the Strategies for Engineered Negligible Senescence Research Foundation. While the charity is self-funded, and de Grey is considered somewhat dubious by the scientific community, he funds $5 million worth of anti-aging research every year.

IN PHYSICS

Science may yet achieve immortality one day, and physicists everywhere are doing their best to vet the options. Professor Frank J. Tipler has been called out for mangling quantum physics as a possibility in his book The Physics of Immortality, and the idea of quantum immortality — where the simultaneous split of subatomic particles offers two equally plausible existing realities — has merit only as a thought experiment. Thus far, the scientific immortality option that seems most physics-friendly is tied into Stephan Wolfram’s “Computational Universe” idea. Rooted in the belief that fundamental programs like fractals and the Fibonacci sequence underlie all behavior in the universe (regardless of whether or not the behavior follows our understanding of physics), Wolfram believes that humans simply need to discover these programs and apply them to further our existence on this planet. And because human brains are more limited in processing these higher-level programs than artificial intelligence, Wolfram proposes creating AI to find those more complex programs and run them for us. Up to an including one for immortality.
Whatever the solution is, we can be sure that physicists will be there to make it happen.
 https://www.fiatphysica.com/blog/making-history/science-of-immortality-aging-wrinkles

HIDING TOR FROM YOUR ISP – PART 1 – BRIDGES AND PLUGGABLE TRANSPORTS

This post is going to talk about something that has been commonly discussed on the forums recently. How can I hide my tor usage from my ISP ?
People are more worried about hiding their tor usage from their ISP, than hiding it from a VPN. There seems to be a back and forth debate about whether using a VPN will or will not protect you. Whether or not the VPN can be convinced to log  your connection, and so forth. A few of my previous posts regarding LulzSec and the YardBird pedophile rings have shown that those who rely on VPNs to protect them are historically known to end up in jail. Even our friend we were recently introduced to, The Grugq says, TOR -> VPN is ok, but VPN -> TOR, go to jail.
In my previous posts about VPN -> TOR and TOR -> VPN, I tried to remain neutral in that you should be able to make your own decisions about how you wish to protect yourself. But just remember, at the end of the day, nobody is going to go to jail for you. If you simply want to hide the fact that you are using tor from your ISP, then we have other options than a VPN. We have bridges, and several different pluggable transports. What are these, and how can we use them in Tails?
Quote
What bridges are and when to use them
When using Tor with Tails in its default configuration, anyone who can observe the traffic of your Internet connection (for example your Internet Service Provider and perhaps your government and law enforcement agencies) can know that you are using Tor.
This may be an issue if you are in a country where the following applies:
1. Using Tor is blocked by censorship: since all connections to the Internet are forced to go through Tor, this would render Tails useless for everything except for working offline on documents, etc.
2. Using Tor is dangerous or considered suspicious: in this case starting Tails in its default configuration might get you into serious trouble.
Tor bridges, also called Tor bridge relays, are alternative entry points to the Tor network that are not all listed publicly. Using a bridge makes it harder, but not impossible, for your Internet Service Provider to know that you are using Tor.
https://tails.boum.org/doc/first_steps/startup_options/bridge_mode/index.en.html
The first thing we are going to do is get some bridges. Let us do this before we configure Tails to use bridges, because once Tails is in bridge mode, we will not be able to connect to tor without working bridges. So the first thing we want to do is visit the following webpage.
https://bridges.torproject.org/bridges
Enter the impossibly difficult captcha, and click “I am human”, and you should get a list of bridges that look like this. These are actual bridges pulled from the tor bridges page.
Quote
  5.20.130.121:9001 63dd98cd106a95f707efe538e98e7a6f92d28f94
106.186.19.58:443 649027f9ea9a8e115787425430460386e14e0ffa
69.125.172.116:443 43c3a8e5594d8e62799e96dc137d695ae4bd24b2
These bridges are publicly available on the Tor Project website, so they may or not may be the best choice to use, but they are a good start. Another option is to send an email to bridges@bridges.torproject.org with a message in the body saying “get bridges” without the quotes. This will only work if sent from a Gmail account or Yahoo, unfortunately. If you want to use this, set up the email account using tor and you will receive a list of around 3 bridges shortly thereafter.  Save them somewhere you can use them the next time you boot up Tails, or write them down.
Ok, so now we have our bridges. How do we use bridges in Tails? This is an option we need to activate when we boot up Tails. To activate the bridge mode, we will be adding the bridge boot option to the boot menu. The boot menu is the first screen to appear when Tails starts. It is the black screen that says Boot Tails and gives you two options. 1. Live, 2. Live (Fail Safe). When you are on this screen, press Tab and a list of boot options will appear in the form of text at the bottom of the screen. To add a new boot option, add a Space then type “bridge” without the quotes and press enter. You have now activated bridge mode.
Once Tails boots up completely, you will get a warning that you have entered bridge mode and not to delete the default IP address in there, which is 127.0.0.1:*. This is advice we will follow, so just click OK and the settings window for tor will pop up. At this point you need to add your bridges. So you are going to take the three bridges you got, and enter the IP address and the port. If we were going to use the example above this is what we would enter.
Quote
  5.20.130.121:9001
106.186.19.58:443
69.125.172.116:443
For each bridge you add, type it in the available text box where it says “Add A Bridge” and then click the green + button to add that bridge. You will need to add one bridge at a time. Once you are finished adding your bridges, you can click OK. At this point, your yellow tor onion icon in the top right should turn green shortly after and you will be connected to the tor network using a bridge. Again, since these bridges are less likely to be known by your ISP, they are less likely to know that you are using tor when you use bridges.
You may wish to look up your bridge before you use it however. Maybe you want to find out where your bridge is located, maybe you want to see who is hosting the bridge, and you can do this by looking for a IP look up service online, by doing a search and typing in the IP address. The three listed above are located in the following locations.
Quote
5.20.130.121 – Country:   Lithuania
106.186.19.58:443 – Country: Japan
69.125.172.116:443 – Country: New Jersey, United States
And with that, you can decide which bridge would be a better choice for you to use. I suggest however, that you go and get new bridges and do not use the ones I listed above for obvious reasons that they are now linked to Silk Road users by me posting them on this forum. I should note that the way bridges hide the fact that you are using tor from your ISP, is that you are connected to an IP address that is likely not known to your ISP to be affiliated with tor entry nodes.
While bridges are a good idea, unfortunately they may not be enough. According to Jacob Applebaum, (a tor developer) bridge traffic is still vulnerable to something called DPI (deep packet inspection) to identify internet traffic flows by protocol, in other words they can tell you are using tor by analyzing the traffic. While tor uses bridge relays to get around a censor that blocks by IP address, the censor can use DPI to recognize and filter tor traffic flows even when they connect to unexpected IP addresses. This is less likely to be done by your ISP, and more likely to be done by the NSA, or other oppresive governments like in China and Iran, so you can choose if this is an issue for you.
Quote
Lately, censors have found ways to block Tor even when clients are using bridges. They usually do this by installing boxes in ISPs that peek at network traffic and detect Tor; when Tor is detected they block the traffic flow.
To circumvent such sophisicated censorship Tor introduced obfuscated bridges. These bridges use special plugins called pluggable transports which obfuscate the traffic flow of Tor, making its detection harder.
https://www.torproject.org/docs/bridges#PluggableTransports
Pluggable transports are a more new, but less talked about technology being implemented by tor to disguise the fact that you are using tor to your ISP and other censors. As mentioned above, it attempts to transform your tor traffic into innocent looking traffic that would hopefully be indistinguishable from normal web browsing traffic. Currently the most popular pluggable transports are obfuscated bridges. Obfuscation by definition, is the hiding of the intended meaning in communication, making communication confusing, wilfully ambiguous, and harder to interpret. Obfuscated bridges actually transform the traffic to look like random packets of data. Obfuscated bridges currently have 2 protocols.
1. obfs2
2. obfs3

Obfs2 (The Twobfuscator) is talked about at length at the following official page.
https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/doc/obfs2/obfs2-protocol-spec.txt
But for the laymans out there, basically obfs2 uses a protocol that disguises your traffic to look like random data, whereas tor has a more distinct structure to it. However, it should be noted in the case of obfs2, that if an attacker sniffs the initial handshake between your computer and the obfuscated bridge, they could get the encryption key used to disguise your traffic and use it to decrypt the disguised traffic which would reveal it as tor traffic. They would not be able to decrypt your tor traffic, but they would be able to see you are using tor. This is not likely something your ISP would do, but it may be something law enforcement or the NSA would do. So if you are only worried about your ISP, then obfs2 would likely suffice.
Obfs3 (The Threebfuscator) is talked about at length at the following official page.
https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/blob/HEAD:/doc/obfs3/obfs3-protocol-spec.txt
Obfs3 uses a very similar protocol to disguise your traffic as obfs2, however it uses a more advanced method of an initial handshake called the Diffie Hellman key exchange. They however found some vulnerabilities in the protocol and had to go a step further and customize the Diffie Hellman key exchange to make it an even more robust method of establishing that initial handshake. Using obfs3 would be a better bet to disguise your traffic if your adversary is the NSA or other law enforcement.
So how do you get these obfuscated bridges? They are not as easy to get, but they can be obtained from tor through email. However, you need to request those bridges specifically to get them. You need to use a Gmail or Yahoo account and send an email to bridges@bridges.torproject.org and enter in the body of the email “transport obfs2” without the quotes, and for obfs3, simply enter “transport obfs3”. Please note that you can only send one request to tor per email, every 3 hours. Which one you should use, is entirely your choice, I am just giving you the information necessary to make an informed choice. Enter them in this format so that Tails knows which protocol to use.
obfs3 83.212.101.2:42782
obfs2 70.182.182.109:54542

tor also provides a few obfuscated bridges on their home page which you can use as well, and I will list them below. If you send a request to tor and get a response containing bridges without obfs2 or obsf3 at the beginning of the lines, then these are normal bridges, not obfuscated, and they are likely to be out of obfuscated bridges at the moment. You will have to try again another day. So if you get a response with bridges that are without obfs2 or 3 at the beginning of each line, please again, be aware these are normal bridges, unlike the ones below.
obfs3 83.212.101.2:42782
obfs3 83.212.101.2:443
obfs3 169.229.59.74:31493
obfs3 169.229.59.75:46328
obfs3 209.141.36.236:45496
obfs3 208.79.90.242:35658
obfs3 109.105.109.163:38980
obfs3 109.105.109.163:47779
obfs2 83.212.100.216:47870
obfs2 83.212.96.182:46602
obfs2 70.182.182.109:54542
obfs2 128.31.0.34:1051
obfs2 83.212.101.2:45235

I have a feeling that some of you reading this will be inclined to go out and get yourself some obfs3 bridges right away, because you think they are the best choice out there for staying anonymous. And right now they have the potential of being what you hope for in that regard, except for one huge flaw. The number of obfs3 bridges is small. Last report I read put it at around 40 bridges running obfs3, and obfs2 was around 200. So while obfs3 is the most secure option out there, its limited number of available bridges would pool you into a smaller group of people making connections to the 40 available bridges and may not provide any more anonymity for you. tor is in depserate need of more obfs2 and obfs3 bridges at this time and these factors should be taken into account when using obfuscated bridges.
One of the solutions to this shortage problem, is to run your own obfuscated bridge. I am not going to go into it, but if you are interested in doing this, you should visit the following page to set up an obfuscated proxy, or better yet, purchase a few VPS and set them up as obfs2 or obfs3 proxies. One of the best things about doing it this way, is that you can configure it (with the instructions provided) to be a private obfuscated bridge, and therefore tor will not give it out to the public. You can then connect to your own private obfs3 bridge. You can also use a friend’s computer, or use a server that you know is secure. But again, make sure that you trust the computer you are using, otherwise it is no more secure than a VPN.
Another possible solution to the lack of obfuscated bridges may be another pluggable transport option, something called a flash proxy. This is brand new and not perfectly implemented yet, and please be aware that this is basically still in beta. When thinking about a flash proxy, think about the characteristics of a flash, quick and short lived. This protocol was developed by a tor developer who attended Stanford University, and the idea is that the IP addresses used are changed faster than a censoring agency can detect, track, and block them. This method is similar to using normal bridges, in that, it hides the fact you are connecting to IP addresses known to be related to tor, including when the bridge’s IP addresses listed by tor are discovered by your ISP or law enforcement. This does not however, hide the fact you are using tor if somebody is analyzing your traffic using DPI (deep packet inspection).
The main benefit to this option is that the proxies are run by many people all over the world. They are run when random internet users visit a webpage with a specific plugin that turns their browser into a proxy as long as they are on that page. You are basically using somebody else’s connection through their browser to connect to a tor relay. You are only using 1 active connection at any time, but you have around 5 established connections to different proxies in case your active connection drops off, then you can start using another proxy in its place. Below is another explanation of how this process works.
Quote
In addition to the Tor client and relay, we provide three new pieces. The Tor client contacts the facilitator to advertise that it needs a connection (proxy). The facilitator is responsible for keeping track of clients and proxies, and assigning one to another. The flash proxy polls the facilitator for client registrations, then begins a connection to the client when it gets one. The transport plugins on the client and relay broker the connection between WebSockets and plain TCP. (Diagram below)
https://crypto.stanford.edu/flashproxy/arch.png
A sample session may go like this:
1. The client starts Tor and the client transport plugin program (flashproxy-client), and sends a registration to the facilitator using a secure rendezvous. The client transport plugin begins listening for a remote connection.
2. A flash proxy comes online and polls the facilitator.
3. The facilitator returns a client registration, informing the flash proxy where to connect.
4. The proxy makes an outgoing connection to the client, which is received by the client’s transport plugin.
5. The proxy makes an outgoing connection to the transport plugin on the Tor relay. The proxy begins sending and receiving data between the client and relay.

In other words, you end up going from your computer, to the proxy, then the proxy to the tor relay. – JR
The whole reason this is necessary is because the client cannot communicate directly with the relay. (Perhaps the censor has enumerated all the relays and blocked them by IP address.) In the above diagram, there are two arrows that cross the censor boundary; here is why we think they are justified. The initial connection from the client to the facilitator (the client registration) is a very low-bandwidth, write-only communication that ideally may happen only once during a session. A careful, slow, specialized rendezvous protocol can provide this initial communication. The connection from the flash proxy to the client is from an IP address the censor has never seen before. If it is blocked within a few minutes, that’s fine; it wasn’t expected to run forever anyway, and there are other proxies lined up and waiting to provide service.
I know this might be a bit complicated, but you really do not need to understand how it works to benefit from it. You also might be asking about somebody just blocking your ability to connect with the facilitator (the supplier of the proxies). But, the way you actually connect to the facilitator is in a very special way that tor has designed, and this is built into the flash proxy pluggable transport. This explanation is just for your comfort, not to help you make it work.
Quote
The way the client registers with the facilitator, is a special rendezvous step that does not communicate directly with the facilitator, designed to be covert and very hard to block. The way this works in practice is that the flash proxy client transport plugin makes a TLS (HTTPS) connection to Gmail, and sends an encrypted email from an anonymous address (nobody@localhost) to a special facilitator registration address. The facilitator checks this mailbox periodically, decrypts the messages, and inserts the registrations they contain. The result is that anyone who can send email to a Gmail address can do rendezvous, even if the facilitator is blocked.
https://trac.torproject.org/projects/tor/wiki/FlashProxyFAQ
Two questions you should be asking. 1) Can I trust the proxies, and/or facilitator? 2) How do I use this?
Well, the facilitator is chosen and currently only run by tor, so you can take that at face value. As far as the proxies go, the proxies themselves may or may not be trustworthy, and this is the risk you run every time you use tor. Your bridges that you use may be compromised, your entry nodes, your exit nodes, every single possible hop along your way to the internet can be compromised at any given time. Luckily, even if the proxy is compromised and logging your traffic, they are only going to be able to see encrypted tor traffic. And as I mentioned above, anybody who visits a webpage with a specific plugin on it, becomes a flash proxy as long as they are on that site. This means, some people will be a flash proxy without their knowledge, and others will be flash proxies because they want to be one. The idea behind this is to have multiple users, tens of thousands, if not hundreds of thousands of flash proxies available at all times to increase the number of possible IP addresses you rotate between to keep your ISP and possibly the NSA guessing.
So do you use this? It actually currently is not supported in Tails. But it can be used with Tor Pluggable Transports Tor Browser Bundle outside of Tails. You can get it at the following page and it will run on your normal operating system, whether it is Windows, MAC, or Linux. Get the package at the following page.
https://www.torproject.org/docs/pluggable-transports.html.en#download
Next follow the following tutorial, which is pretty straight forward and has pictures of exactly what you need to do, and will probably do a better job than I would at explaining how to set it up.
https://trac.torproject.org/projects/tor/wiki/FlashProxyHowto
Essentially it comes down to, enable port forwarding for port 9000, add “bridge flashproxy 0.0.1.0:1” without the quotes, to your torrc, and leave everything else alone unless you need to use a different port, which is unlikely. You may need to make an exception in your firewall for the flashproxy plugin if it asks you. As long as you are using the Tor Pluggable Transports Tor Browser Bundle, it should be pretty easy to get this feature working. But until Tails adds support for it, this is the only option you have if you want to use flash proxy bridges.
Ok, so you have a lot of information right now and maybe are left a bit confused, but read over this one a few times and try to extract as much out of it as possible at once. Try setting up normal bridges, then try doing the obfuscated bridges, and once you get those working, then maybe consider doing the flash proxies if you are okay without using Tails. Tails will likely implement support for this later. Ask yourself some questions, do I just want to hide the fact that I am using tor from my ISP? Or am I hiding from somebody much bigger than that?
Consider whether it is plausible for you to run a private obfuscated proxy, or even a private bridge. Hopefully now you have enough information to make an informed decision.
Currently there are other pluggable transports currently under developed, but not yet deployed. Here is a list of upcoming projects.
Quote
ScrambleSuit is a pluggable transport that protects against follow-up probing attacks and is also capable of changing its network fingerprint (packet length distribution, inter-arrival times, etc.). It’s part of the Obfsproxy framework. See its official page. Maintained by Philipp Winter.
http://www.cs.kau.se/philwint/scramblesuit/
Status: Undeployed

StegoTorus is an Obfsproxy fork that extends it to a) split Tor streams across multiple connections to avoid packet size signatures, and b) embed the traffic flows in traces that look like html, javascript, or pdf. See its git repository. Maintained by Zack Weinberg.
https://gitweb.torproject.org/stegotorus.git
Status: Undeployed

SkypeMorph transforms Tor traffic flows so they look like Skype Video. See its source code and design paper. Maintained by Ian Goldberg.
http://crysp.uwaterloo.ca/software/SkypeMorph-0.5.1.tar.gz
http://cacr.uwaterloo.ca/techreports/2012/cacr2012-08.pdf
Status: Undeployed

Dust aims to provide a packet-based (rather than connection-based) DPI-resistant protocol. See its git repository. Maintained by Brandon Wiley.
https://github.com/blanu/Dust
Status: Undeployed

Format-Transforming Encryption (FTE) transforms Tor traffic to arbitrary formats using their language descriptions. See the research paper and web page.
https://eprint.iacr.org/2012/494
https://kpdyer.com/fte/
Status: Undeployed

Also see the unofficial pluggable transports wiki page for more pluggable transport information.
https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports

Source: https://www.torproject.org/docs/pluggable-transports.html.en
https://www.deepdotweb.com/jolly-rogers-security-guide-for-beginners/hiding-tor-from-your-isp-part-1-bridges-and-pluggable-transports/
 

Wednesday, January 27, 2016

Gadget Steals Encryption Keys

Here’s how it works: the PITA consists of a bunch of off-the-shelf parts and it runs on four AA batteries. Using an antenna that can read electromagnetic waves emitted by computer processors from up to 19 inches away, the device can swipe RSA and ElGamal data and decrypt it. Stolen data is then stored locally on the device’s microSD card, or the PITA can transmit data over Wi-Fi to the attacker’s computer.

http://bgr.com/2015/07/08/hacking-tools-pita-encryption-keys-radio-waves/

The cost of the radio device has been estimated at $300 / €270 and it can be built with readily available components: a Rikomagic controller, a piece of wire acting as an antenna and a FUNcube software defined radio (SDR).


The FUNcube Dongle Pro+: LF to L band software-defined radio


No drivers required! Device drivers are already included in your operating system – Windows, Linux or Mac OSX, 32 or 64 bit.
* The guaranteed coverage of the FUNcube Dongle Pro+ is from 150kHz to 1.9GHz, and there is a gap in coverage between 240MHz and 420MHz.

MK802IV LE Quad Core (Linux Edition) Picuntu Linux Mini PC - 8GB Flash Storage

Email
MK802IV LE (Linux Edition) Quad Core Ubuntu/Picuntu Linux Mini PC - 8GB Flash Storage.
http://www.cloudsto.com/products/rikomagic-mk802iv/mk802iv-le-quad-core-linux-edition-picuntu-linux-mini-pc-8gb-flash-storage-detail.html


Rikomagic Remote Control is a nice application which let you use your Android phone or tablet as a remote control


Installing Bluefish

Installing Bluefish on Debian GNU/Linux

Installing the release that is part of Debian / Ubuntu / Mint / etc.

Use
sudo apt-get install bluefish
sudo aptitude install bluefish
or any other frontend for the package manager such as synaptic or simply "add / remove programs".

Installing the very latest release on Debian

Installing the very latest release on Debian 8 (Jessie/Stable)

Recent packages for bluefish are available from the official Debian backports archive and can be installed by following the instructions given here. The entry would look like this:
deb http://YOURMIRROR.debian.org/debian jessie-backports main
or
deb http://YOURMIRROR.debian.org/debian stable-backports main
And install the package via:
apt-get -t jessie-backports install bluefish
Report any bugs to the Debian bugtracker.

Installing the very latest release on Debian 7.0 (Wheezy/Oldstable)

Recent packages for bluefish are available from the official Debian backports archive and can be installed by following the instructions given here. The entry would look like this:
deb http://YOURMIRROR.debian.org/debian wheezy-backports-sloppy main
or
deb http://YOURMIRROR.debian.org/debian oldstable-backports-sloppy main
And install the package via:
apt-get -t wheezy-backports-sloppy install bluefish
Report any bugs to the Debian bugtracker.

Installing the very latest release on Debian 6.0 (Squeeze/Oldoldstable)

Recent packages for bluefish are available from the official Debian backports archive and can be installed by following the instructions given here. The entry would look like this:
deb http://YOURMIRROR.debian.org/debian-backports squeeze-backports-sloppy main
or
deb http://YOURMIRROR.debian.org/debian-backports oldoldstable-backports-sloppy main
And install the package via:
apt-get -t squeeze-backports-sloppy install bluefish
This version is built with the GTK+ 2 libraries. Report any bugs to the Debian bugtracker.

Installing the very latest on Ubuntu Linux

You'll find recent packages of bluefish in the Bluefish PPA maintained by Klaus Vormweg. Follow the instructions given there to add this repository. Then bluefish can be updated to its latest release:
sudo apt-get update
sudo apt-get upgrade
Please note, that the http://debian.wgdd.de repository has become obsolete. See below, how to clean your system.

Removing obsolete debian.wgdd.de entries from sources.list

The http://debian.wgdd.de/ repository no longer provides packages of bluefish. The above steps make the following entries to either /etc/apt/sources.list or /etc/apt/sources.list.d/debian.wgdd.de_*.list or any other file in /etc/apt/sources.list.d/ obsolete. You can safely remove any references to the http://debian.wgdd.de repository, that may look like these:
deb     http://debian.wgdd.de/debian wheezy main contrib non-free
deb-src http://debian.wgdd.de/debian wheezy main contrib non-free
deb     http://debian.wgdd.de/debian stable main contrib non-free
deb-src http://debian.wgdd.de/debian stable main contrib non-free
deb     http://debian.wgdd.de/debian squeeze main contrib non-free
deb-src http://debian.wgdd.de/debian squeeze main contrib non-free
deb     http://debian.wgdd.de/debian oldstable main contrib non-free
deb-src http://debian.wgdd.de/debian oldstable main contrib non-free
deb     http://debian.wgdd.de/ubuntu UBUNTU_VERSION_HERE main restricted universe multiverse 
deb-src http://debian.wgdd.de/ubuntu UBUNTU_VERSION_HERE main restricted universe multiverse 
and update your system:
sudo apt-get update
sudo apt-get upgrade
Also the wgdd-archive-keyring package then is obsolete together with the repository keyring. If you have the package installed, do:
sudo apt-get autoremove --purge wgdd-archive-keyring
... or if you only had the key:
sudo apt-key del E394D996

Installing Bluefish on Fedora Linux

Installing the version distributed by Fedora

yum install bluefish

Installing the very latest on Fedora with yum

To enable a bluefish-release yum repository download the bluefish-release.repo file.
Place this repo file in /etc/yum.repos.d
Then you can install normally with...
yum install bluefish
Packages are currently provided for Fedora 19, 20 and 21. Packages are provided for both i386 and x86_64.
All packages are built using mock. All packages are signed. You will be prompted to download the GPG key.

Installing development versions on Fedora with yum

While care is taken to keep development versions very stable and usable, development versions may crash, contain data eating bugs and incomplete features.
Please report any bugs you might find in Bluefish bugzilla
If you wish to test the bleeding edge versions of Bluefish currently under development download the bluefish-svn.repo file.
Place this repo file in /etc/yum.repos.d
Then you can install normally with...
yum install bluefish
Packages are currently provided for Fedora 19, 20 and 21. Packages are provided for both i386 and x86_64.
All packages are built using mock. All packages are signed. You will be prompted to download the GPG key.

Browsable Yum repo's for Fedora

These pages were created using repoview.
Fedora 19 - Release
* i386
* x86_64
Fedora 20 - Release
* i386
* x86_64
Fedora 21 - Release
* i386
* x86_64

Installing Bluefish on RHEL/CentOS 6.5

Installing the very latest on RHEL/CentOS 6.5

Bluefish packages for RHEL/CentOS 6.5 are available at the links below for i386 and x86_64.
These packages require version 6.5. Previous versions prior to 6.5 had GTK+ 2.18.x.
RHEL/CentOS 6.5 has GTK+ 2.20.x which is the minimum version required to build current versions of Bluefish.
All packages are built using mock. All packages are signed with this gpg key.

Required for RHEL/CentOS 6.5..
i386
* bluefish-2.2.7-1.el6.i686.rpm
* bluefish-shared-data-2.2.7-1.el6.noarch.rpm
x86_64
* bluefish-2.2.7-1.el6.x86_64.rpm
* bluefish-shared-data-2.2.7-1.el6.noarch.rpm
Optional debug info RHEL/CentOS 6.5..
i386
* bluefish-debuginfo-2.2.7-1.el6.i686.rpm
x86_64
* bluefish-debuginfo-2.2.7-1.el6.x86_64.rpm

Installing Bluefish on openSUSE

Bluefish is available in the main repository. Launch YaST and search for "bluefish" to find and select the appropriate package to install.
This process is also automated through 1-Click-Install on the openSUSE Build Service: https://software.opensuse.org/package/bluefish

Installing Bluefish on AltLinux

Installing Bluefish on Slackware

Installing Bluefish on Mac OS X

Download the latest version installer from http://www.bennewitz.com/bluefish/stable/binaries/macosx/, open it and drag the bluefish icon onto Applications.
In Mavericks there is a system setting called Gatekeeper that only allows you to install packages from Apple-identified developers. Bluefish is not distributed through the Apple app store, so you will have to workaround that setting.
Use the contextual menu (e.g. secondary-click button), and you'll see a menu with "Open" in it. This will present you with a dialogue box, asking you for permission to run the software. You will only be asked this the first time.
Alternatively, the Gatekeeper setting can be disabled. For information, see: https://kb.wisc.edu/helpdesk/page.php?id=25443 or http://support.apple.com/kb/ht5290

Installing Bluefish on Windows XP or newer

Installing 2.2.7

Download the latest Bluefish installer from the main download server: http://www.bennewitz.com/bluefish/stable/binaries/win32/
The installer will require internet access to download GTK+ and any spell check dictionaries. Please note that the internet-enabled setup may fail if the installer is run from a network share. See below for instructions for internet-less installation.

Installing without Internet Access

Download the latest Bluefish installer from the main download server: http://www.bennewitz.com/bluefish/stable/binaries/win32/
Download the GTK+ 2.24.8 installer (from the gtk-win project): http://downloads.sourceforge.net/gtk-win/gtk2-runtime-2.24.8-2011-12-03-ash.exe?download
Download any language dictionaries you wish to be able to install: http://www.muleslow.net/files/aspell/lang/
Place the files in a new directory named 'redist' in the same directory as the Bluefish installer. e.x.
Bluefish\
Bluefish\Bluefish-2.2.7-setup.exe
Bluefish\redist\gtk2-runtime-2.24.8-2011-12-03-ash.exe
Bluefish\redist\aspell6-en-7.1-0.tbz2
The installer will fall back on downloading the files if they are not found in the redist folder, or if the checksum of the local copy is invalid.
http://bfwiki.tellefsen.net/index.php/Installing_Bluefish