Instructions For On-Line Registration And Fee Payment: Fill & Download for Free

Candidates can apply online by visiting the website http://upneet.gov.infollow these steps carefully:For registration candidate will use his/her NEET-UG Roll No. and email ID(that is used for registration in AI-NEET-UG) and follow instructions on screen.Thereafter the candidates AI-NEET-UG registration details will be displayed.The candidate will make an online payment of Rs. 1,000/- (through debit/credit/internet banking only) towards registration fees.Candidate will be able to generate his/her own password, which will ease further login and SMS will be sent to his/her registered mobile no (that was used for AI-NEET-UG registration) confirming successful on-line registration. Please keep the mobile active as it will also be used for OTP for choice filling.Only those candidates making successful online payment of Rs. 1000/- (once only) shall be considered for inclusion in state merit list. After successful payment candidate will get Transaction no. and Registration no, and will be able to take the print out of the same.Registration no. and Transaction no. will be used later for Choice filling.After state merit list is declared, online seat choice filling option will be available as per the notified schedule.Candidate would be able to take a print out of his/her online registration and save.For Inter-se rank in State merit list reference shall be AI-NEET-UG 2017 ranking .Merit list will be prepared as per the provisions.ALL THE BEST !!!

Cracked versions of software are created with the use of debuggers. (A debugger is a special type of software that lets programmers deconstruct their software into its constituent parts for the purpose of finding bugs, and thus de-bugging. Additionally debuggers can be used for reverse-engineering, or to see what is inside the software, to learn its logic. The latter method is used mostly by malware researchers to study what malware (or computer viruses) do on-the-inside. But it can be also used by an attacker to "crack" (or bypass) legal software registration, or at times, to alter normal behavior of software, for instance by injecting a malicious code into it.)For the sake of this example, I will assume that the software that is being "cracked" was compiled into a native code, and is not a .NET or a JavaScript based application. (Otherwise it will be somewhat trivial to view its source code.) The compiled native code is a bit more tricky "beast" to study. (Native means that the code executes directly by the CPU, GPU, or other hardware.)So let's assume that the goal of an attacker is to bypass the registration logic in the software so that he or she doesn't have to pay for it. (Later for lolz, he or she may also post such "crack" on some shady online forum or on a torrent site so that others can "use" it too and give him or her their appreciation.)For simplicity let's assume that the original logic that was checking for the software registration was written in C++ and was something similar to the following code snippet:In this code sample "RegistrationName" and "RegistrationCode" are special strings of text that a legitimate software user will receive after paying for the license. (The name is usually that person's actual name or their email address, and the code is some string of unique/special characters that is tied to the name.)In the logic above, the function named "isRegistrationCodeGood()" will check if "RegistrationName" and "RegistrationCode" are accepted using some proprietary method. If they are, it will return true. Otherwise false. That outcode will dictate which branch (or scope) the execution will follow.So the logic above will either show that registration failed and quit:Or, if the registration code and name matched, it will save the registration details in persistent storage (such as the File System or System Registry) using the function named "rememberRegistrationParameters()" and then display the message thanking the user for registering:A "cracker" will obviously want to achieve the second result for any registration code that he or she enters. But they have a problem. They do not have the C++ source code, part of which I showed above. (I hope not!)So the only recourse for an attacker is to disassemble the binary code (that always ships with software in the form of .exe and .dll files on Windows, and mostly as Unix executables inside the .app packages on a Mac.) An attacker will then use a debugger to study the binary code and try to locate the registration logic that I singled out above.Next you can see the flowchart for a snippet of code that I showed in C++, presented via a low-level debugger. Or, as the code will be read in the binary form after compilation:(For readability I added comments on the right with the names of functions and variables. They will not be present in the code that an attacker could see.)(To understand what is shown above an attacker will have to have good knowledge of the Assembly language instructions for the native code.)I also need to point out that having a disassembly snippet like the one above is the final result for an attacker. The main difficulty for him or her is to locate it among millions and millions of other similar lines of code. And that is their main challenge. Not many people can do it and that is why software "cracking" is a special skill.So having found the code snippet above in the software binary file a "cracker" has two choices:1) Modify (or patch) the binary.2) Reverse-engineer the "isRegistrationCodeGood()" function and copy its logic to create what is known as a "KeyGen" or "Key Generator."Let's review both:The first choice is quite straightforward. Since an attacker got this far, he or she knows the Intel x64 Instruction Set quite well. So they simply change the conditional jump from "jnz short loc_7FF645671430" at the address 00007FF645671418 (circled in red in the screenshots) to unconditional jump, or "jmp short loc_7FF645671430". This will effectively remove any failed registration code entries and anything that the user types in will be accepted as a valid registration.Also note that this modification can be achieved by changing just one byte in the binary code from 0x75 to 0xEB:But this approach comes with a "price" of modifying the original binary file. For that an attacker needs to write his own "patcher" (or a small executable that will apply the modification that I described above.) The downside of this approach for an attacker is that patching an original executable file will break its digital signature, which may alert the end-user or the vendor. Additionally the "patcher" executable made by an attacker can be easily flagged and blocked by the end-user's antivirus software, or lead criminal investigators to the identity of the attacker.The second choice is a little bit more tricky. An attacker will have to study "isRegistrationCodeGood()" function and copy it into his own small program that will effectively duplicate the logic implemented in the original software and let him generate the registration code from any name, thus giving any unscrupulous user of that software an ability to register it without making a payment.Vendors of many major software products understand the potential impact of the second method and try to prevent it by requiring what is known as "authentication." This is basically a second step after registration, where the software submits registration name to the company's web server that returns a response back to the software of whether the code was legitimate or not. This is done by Microsoft when you purchase Windows (they call it "Activate Windows") and also by Adobe, and many other companies. This second step may be done behind-the-scenes on the background while the software is running, and will usually lead to cancellation of prior registration if it was obtained illegally.So now you know how software is "cracked".Let me answer why it is not possible to prevent it. It all boils down to the fact that any software code needs to be read either by CPU (in case of a binary native code) or by an interpreter or a JIT compiler (in case of JavaScript or .NET code.) This means that if there's a way to read/interpret something, no matter how complex or convoluted it is, an attacker with enough knowledge and persistence will be able to read it as well, and thus break it.There is an argument though that cloud-based software is more secure, which is true, since its (binary) code remains on the server and end-users do not have direct access to it. And even though cloud-based software is definitely the future, it has some major drawbacks that will never allow it to fully replace your conventional software. To name just a few:Not everyone has an internet connection, or is willing to upload their data online. Additionally someone’s internet connection can be very expensive or too slow to make the software run very laggy.Then there’s a question of distributed computing. For instance, Blizzard Entertainment would never make “World of Warcraft” to fully run on their servers due to immense computational resources needed to render every single scene for every player they have. Thus it is in their best interest to let each individual user’s computer to do the rendering instead.As a software developer myself, I obviously don't like when people steal software licenses. But I have to accept it and live with it. The good news is that there are not that many people who are willing to go extra mile and search for a cracked version of software. The main problem for those who do, is that by downloading a patched executable, or an attacker's KeyGen or a Patcher, they are effectively "trusting" him or her not to put anything "nasty" into it that was not "advertised on the package" (stuff like trojans, malware, or keyloggers.) So the question for those people becomes -- is it worth the cost of the software license to potentially infect your system with a nasty virus?On the other side of the equation, some developers react very negatively to any attempts to steal their software licenses. (I was there too.) They try to implement all kinds of countermeasures -- anything from tricking reverse-engineers, to adding booby traps in the code that may do something nasty if the code detects that it is being debugged, to obfuscating or scrambling the code, to enforcing all kinds of convoluted DRM schemes, to blocking users from certain countries. I personally try to stay away from all of those measures. And here's why:A) Any kind of anti-reverse-engineering tactics could be bypassed by an attacker with enough persistence. So why bother and waste my time when I can invest that time into adding something useful to my software that will make it more productive for legitimate users?B) Some code packers could create false positives with antivirus software, which is obviously not good for marketing of that software. It also creates unnecessary complexity for the developer to debug the software.C) Adding booby traps in the code can also “misfire” on your legitimate users, which will really infuriate them and can even lead to lawsuits.D) Any DRM scheme will probably catch some 100 illegal users and greatly inconvenience 10,000 legitimate ones. So why do it to your good customers?E) Our statistics show that about 75% of all illegal licenses come from China, Russia, Brazil, to name the worst offenders. (I also understand that the reason may be much lower incomes that people have in those countries.) The main issue for us though was the fact that if we enforce our DRM or add some strong registration authentication, many people that wanted to bypass our registration would simply use a stolen credit card number. And we had no control over it. Our system will use it to send them a legitimate license only to have the payment bounce in weeks time. As a result we would lose the money that were paid for the license, plus the credit card company will impose an additional chargeback fee to our account, which may range from $0.25 to $20 per bad purchase on top of the license cost.F) As was pointed out in the comments, some companies may actually benefit from allowing pirated copies of their software. Microsoft for instance gets a lot of free publicity from people using their Windows OS, the same goes for Adobe with their Photoshop. That is a good point that I agree with.So my philosophy is now this -- if someone wants to go extra mile and steal our software, go for it! They went this far to do it anyway, so they probably have a good reason. On the positive side there are so many other customers that appreciate the work that goes into creating software that greatly outnumber those that don’t.PS. Thank you everyone! It makes me feel good that the knowledge I shared is useful to others.If you want to see more of my tech articles, check out my blog at dennisbabkin.com/blog

This answer will guide you through the process of filing an RTI application.Online MethodThe online method makes it extremely easy to file RTIs and also makes it easier to appeal against the order on such application. Unfortunately, this service, for now, is only available for Central Government Departments and Ministries including the PMO, the Secretariat of the President and the Vice-President and Lok Sabha and Rajya Sabha Secretariat. The following steps will guide you through filing of RTI application onlineIdentify the department from which you are seeking information from. You can use the respective website of the department or a do a quick research in order to make sure you file the application with the right department.Visit http://rtionline.gov.in. On the Home-Page of the website, you will find an option for the login of Registered Users. Please note that registration is not mandatory, you can choose to register or move directly to the “Submit Request” option.Click on the “Submit Request” tab and go through the guidelines for the use of the RTI online portal. Once done, click on the “I have read and understood the above guideline” checkmark and click on “Submit.”Fill out the form. The form consists of the options to chose the department of the central government and the public authority. Then it requires mostly personal details. Do not forget to provide a working email id and phone number. In the “Text for RTI Request application” text box you need to provide the questions about the subject upon which you seek information. The said text box has a 3000 character limit. In order to put in more text, you can click and attached supporting documents through the “supporting document” option below the text box.5. The form is not processed until the payment is made. A nominal fee of INR 10 needs to be paid, which can be done through a credit or debit card, or through internet banking. If you have an account with a state bank, the process gets even simpler. You can now make the payment from you RuPay cards.6. Once the payment is made you are provided a Registration ID along with the receipt. You must have the receipt for future reference. The Registration ID will provide you access to your application and the reply.Important points:Keep an eye on the Status Report of your application, which is available on the website, or track your e-mail alerts. This will ensure you are notified of any additional fees/documents you might need to submit.As per the Act, a reply should occur within 30 days. If your application is not processed (or answered) within that time, you may submit an appeal through the website.Offline MethodThe Offline Method of RTI application is a little complicated but is easy none the less. The steps involved are as follows.Like in the case of online application you need to first identify the government and the authority from which you seek the information.Once the above step is complete, you need to address an application on a white sheet of paper to the “Public Information Officer” of such authority or department, followed by the name and address of the department.In the Subject line of the application mention this line “Seeking Information Under the RTI Act, 2005.”You must enlist all such points in the form of questions upon which you wish to receive information. Include details if you need specific information such as dates and years.Once the application is complete, do not forget to mention the date of the application and the details of the postal order of Rupees 10 which you need to attach along with the application. These Postal Orders can be obtained from any post office in India mostly before 3 PM. Also, the people below poverty line are not required to attach the postal order or make the fee payment, but they must attach a copy of the BPL Certificate.Sign the Application form with your full name and address along with the date and send it through a registered post to the office of the concerned authority.If a reply is not received within 30 days, an appeal can be filed with the Appellate Authority.