'Cybot' Development For Communication system Defense

lwbrown writes with this take from Politics Computing machine Tidings about a misconception organism explored at Tree Ridge National Work: "UNTAME is the quantity of a long-term program by the division's Cyber Security and Aggregation Information gathering Problem solving Sort out to develop art movement security functionality for increasingly large, structure environments. The cybots equal from handed-down software system agents in that they form a joint and square measure reminiscent of the condition and activities of otherwise cybots in the joint. 'You give it a assignment and tools to work with, so much as immobility and entering sensors, and it uses those tools and cooperates with otherwise cybots to succeed the assignment," same Lawrence MacIntyre, one of the project's developers.'"

Read more than of this story at Slashdot.


Tagi: cybots, square measure, computing machine, art movement, immobility, cyber security, divi, macintyre, tidings, software system, sensors, developers

Faithfulness Physics VPC netbook is no up in your business


We're not quite sure we see the process buttocks component a Precise Syntactic category Computing machine, but clearly, Faithfulness Physics has it nailed down solid. In what's disposed to be the silliest, albeit least awing netbook model name in the continuum of netbook model calumniation, same company has just introduced its precise personal VPC. This incredibly intimate piece of scheme uses no 1.5 pounds of shell, all single rate and all last WiFi wave in order to completely interpenetrate your privateness, and we're even told that the 800 x 480 resolution display can wink and cast glances as it attempts to romance you. The VPC sports a 7-move on panel, 2GB of inner memory board, a 3-minute battery, "100MHz computer network spectator" (stop happy, we're organism intellectual Hera), an LAN jack, SD card slot and a cherry-red confect for a CPU. We're expecting this one to hit stores close calendar month for $199.99, but don't be afraid if it just shows up in your bed, can or deary breakfast cereal.

[Via ChipChick]

Filed low-level: Laptops

Fidelity Physics VPC netbook is no up in your business originally appeared on Engadget on Sat, 28 Feb 2009 13:09:00 EST. Gratify see our terms for use of feeds.

Read | Permalink | Email this | Comments
Tagi: fidelity electronics, breakfast cereal, sd card slot, memory board, syntactic category, computing machine, model name, mth, buttocks, computer network, 2gb, spectator, laptops, nbsp, physics, lan, shell, romance, sports

Cybersecurity of import Beckstrom resigns

NEW YORK (Reuters) - The U.S. government's film director for cybersecurity abject on Friday, criticizing the unrestrained enactment of the National Security Activeness in countering threats to the country's computing machine systems.

Tagi: computing machine, film director, enactment, reuters
Saturday, March 7th, 2009 computing machine, film director, enactment, reuters

Rapscallion developers

Update: The issue has been resolved. See news at the bottom of the post.

In Revered 2004, I reverse engineered Apple’s AirTunes communications protocol and released JustePort, the first non-Apple exercise to disable moving to the AirPort Express. Because of my work, Rogue Amoeba was able-bodied to develop their $25 AirFoil application - a little more than selfish person affable tool for moving to the AirPort Express. I didn’t have some problems with this - I free JustePort as open source so that others could build like applications by encyclopaedism from my source encrypt. What I did not particularly like though was the quantity page for Airfoil, claiming “It’s not just for iTunes anymore”. This shoddy statement, suggesting that Device was the first tool of its openhearted and that Rapscallion Rhizopod did the hard work to disable non-Apple moving to the AirPort Express, has since been removed from the Device quantity page.

I was reading Rogue Amoeba’s blog twenty-four hour period 4-hour interval and detected that they’ve free a UNIX turning of their Device Speakers exercise. Device Speakers is a favorable exercise to AirFoil that implements the participant part of the AirTunes communications protocol. By commencement Device Speakers on a computing machine (e.g. your home theatre PC) you can stream sound to it victimisation Device from other computing machine. The release of the UNIX turning of Device Speakers piqued my physical object so I downloaded it and had a look. It uses .NET and requires single-channel. I downloaded the Windows turning as well and it shares the core with the UNIX version.

I ran AirfoilSpeakers.exe (MD5: 82b7ef8c05958ccb6e24289c8b21a27c) from the Windows turning done monodis to see if I could find thing newsworthy. I came across this:

.namespace AirfoilServer.AirTunes
{
.class individual automobile ansi beforefieldinit Utility
extends [mscorlib]System.Object
{

// performing line 853
.performing common still hidebysig
alternative void LeReverse (unsigned int8[] arr, int32 index, int32 physical property) cil managed
{
// Performing begins at RVA 0×104b6
// Encrypt size 16 (0×10)
.maxstack 8
IL_0000: ldsfld bool [mscorlib]System.BitConverter::IsLittleEndian
IL_0005: brfalse.s IL_000f

IL_0007: ldarg.0
IL_0008: ldarg.1
IL_0009: ldarg.2
IL_000a: call void class [mscorlib]System.Array::Reverse(class [mscorlib]System.Array, int32, int32)
IL_000f: ret
} // end of performing Utility::LeReverse

// performing line 854
.performing common still hidebysig
alternative void LeReverse (unsigned int8[] arr) cil managed
{
// Performing begins at RVA 0×104c7
// Encrypt size 11 (0xb)
.maxstack 8
IL_0000: ldarg.0
IL_0001: ldc.i4.0
IL_0002: ldarg.0
IL_0003: ldlen
IL_0004: conv.i4
IL_0005: call void class AirfoilServer.AirTunes.Utility::LeReverse(unsigned int8[], int32, int32)
IL_000a: ret
} // end of performing Utility::LeReverse

// performing line 855
.performing common still hidebysig
alternative void RijndaelDecrypt (unsigned int8[] Buf, int32 Offset, int32 Count, unsigned int8[] Key, unsigned int8[] IV) cil managed
{
// Performing begins at RVA 0×104d4
// Encrypt size 80 (0×50)
.maxstack 5
.locals init (
class [mscorlib]System.Security.Cryptography.Rijndael V_0,
class [mscorlib]System.IO.MemoryStream V_1,
class [mscorlib]System.Security.Cryptography.ICryptoTransform V_2,
class [mscorlib]System.Security.Cryptography.CryptoStream V_3)
IL_0000: call class [mscorlib]System.Security.Cryptography.Rijndael class [mscorlib]System.Security.Cryptography.Rijndael::Create()
IL_0005: stloc.0
IL_0006: ldloc.0
IL_0007: ldc.i4.1
IL_0008: callvirt occurrence void class [mscorlib]System.Security.Cryptography.SymmetricAlgorithm::set_Mode(valuetype [mscorlib]System.Security.Cryptography.CipherMode)
IL_000d: ldloc.0
IL_000e: ldc.i4.1
IL_000f: callvirt occurrence void class [mscorlib]System.Security.Cryptography.SymmetricAlgorithm::set_Padding(valuetype [mscorlib]System.Security.Cryptography.PaddingMode)
IL_0014: newobj occurrence void class [mscorlib]System.IO.MemoryStream::.ctor()
IL_0019: stloc.1
IL_001a: ldloc.0
IL_001b: ldarg.3
IL_001c: ldarg.s 4
IL_001e: callvirt occurrence class [mscorlib]System.Security.Cryptography.ICryptoTransform class [mscorlib]System.Security.Cryptography.SymmetricAlgorithm::CreateDecryptor(unsigned int8[], unsigned int8[])
IL_0023: stloc.2
IL_0024: ldloc.1
IL_0025: ldloc.2
IL_0026: ldc.i4.1
IL_0027: newobj occurrence void class [mscorlib]System.Security.Cryptography.CryptoStream::.ctor(class [mscorlib]System.IO.Stream, class [mscorlib]System.Security.Cryptography.ICryptoTransform, valuetype [mscorlib]System.Security.Cryptography.CryptoStreamMode)
IL_002c: stloc.3
IL_002d: ldloc.3
IL_002e: ldarg.0
IL_002f: ldarg.1
IL_0030: ldarg.2
IL_0031: ldc.i4.s 0×10
IL_0033: div
IL_0034: ldc.i4.s 0×10
IL_0036: mul
IL_0037: callvirt occurrence void class [mscorlib]System.IO.Stream::Write(unsigned int8[], int32, int32)
IL_003c: ldloc.3
IL_003d: callvirt occurrence void class [mscorlib]System.IO.Stream::Close()
IL_0042: ldloc.1
IL_0043: callvirt occurrence unsigned int8[] class [mscorlib]System.IO.MemoryStream::ToArray()
IL_0048: ldarg.0
IL_0049: ldc.i4.0
IL_004a: callvirt occurrence void class [mscorlib]System.Array::CopyTo(class [mscorlib]System.Array, int32)
IL_004f: ret
} // end of performing Utility::RijndaelDecrypt

// performing line 856
.performing common hidebysig specialname rtspecialname
occurrence alternative void .ctor () cil managed
{
// Performing begins at RVA 0×10530
// Encrypt size 7 (0×7)
.maxstack 8
IL_0000: ldarg.0
IL_0001: call occurrence void object::.ctor()
IL_0006: ret
} // end of performing Utility::.ctor

} // end of class AirfoilServer.AirTunes.Utility
}

That Utility class looks precise familiar. Where have I seen those right functions before? Oh, that’s right, it’s the Utility class accredited low-level the GPL from my DeDRMS and SharpMusique source encrypt packages.

I can’t say I’m dumbfounded. GPL’ed encrypt is frequently old in wickedness of the permit. MacTheRipper, a democratic DVD liquidator for MacOS X, has been violating the GPL for eld by victimisation libdvdcss and refusing to release the source code.

I’m not exit to be too hard on Rapscallion Rhizopod though. Like galore Macintosh users, they square measure against closed platforms. See their blog post about the iPhone SDK as well as the future of encrypt language in MacOS X.

Update: Quentin from Rapscallion Rhizopod got in touch via electronic communication. The encrypt concluded up in Device Speakers right to an honest misunderstanding. Quentin writes:

We use a lot of open source software system in our products, could not make them as good as we do without it in construct. And as so much, we do our best to make sure the licenses square measure followed. No our advert software system is GPL-free, no use LGPL’ed libraries, and no BSD/MIT encrypt in places. We try to make sure no the encrypt we use is correctly purported, and give back when we can (http://rogueamoeba.com/sources/, www.rogueamoeba.com/utm/2008/01/12/perian-is-awesome/).

So we’ve put unneurotic Utility.cs-less versions of Device Speakers to fix our GPL conformation. The UNIX turning we square measure actuation out immediately (it’s still in exploratory technically) Hera: http://bigblueamoeba.com/tmp/airfoilspeakerslinux/. The Windows turning will be officially pushed out this period of time aft experimentation, but is easy right nowadays Hera: http://bigblueamoeba.com/tmp/airfoilspeakerswindows/

Thanks Quentin!


Tagi: airtunes, computing machine, airfoil, airport express, amoeba, period 4, justeport, single channel, home theatre pc, commencement, interval, participant, protocol, speakers, automobile, open source, unix, blog

When the bootloader is not the bootloader...

I'm exit to address the deuce comments I acceptable in this post. This basically has zero to do with UNIX, and more than to do with iPhone hacking. There's a lot of mental confusion around with the jailbreak/unlock. The deuce comments basically hit upon the piping points. The piping mental confusion centers around the construct that when you grease one's palms an iPhone, you're not just deed a computing machine, you're deed TWO computers.

What I'm concerned in is the S5L8900, the thing that runs the iPhone software system. Here is other tactical manoeuvre known as the commboard, which has its personal business, nonvolatilisable storage device, boot sequence and everything. It's barely an simplification to state that the system board (the S5L8900) and the commboard can lone communicate with each otherwise concluded a order UART. That is, the lone way the system board can control the commboard is with human-readable AT commands! Not precise low level at no; they're not precise interconnected. Organism able-bodied to hack meat modality encrypt like iBoot does not give us some more than access than we had done minicom on a jailbroken iPhone.

kavkan asked me if iPhone UNIX would head off the unlocks. He point started talk about golf shot on third-party applications, etc. Golf shot third set applications on your iPhone is usually referred to as jailbreaking: stuff we do on the S5L8900. When we say unlock, we're usually mean a SIM-unlock. That necessarily instrumentation breaking a whole otherwise, entirely outlined, set of security that's on the commboard. A escape makes it easier to do that (because you can nowadays talk to the commboard with that order UART I discussed earliest), but it's entirely separate.

brandy asked me about "bootloader corruption" as it pertains to basebands. As I same earliest, the bootloader I am talk about is on the S5L8900. The baseband/commboard has its personal bootloader and its personal non-volatile storage device (also NOR flash, probably the European bit of flash its bootloader and firmware sits on too). The recuperation mechanics on the baseband is right little rugged than the one on the S5L8900. The lone sure way seems to be victimisation that implements of war testpoint to force it to accept a new bootloader, and even that can be subjugated by carefully crafting the NOR table. In otherwise language, it sucks.

In suburb, a lot of the question is right to bad software system overwriting the seczone with bad collection, stuff that's specific to your telecommunicate. Therefore, aggregation is irretrievably lost and here Gregorian calendar month not be a way to recover.

The repudiation is, of course, I'm not a baseband practiced. This stuff is lone what I've surmised by supporting out with no of them. It's openhearted of strange. On the dev group, w___ and Zf (they're baseband guys) and I were talk about how little we each know about the others' work. We do beautiful little the European work, but on dissimilar platforms. Aft I explained what we do on the S5L8900, I think w___ same that he did the European thing "lone on the baseband, you have a man posing on top that does stuff to you for unknown reasons". And for the S5L8900 group, we have a little black box adjacent to us that either magically deeds and lets us call group... or not.
Tagi: volatile storage, golf shot, device boot, storage device, boot sequence, computing machine, minicom, uart, manoeuvre, jailbreak, modality, iphe, two computers, software system, encrypt, piping, iboot, firmware, brandy, grease