Saturday, February 21, 2015
Protecting yourself against POODLE attacks by disabling SSLv3 Support in Browsers
Sunday, February 15, 2015
What is dirty db ?
It is a in-memory db used in Node.js
A tiny & fast key value store with append-only disk log. Ideal for apps with < 1 million records
This module is called dirty because:
- The file format is newline separated JSON
- Your database lives in the same process as your application, they share memory
- There is no query language, you just forEach through all records
So dirty means that you will hit a very hard wall with this database after ~1 million records, but it is a wonderful solution for anything smaller than that.
Thursday, February 12, 2015
What is gfe_rd=cr&ei= ?
It is a cookie link redirected to your browser based on the country from which it is accessed.
Which means If your enter
https://www.google.com
it will return
https://www.google.co.in/?gfe_rd=cr&ei=fgdfsg4534fdg
and browser will store the cookie and redirect to https://www.google.co.in
gfe=Google Front End
rd=Redirect
cr=Country
ei=Engine Id
This Engine Id is the cookie that is sent to our browser.
Which means If your enter
https://www.google.com
it will return
https://www.google.co.in/?gfe_rd=cr&ei=fgdfsg4534fdg
and browser will store the cookie and redirect to https://www.google.co.in
gfe=Google Front End
rd=Redirect
cr=Country
ei=Engine Id
This Engine Id is the cookie that is sent to our browser.
Sunday, February 8, 2015
.profile,.bash_profile and .bashrc
.profile
.profile is for things that are not specifically related to Bash, like environment variables PATH and friends, and should be available anytime.
For example, .profile should also be loaded when starting a graphical desktop session.
.bash_profile
.bash_profile is for making sure that both the things in .profile and .bashrc are loaded for login shells.
.bashrc
.bashrc is for the configuring the interactive Bash usage, like Bash aliases, setting your favorite editor, setting the Bash prompt, etc.
.profile is for things that are not specifically related to Bash, like environment variables PATH and friends, and should be available anytime.
For example, .profile should also be loaded when starting a graphical desktop session.
.bash_profile
.bash_profile is for making sure that both the things in .profile and .bashrc are loaded for login shells.
.bashrc
.bashrc is for the configuring the interactive Bash usage, like Bash aliases, setting your favorite editor, setting the Bash prompt, etc.
Tuesday, February 3, 2015
Can we submit an app to playstore that is signed by debug.keystore ?
No..
You can't you have to create a keystore and sign the app using that key.
Make sure the key is safe..or else you can push the update (it will cause signature error)
You can't you have to create a keystore and sign the app using that key.
Make sure the key is safe..or else you can push the update (it will cause signature error)
Labels:
android,
debug keystore,
Google Play store,
keystore
how to get the our andoird app signed by debug.keystore ?
1)Make sure you have built the app atleast one time
2)Go to the bin folder and copy the .apk file that's enough.
2)Go to the bin folder and copy the .apk file that's enough.
Labels:
android,
debug keystore,
Google Play store,
keystore
How to create debug.keystore ?
Your debug keystore gets created automatically for us the first time we build an Android app
|
Find the location of debug.keystore
Input the following command in osx terminal
mdfind debug.keystore
Sunday, February 1, 2015
Android AVD:ERROR Unable to load VM from snapshot
Starting emulator for AVD ‘AVD-NAME’ emulator: ERROR: Unable
to load VM from snapshot. The snapshot has been saved for a different
hardware configuration.
Solution:
Go to AVD manager and choose edit avd then uncheck snapshot there you go
Solution:
Go to AVD manager and choose edit avd then uncheck snapshot there you go
Android manually trigger OnBootCompleted
Windows:
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED
Osx:
./adb shell am broadcast -a android.intent.action.BOOT_COMPLETED
Emulator-5554 disconnected error message or Emulator-5554 offline
Solution 1:
- Run Emulator
- Keep the Emulator, (no matter same error occurs)
- Make Sure the Home Screen of Emulator is appeared
- go to Window -> Show Perspective -> DDMS --> In Devices Panel -> on Corner Drop Down Menu
- Reset adb
Solution 2:
Run configurations > Target > Wipe user data > Run
Subscribe to:
Posts (Atom)