Wednesday, 13 August 2014

Sean Cull - SNTT : Using Active Directory to authenticate web users:



'via Blog this'



It took me ages to find this on Sean's old blog so just saving it in case. Thanks for the good writeup Sean.



Sean Cull  10 March 2011 21:24:59

Introduction



This article describes how you can use Active Directory via LDAP and Directory Assistance to authenticate your web users. This is particularly useful in our case where we have an XPages based application running in on a black boxed  appliance in a MS shop. 
The example uses a Windows Server 2008 R2 for AD and Domino 8.5.2 running on Linux. The scheme is simple enough but I struggled to piece the bits together so I thought a write up would be useful. 


Useful tools



I found that the Apache Directory Studio was really useful. This allows you to explore the Active Directory LDAP feed and get a feel for its structure. 



Useful debugging parameters



I found the following two parameters very useful because you can see the structures of the names and groups in AD as they are queried by Domino - these settings are for temporary use only as they create overhead and also show users passwords on the console in plain text ( somewhat disconcerting ) 

Webauth_verbose_trace=1 
LDAPDEBUG=1 


Setting up an AD test environment



This was very straight froward. I installed a 2008 R2 server as a VM and used the Server Roles Manager wizard to install Active Directory accepting the defaults and dependencies. 
I then created a new user ( joe bloggs ) and used that account to authenticate the LDAP feed.

Image:SNTT : Using Active Directory to authenticate web users


Exploring the LDAP Feed with Apache Directory Studio



Use File New and then choose LDAP Connection 

Image:SNTT : Using Active Directory to authenticate web users

Image:SNTT : Using Active Directory to authenticate web users

Image:SNTT : Using Active Directory to authenticate web users

Press the check Authentication button and all should be well 

Next you can browse the LDAP tree and see information on the users and groups 

Image:SNTT : Using Active Directory to authenticate web users
The equivalent "Notes name" as used in an ACL would be 

CN=joe bloggs/CN=Users/DC=ad/DC=focul/DC=net 


Image:SNTT : Using Active Directory to authenticate web users


Configuring Domino to use the Active Directory LDAP



You need to create a Directory Assistance Database and then list this in the server record 
The directory assistance template is an advanced template called called Directory Assistance ( da.ntf ) 

The server document entry looks like this 

Image:SNTT : Using Active Directory to authenticate web users

In the Directory Assistance Database create a record as follows. 

Note that Gabriella Davis and Marie Scott  on page 20 of their very useful presentationOne DirectoryTo Rule Them All, Yes suggests encrypting the LDAP configuration document - not sure how to do that just yet. 


Image:SNTT : Using Active Directory to authenticate web users

Image:SNTT : Using Active Directory to authenticate web users

Note that the suggest and verify buttons are very useful, particularly for the Base DN for search 

Image:SNTT : Using Active Directory to authenticate web users


Testing Authentication



Start with the most basic example you can. 
With a test database set anaonymous access to No Access and Default Access to reader or higher. 

Open the URL and attempt to login - in my case as Joe Bloggs. In the console you will see something similar to this : 

Image:SNTT : Using Active Directory to authenticate web users
Your authentication is working. 

You can now test it with a specific name. You can see the shape of the name from the console output 

The AD name CN=joe bloggs,CN=Users,DC=ad,DC=focul,DC=net gets mapped to CN=joe bloggs/CN=Users/DC=ad/DC=focul/DC=net for use in the ACL 
Groups also work but note that if you put a group into the AD as a peer of "Users" the group name construct includes "Builtin" as in CN=testgroup/CN=Builtin/DC=ad/DC=focul/DC=net so it is better to put the groups within the users branch. 

Image:SNTT : Using Active Directory to authenticate web users

In our case the group name is CN=testgroup4/CN=Users/DC=ad/DC=focul/DC=net 

Image:SNTT : Using Active Directory to authenticate web users



Further Integration



This OpenNTF  Active directory name picker project and search by Rishi Sahi looks really interesting. He also has some good blog articles on LDAP integration 


Other useful presentations



As mentioned above I found Gabriella Davis and Marie Scott's presentation very useful - One DirectoryTo Rule Them All, Yes 

I also attended Warren Elsmore's Directory Integration session at ILUG which was very useful. You can download all of the ILUG slides here => http://www.ilug2010.org/ilug/ilug2010.nsf



A mild rant



In pulling this material together I have come to the conclusion that it is a real shame that IBM has not published the slide decks from lotussphere 2011. 

It would make it a lot easier for developers to make the IBM products more popular if IBM asan organisation was a good citizen of the community in that respect. 

I have huge admiration for many individuals within  IBM that do their best despite IBM in this regard. I also think it is unfair to expect the community to contribute to the IBM Wikis when they are sitting on hundreds of excellent presentations by the world experts in this area - experts who gave up thousands of hours to prepare those slide decks. 

Its hardly what I would describe as a good example of a Social Business. 





 Admin Tips  Appliance  Dev Tips  Show-n-Tell Thursday  Active Directory  LDAP  Lotus 




1Marie Scott  10.03.2011 23:59:30  Directory Assistance Database
Sean - to encrypt the Directory Assistance Database you would go to Database properties and select Encryption Settings to locally encrypt the database, so that anyone who may be able to physically access a copy of the database would not be able to review the LDAP password credentials. Additionally, you should enable SSL for the connection to Active Directory. But it does mean that you have to have a secure LDAP port open on the AD side.

2Sean Cull  11.03.2011 0:13:20  Thanks Marie
Thanks Marie, I thought it was encryption of just that document. Encrypting the whole database makes sense.
Thanks for the help, Sean

3Alberto  12.03.2011 8:22:19  Other scenarios
Two more scenarios I've tested. They are relevant when you share the same users in domino and AD.
1- Try Tivoli Directory Integrator to synchronize users. There are couple of good papers about that.
2- Try Websphere plugging in IIS for Web Single Logon. Tip: You'll need to duplicate names in Domino to establish the DN equivalence

4Sean Cull  12.03.2011 8:29:46  Thanks alberto
Thnaks Alberto - you are correct.
I looked at these but quickly discounted them because in this use case the potential customer needs something very simple as they will have no Domino skills at all. TDI is reported to have a steep learning curve and using IIS is complex to set up.
I was quite pleased to find that the LDAP / DA method above was so straight forward once you understood the nomenclature of the names and groups.



5Nick Wall  12.09.2013 10:55:41  LDAP
Just done proof of concept integration of AD on one of our Test servers, works great. Thanks for reference to Apache Directory Studio, nice tool. If anyone is following install instructions here: directory.apache.org/studio/users-guide/ldap_browser/gettingstarted_download_install.html ...and you are as slow on the uptake as me(!)...the bit where adding new remote site, it has the url: directory.apache.org/studio/update/1.x which obviously doesn't exist, so you will get a 404, go here: { Link } click link on one of the versions, e.g. { Link } and use that as url for remote site.
Thanks again for "rounding up" this LDAP info, saved me a bunch of time.

Tuesday, 12 August 2014

Lialis Notes to SharePoint migration - part 2:



'via Blog this'



Notes to SharePoint: Migrating applications away from Notes – part 2

Notes to SharePoint migration part 2, including: Comparison Notes / SharePoint, tools we use and the people we have.
 
6 months ago I wrote the first blog about this project I am working on, moving Notes and Domino applications to SharePoint (SP). We are now (August 2014) developing the SP applications, so I thought it’s a good moment to write down how this project is going. The client started with approximately 200 Notes applications identified, at the end many where archived, many are planned to be moved to SAP and 60 Notes applications will move to SP. Don’t be mislead by the number, some applications are build up by multiple Notes databases.
Let me first start with what I think of SP these days, compared what Domino can do for clients. Please, this is not a complete comparison of the two products.
  • SP has some great features. It has many out of the box functionality, compared with a Domino server on application level has none besides a few useless Notes database templates.
  • The SP user interface (browser) is great, when a new app is deployed in SP users will find the link somewhere in SP when they log in. Compared with the Notes client, the Notes database links have always been a nightmare, users have to manage the workspace them self. I understand now that IBM tried to get rid of the Notes client desktop and replaced it with the bookmark bar which was so bad people were forced to find the hidden workspace again.
  • All SP apps will look the same because of the style sheet used in the browser, I find this great and it will increase the professional look of the app environment, compared with Notes apps, they all look different and most Notes apps I have seen look from design UI point of view very bad, simply because Notes developers are no UI developers. This is where SP does a good job as well, the things you can do from designing an app are streamlined and bordered by SP. What I mean is that all views look the same, all forms look the same – when you stay in the out of the box area SP will help you in making many apps that have a consistent UI, so you users will understand them more quickly because they look and work the same.
  • You know I have been doing Domino for many years, I know this product very well. There must be a area where it’s better as SP. No worries, there is. But will this be a reason for clients to choose Domino in favor of SP, I don’t think so. Domino is better is developing complex Notes and Web applications (with help of xpages). In SP when you want to do complex stuff you are forced to step out of the save out of the box area. Sure you can still do complex stuff in SP, but the development time will become huge because SP is not meant  for building complex applications. On the Domino server you can build anything, it supports the very powerful formula language, lotus script, java script and you can even run java servlets on Domino. With xpages great Web and Notes client apps can be build. It’s nice to have the mail server on the same system as well and Domino is very secure. But why do so many clients choose SP instead of Domino? Simply because they don’t need to build many complex custom applications. When I look at this 8000 users client I am currently migrating away from Notes to SP there is only 1 Notes application that is so complex we have no clue how to build it in SP. Only 1 Notes app!!!! This is not a reason to keep Notes running compared with all the other great features SP offers. I guess the client will try to buy something of the shelf to replace this xpages application finally. Writing this I realize that these days clients can buy so many applications on the internet there is no need to maintain Domino and the developers to build complex apps.
Anyway, how is the migration project going, 6 months after the start? I have to say it’s going great. We are now actually building SP apps to replace the Notes apps. We started with the simple ones and move up to the more complex ones next year. The development time we calculated is huge, so I will have something to do in 2015.
There a 3 items in this project I have found to become very import and are a must have to make projects like this a success. I will share these with you so you can benefit from it.
  • Dell Quest NMSP. We use this product to migrate Notes apps to SP. First NMSP makes an inventory of the Notes apps you have. I use this to see which forms are used in the Notes apps I must migrate to SP. The not used forms I omit. Then NMSP creates the SP lists, it moves all the Notes app ACL, author, readers fields and other security stuff to the SP list, then it creates the columns in SP (= the Notes fields) and finally it will migrate the Notes content to SP and it will try to match all the Notes names it finds with AD user names. At this moment each app we migrate starts with creating a NMSP job. When the jobs are finalized a big deal of the Notes application is present in SP. Then the final SP design work must be done.
  • This leads me to the roles of the people you need. In our project the Notes developer does the NMSP part. This is logical because he understands the Notes apps, The Quest NMSP tool has many features, so if you find a Notes consultant who understands NMSP very well you are lucky, else he/she had to learn to use the tool which will take a few months on the job learning. On Youtube you will find 7 NMSP training sessions which are great. Back to the people in this project. Off course you need a SP developer as well. In my project I do the NMSP stuff because I am the Notes guy. I create the jobs in NMSP and I do some easy development work in SP. Then I tell the SP developer what functions we need in the new SP app. I can do this because I understand how the Notes app works. When all the SP stuff has been build I do the final tests and when the application is 100% it is moved to the client for user acceptance test and then to production. In our project the Notes guy is critical because he does the NMSP work, he instructs the SP development team had he is responsible for testing the end result. Off course the SP consultant has to do a proper job as well.
  • Dell Quest NMSP can migrate the Notes form design to infopath, but infopath is crap so we replaced it with a tool we found on the market spform.com. It’s a Russian tool, it’s cheap and we love it. It has made our live much easier because it speeds up form design work, it can do tabbed tables (which we find a lot on Notes forms), it can make fields not editable when other fields can be edited, it’s a drag and drop tool in the browser and no need to waste time on making pixel perfect forms (it does this for you). In this project we have to migrate 170 forms to SP, so at his moment my company Lialis is building a tool that can convert Notes forms to spform.com forms, this will save a lot of time because the Notes tables on the form will be migrated to spform.com and all the Notes fields will be at the right spot in spform.com tool.
I think in the next blog I will focus more on how the organization succeeds or struggles to implement all the SP apps we develop.
If you need help with migrations like this feel free to contact me at marten@lialis.com
Lialis Migrating Notes applications from Notes to SharePoint:



'via Blog this'



A good article by Marten



Notes to SharePoint: Migrating applications away from Notes – part 1

A real life large enterprise decided to move away from Notes/Domino.  I am part of the Notes to SharePoint migration team with the focus on the Notes application migration. The client already has carried out the mail migration to Exchange (which is easy with the right tools). I don’t know why they decided to move away from Notes. I know IBM renamed Notes to Domino, I don’t care and I stick to using the Notes name when mentioning Notes client and browser apps running on a Domino server.
In this blog I will share the work we have done so far and other experiences that might be important for you. I guess I will write more blogs about this project in the period 2014 till 2016.
My background is 100% Notes, before I started this project I never touched SharePoint or installed Active Directory.
We are now three months into this project and so far we have worked on the following tasks.
  1. Notes application inventory
  2. Quest Notes Migrator For SharePoint evaluation and test
  3. Notes app to SharePoint conversion documentation

Phase 1; Create proper inventory of your Notes applications

A. get rid of not used Notes applications
You will see that many Notes applications are no longer used and do not need to be migrated. So the first task is to get rid of the not used applications. The knowledge of the clients Notes administrators and developers is needed for this phase. In addition we used Quest NMSP to scan all Notes databases on the different Domino servers. This scan gives a great insight in the application usage. This task will take much time because you will have to talk to each application owner and see if the application may be removed.
B. collecting information about the used Notes applications
In this task you must collect information about the Notes application that you will need during the migration. We have collected information like: Application name, Notes databases used within this application, owner, size, short description of application function, usage and some other organization related details.
In addition we tried to group several Notes application with similar functions to one group. The goal is to create one new (SharePoint) application for all these similar Notes apps. You don’t want to end up with 5 different, almost equal form functions point of view, document libraries in SharePoint.
We categorized the Notes application complexity into low, medium or high. We created rules for this job. The reason of this categorization is because the client wanted to get this insight. In addition it’s wise to start with the simple Notes apps.
The most important job of this phase is to decide where to move the Notes application to. You can migrate to SharePoint, Intranet, MS Dynamics, SAP and other platforms within the organization. You can even decide to host the application externally or buy something of the shelf. The client created criteria to make this decision.
Collecting all this information will take much time because you must wait for application owners and architects to respond. I would suggest to start with this phase as early as possible because most clients can manage this phase them self without the help of external (technical) consultants.

Phase 2; Install the proper tools to migrate the Notes applications away from Notes

In this case, for this particular client, we will start with the migration of  Notes applications to SharePoint. Approximately 40% of the Notes apps will go to SP, the rest will go to other platforms. We will start with the tools we need for the migration to SP. Later during the project we might need other tools to migrate notes apps to other platforms (like MS Dynamics), something to worry about later on during the project.
For migrating Notes apps to SP we have chosen Quest NMSP. The reason is that Quest is capable for migrating Notes content, migrating Notes security (ACL, roles, reader author fields), has the notes doc link tracking support inside and can migrate forms and views. But as it turns out now we will not use Quest to migrate forms and views because recreating these from scratch in SP seems to go faster than fixing the Quest mess in the generated Notes forms and views (no offense to Quest). I must say we did not do a proper assessment of the other tools on the market.
In this clients case getting a SP 2013 test environment is taking some time. So we decided to create a SP 2013 environment from scratch for testing Quest and development POC in our own environment. We needed this environment because Quest needs you to install software on the SP server for the link tracking and to speed up the content conversion. Randy of Dell Quest has written a great blog how to setup all servers needed for SP 2013 environment and how to install the Quest tools on it. Me as Notes guy followed this guide and I succeeded in getting these servers up and running and get Quest NMSP services installed and configured. Here is the link to Randy’s blog.
The great advantage of having these servers is that you will understand what it takes to install the Quest tools on SP 2013 server in order to explain it to the client. You can use this environment to give the first demos to the client and you may use it to evaluate the Quest tooling. So far I like what I have seen form Quest point of view.

Phase 3; The phase I am in currently

We (client) have made a very good inventory of the really used Notes applications that must go to SP (and to other platforms used by the client). We have grouped similar Notes apps, from functionality point of view, together with the goal to create one SP app for these Notes apps. We have a SP 2013 server environment with Quest tooling operational and we can demo it to the client.
Now we need to break down, for each Notes application, the functionality within this application. We must write down details on the content in the Notes application and other details like security. So I started writing word documents for each Notes application and capturing the functions in this document. With capturing I mean creating screen captures of all Notes forms, views, actions and so on. The goal of this approach is to create a mid level document explaining the app functions. We will not dive to deep into the application script libraries that, for example, are created to get a Notes workflow in place because this code will not be used because the workflow will be created in a different manner in SP. I hope you understand my approach. So bottom line I write a document with many screen captures which quickly show the applications functions. Then the client reviews this document in order to check if I did not miss functions. When approved by the client it’s time for entering the SharePoint details. So imagine a table with two columns, the left column drills down the functions of the Notes application (without going into the coding and field level). The right column will explain to the application owner how the Notes functions (like screens, forms, workflows and so on) will be recreated in SharePoint. Then the finished document with Notes and SP functions is send back to the application owner for approval. When approved, the development of this application can start in SP.
At this moment we are starting with the development of the first SP apps to replace the Notes apps. So far I can tell that SP has much more default features and functions out off the box included compared with Notes. So (power) users can use the browser to modify views, add columns and can do level designing of forms with InfoPath. With Notes apps you need designer rights and a Notes designer client to do similar work compared with SP (which is too difficult for power users to do, so you need a Notes developer). On the other hand it seems that creating simple and complex applications is easier and faster in Notes compared SP. The main reason is that in Notes you have the Notes designer client which is a very power development tool which can do all development work, compared with the tools you need in SP (which are InfoPath, SharePoint designer and C#) which work slow and are not designer friendly. InfoPath can be used to create SP forms, when you create a form you can’t snap the fields to a grid, so it’s a nightmare to create pixel perfect forms compared with Notes form creation. Anyway, I will keep you posted about the things we learn when moving 60 Notes applications to SP and another 100 Notes applications to other platforms.
It won’t be a walk in the park – that’s for sure.
Thank you.



Friday, 8 August 2014


hitachiglass

'Superman' crystals could store 360TB of data forever

Data can be kept in crystals that can resist temperatures of 1,000°C

July 12, 2013 04:31 PM ET
Computerworld - Researchers have been able to demonstrate the ability to read and write data using a five-dimensional recording process in a synthetic crystal to store massive amounts of data indefinitely.
The researchers, led by Jingyu Zhang from the University of Southampton in the U.K., successfully recorded a 300KB digital copy of a text file onto nanostructured glass in 5D using ultrafast and intense pulse laser. The file was written in three layers of nanostructured dots separated by five micrometers (five millionths of a meter).
The scientists used a femtosecond laser, which emits pulses of light in femtoseconds (one quadrillionth, or one millionth of one billionth of a second). The 5D read/write laser can record up to an estimated 360 TB/disc data capacity on nanostructured glass capable of thermal stability up to 1000°C -- and a practically unlimited lifetime.
In a statement this week, the researchers called the glass the "Superman memory crystal," alluding to the "memory crystals" used in Superman films to store the planet Kryptonite's history and its civilization's collective knowledge.
The University of Southampton researchers recorded via self-assembled nanostructures created in fused quartz, which they said is able to store the vast quantities of data for more than a million years.
The information encoding comes in five dimensions that include the size and orientation in addition to the three dimensional position of these nanostructures.
According to a recently published paper, the self-assembled nanostructures change the way light travels through glass, modifying polarization of light that can then be read by combination of optical microscope and a polarizer, similar to that found in Polaroid sunglasses.
Superman crystal
A graphic depicting a 5D optical storage writing setup: femtosecond laser, spatial light modulator (SLM), Fourier lens (FL), half-wave plates matrix (»/2 M), dichroic mirror, 1.2 NA water immersion objective, silica glass sample, translation stage. (Image: University of Southhampton)
The research was conducted as part of a joint project with Eindhoven University of Technology.
"We are developing a very stable and safe form of portable memory using glass, which could be highly useful for organizations with big archives," Jingyu said in a statement. "At the moment, companies have to back up their archives every five to 10 years because hard-drive memory has a relatively short lifespan.
"Museums who want to preserve information or places like the national archives where they have huge numbers of documents, would really benefit," he added.
This article, 'Superman' crystals could store 360TB of data forever, was originally published at Computerworld.com.

Wednesday, 30 July 2014

Installing the amazing XZDualRecovery - PhilZ Touch and CWM and TWRP ~ Ray blogs about - Linux:



'via Blog this'






































































Download from here.

http://forum.xda-developers.com/showthread.php?t=2261606

Currently supported XPERIA models:
Xperia Z: SO-02E, C6602, C6603, C6606, C6616
Xperia ZL: C6502, C6503, C6506
Xperia Tablet Z: SO-03E, SGP311, SGP312, SGP321, SGP351 
Xperia Z Ultra: C6802, C6806, C6833, C6843
Xperia Z1: C6902, C6903, C6906, C6943, C6916
Xperia Z1 Compact: D5502, D5503, D5506
Xperia Z2: D6502, D6503, D6506, D6543
Xperia Tablet Z2: SGP511, SGP512, SGP521
Xperia ZR: C5602, C5603, C5606
Xperia T, TX, TL and V: LT30p, LT29, LT30at, LT25i
Xperia S: LT26i
Xperia SP: C5302, C5303
Xperia T2 Ultra: D5303, D5322

How to use:
At boot, once you feel the phone vibrate and while you see the green led burn:
- press VOL-UP for PhilZ Touch;
- press VOL-DOWN for TWRP.


To enter Vanilla CWM, you will need to use the (free) NDRUtils app from the Play store


rayd@raydHPEliteBook8440p ~/Downloads/Sony/lockeddualrecovery $ ls
files  install.bat  install.sh
rayd@raydHPEliteBook8440p ~/Downloads/Sony/lockeddualrecovery $ ./install.sh 
[sudo] password for rayd: 




==============================================
=                                            =
=               XZDualRecovery               =
=            Maintained by [NUT]             =
=                                            =
=      For many Sony Xperia devices!         =
=                                            =
==============================================

          Choose an installation option:

          1/ Installation on device rooted with SuperSU
          2/ Installation on device rooted with SuperUser
          3/ Attempt installation on an unrooted device

          Q/ Exit

    Enter option:

3




Using TowelRoot to attempt an installation.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

=============================================
Step1 : Waiting for Device.
=============================================

Succes

=============================================
Device and firmware information:
=============================================
Device model is C6503
Firmware is 10.5.A.0.230

=============================================
Step2 : Sending the recovery files.
=============================================

0 KB/s (29 bytes in 0.040s)
345 KB/s (15757 bytes in 0.044s)
12 KB/s (501 bytes in 0.040s)
272 KB/s (11842 bytes in 0.042s)
1011 KB/s (56834 bytes in 0.054s)
72 KB/s (3082 bytes in 0.041s)
9 KB/s (385 bytes in 0.040s)
3477 KB/s (657704 bytes in 0.184s)
4309 KB/s (3015476 bytes in 0.683s)
2894 KB/s (1928498 bytes in 0.650s)
3501 KB/s (2649152 bytes in 0.738s)
199 KB/s (8759 bytes in 0.042s)

=============================================
Step3 : Setup of dual recovery.
=============================================

=============================================
Attempting to get root access for installation using TowelRoot now.

NOTE: this only works on certain ROM/Kernel versions!

If it fails, please check the development thread (Post #2) on XDA for more details.
=============================================

=============================================
Sending files
=============================================
37 KB/s (1572 bytes in 0.041s)
292 KB/s (13592 bytes in 0.045s)
2428 KB/s (197320 bytes in 0.079s)
215 KB/s (9496 bytes in 0.043s)
299 KB/s (13672 bytes in 0.044s)
Copying kernel module...
855 KB/s (34473 bytes in 0.039s)
18 KB/s (765 bytes in 0.040s)
295 KB/s (13592 bytes in 0.044s)
Kernel version is 3.4.0-perf-g32ce454
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.

modulecrcpatch (by zxz0O0)

module_layout: patched to 0x16FBCA7C
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched

=============================================
Installing using zxz0O0's towelzxperia (using geohot's towelroot library)
=============================================

towelzxperia (by zxz0O0)
thanks to geohot for libexploit

creating libzxploit.so
libzxploit.so created
doing the magic
creating vm (loljavasucks)
libdvm opened (loljavasucks)


##########################################################
#
# Installing XZDR version 2.7.153 BETA
#
#####

Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Rename stock mr
Copy mr wrapper script to system.
Rename stock chargemon
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Creating /system/.XZDualRecovery to store a backup copy of busybox.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event5!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event0!
Speeding up backups.
Make sure firstboot goes to recovery.

=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================


=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================


thanks for using towelzxperia
cleaning up
=============================================

REMEMBER THIS:

XZDualRecovery does NOT install any superuser app!!

You can use one of the recoveries to root your device.

=============================================

=============================================
Installation finished. Enjoy the recoveries!
=============================================