Skip to main content

Is it possible to control over terrorism with New Technologies “Passports with Radio Tags”



             A few years a go, the United States government required nearly all passports to have a computer chip with the passport holder’s personal information. This contains the name, nationality, gender, date of birth and place and a digitized photo of the passport holder. Allowing this to protect the cardholder and makes it more difficult for criminals to get away with tampering passports.
        Like everything else, this brings up privacy issues.
With these passports, this exposes people’s identity to strangers. The State Department made security precautions to prevent this from happening. The RFID tags will use digital signatures to prevent tampering, and only when it is within inches of an RFID reader will the information be accessible.
These passports have a “multilayered approach” which protects privacy to reduce people from stealing data. This metallic “anitskimming material” is located in the front cover and spine of the book and prevents it from being read in the distance. However, because the digitized picture is required it helps to make it impossible for posers to make copies and forge someone’s identity.
The biggest downfall here with the RFID tags in the passports, is that the government, once again, has access to tracking your every move. Essentially with the passport being closed it supposedly cannot be read unless it is near a RFID reader, but once you come near a reader your information is handed over and you are being tracked.
Is this just another technology where the government is trying to track people? Or do you this is a necessity and not an invasion of privacy?
If this can control the Terrorism Y cant be apply in INDIA....? 

Comments

Popular posts from this blog

Google re-branded the support Android libraries to AndroidX

It is important to note, you cannot mix AppCompat and Jetpack in the same project. You must convert everything to use Jetpack if you want to upgrade. The support library artifacts are being deprecated and all future development is going into AndroidX , so there's no avoiding this migration. Alan Viverette sums this up nicely: “There won’t be a 29.0.0, so Android Q APIs will only be in AndroidX” The stable release of 28.0.0 will be the final feature release packaged as android.support . All subsequent feature releases will only be made available as androidx-packaged artifacts. Below tips will give you a clearer transition path. The current version of AppCompat (v28.x) is exactly the same as AndroidX (v1.x). In fact, the AppCompat libraries are machine generated by changing maven coordinates and package names of the AndroidX codebase. For example, android.support.v7.app.AppCompatActivity is now androidx.appcompat.app.AppCompatActivity For a complete listi

Android Beginners Guide

                                                                                                               Android Operation System: Android is an operating system based on Linux with a Java programming interface. It provides tools, e.g. a compiler, debugger and a device emulator as well as its own Java Virtual machine (Dalvik Virtual Machine - DVM). Android is created by the Open Handset Alliance which is lead by Google. Android uses a special virtual machine, e.g. the Dalvik Virtual Machine. Dalvik uses special bytecode. Therefore you cannot run standard Java bytecode on Android. Android provides a tool "dx" which allows to convert Java Class files into "dex" (Dalvik Executable) files. Android applications are packed into an .apk (Android Package) file by the program "aapt" (Android Asset Packaging Tool) To simplify development Google provides the Android Development Tools (ADT) for Eclipse. The ADT performs automatically the conversion f

Android Pi migration(28 API support)

I am here to give some inputs on android PI migration. .  Apps must target at least API level 28 to ensure it is built on the latest APIs optimized for security and performance . From August 2019, new apps must target at least Android 9.0 (API level 28) . The objective here is to make sure that your existing app works as-is on Android 9. Because some platform changes might affect the way your app behaves, some adjustments might be necessary, but you do not need to use new APIs or change your targetSdkVersion. Android Service Problem On Oreo, startService() will throw IllegalStateException. This can be fixed by changing it to startForegroundService(). but it also stops the service immediately if you don’t bind to the Notification with Service.startForeground() within 5 seconds. For other background service we decided to use the WorkManager . Implementation: Since we have minSdkVersion 19, We migrated to workmanger for scheduled tasks and we still use JobIntentSer