Grab stuff from people, without any USB / HDD, over Dropbox, without them signing up on Dropbox

Dropbox new feature, FILE REQUEST allows you to do just that. Simply open a file request, send your loved one, aka the person from whom you want to file (s), a link or email them. They will just be uploading the file from browser and you will be get that file in your DropBox. They won’t be signing up with Dropbox if they don’t have dropbox. Cool isn’t it.

Qouting below from Dropbox file requests..

Use file requests to collect and receive files from anyone, right in your Dropbox account. With file requests:

  • Anyone can send you a file, whether they have a Dropbox account or not
  • All the files you collect are automatically organized into a single Dropbox folder.
  • People who upload files to your file request cannot access your Dropbox. Only you can view files uploaded by others, unless you decide to share them.

Sections in this article:

How to create a file request

  1. Sign in to
  2. Click Files.
  3. Click File requests.
  4. Click Request files.
  5. Enter a name for the folder that will store all collected files under What are you requesting?
  6. Under Where should these files go in your Dropbox?, you’ll see the path to the new folder populate. If you’d like to change the folder’s location, click Change folder.
  7. If you’re a Dropbox Professional or Business customer, you can add a deadline for these submissions. Click Add a deadline to set your deadline. You can also Allow late uploads and choose a timeframe.
  8. Click Next.
  9. Click Copy link to copy the file request link and send it to anyone you want to request files from. Or you can enter emails of the people you need files from and send the file request directly from Dropbox.
  10. Click Done.

You’ll receive an email whenever people upload files to your file request.

Note: By default the uploaded files are private. You can share the uploaded files by selecting a shared folder or by sending a link to the files.

If you want to change your file request once it’s created, follow these steps:

  1. Sign in to
  2. Click Files.
  3. Click File requests.
  4. Click the (ellipsis) icon.
  5. Click Edit.
  6. You can edit both What are you requesting? and Where should these files go in your Dropbox?
  7. Click Save.

How to close a file request

You can close a file request when you’d like to stop receiving files. Once a file request is closed, people with an invitation link can’t upload files to your Dropbox.

  1. Sign in to
  2. Click Files.
  3. Click File requests.
  4. Click the (ellipsis) icon.
  5. Click Edit.
  6. Click the Close request button.
  7. View your closed file requests from the Closed tab.

Note: You can reopen a closed file request. From the Closed tab, hover over the file request you’re interested in and click Reopen.

Do file requests take up space in my Dropbox account?

All files collected for a file request will take up space in your Dropbox account. To ensure that you can accept the files that you’re requesting, check how much spaceyou have in your account.

Note: You need enough space in your Dropbox account to receive the files sent through a file request. The people you invite to upload files will receive an error that your Dropbox account doesn’t have enough space.


How to save any Youtube video to your local system

These days, we frequently watch youtube video and a lot of times, we think, gosh I need to save this file on my PC locally.

Here is how and what you need to do.

First off, make sure, you have VLC player installed and a browser off course.

  1. Copy the desired URL from browser, open VLC.
  2. CTRL + N (Open Network Stream).
  3. Paste the URL. Wait for the Video to load in VLC. Once video is open, CTRL +J (Tools > Codec Information). At bottom of that dialog box, TRIPLE click and copy the whole URL.
  4. Switch to browser. CTRL + T (New Tab), CTRL + V (Paste) and ENTER.
  5. Once video is loaded, right click on Video and choose SAVE AS.

Voila, Video would be saved on your PC.

To be a Bug or not to be a Bug. What’s, How’s and Why’s of Bug Report

Being in a Software Testing field, process engineering, and now Application Security, I have been reading and documenting about Bug Reports but I have never came across such good, concise and precise definition of Bug Reporting.
What is Observation, Expectation, Reproducibility, and ultimately, what is Bug.

Have a look.

You’re using your computer and all of a sudden you notice something wrong. Something doesn’t seem to work correctly… it doesn’t do what you expect it to.

Is there something wrong with the hardware or with the software? Is there something wrong in your configuration or the way you’re using the computer? Are you expecting the wrong thing to happen?

You don’t know yet, but one thing is sure: What you saw didn’t match what you expected.

At this stage, this is an observation. Something looks wrong, so you start to troubleshoot.

Here’s an example of an observation:“While walking, I felt a pain in my right foot”.

Here’s an example of a valid expectation:“My shoe should not hurt my foot”.

Here’s an example of a reproducible issue:“Every time I walk, I feel a pain in my right foot”.

Here’s an example of an issue where the responsible component was identified:

“My Nike shoes hurt my right foot every time I walk. I feel no pain with other pairs of shoes, the same socks, the same places, the same amount of time.”

Changing User Agent String

How to change user agent string

During Security testing, web testing, there is dire need to change User Agent String of Browser. Here is how to change User Agent string of browser without installing any addon.

Reference URL is

Firefox Quantum, which is new version of Firefox Developer Edition, goto

  1. about:config/
  2. Search for “general.useragent.override”
  3. Add new STRING > “general.useragent.override”
  4. Value should be one of the values below.

User-Agent: <product> / <product-version> <comment>
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
User-Agent: Mozilla/<version> (<system-information>) <platform> (<platform-details>) <extensions>

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36 OPR/38.0.2220.41

Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_1 like Mac OS X) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.0 Mobile/14E304 Safari/602.1

Mozilla/5.0 (compatible; MSIE 9.0; Windows Phone OS 7.5; Trident/5.0; IEMobile/9.0)

Googlebot/2.1 (+


For those who need firefox add on, use

How manually update ZAP proxy on Kali linux.

1) Download latest version   * in my case it is ZAP_2.4.3_Linux.tar.gz

2) Untar it tar -xzvf ZAP_2.4.3_Linux.tar.gz

3) cd ZAP_2.4.3/

4) Copy new version over old : cp -Ra * /usr/share/zaproxy/

Source: IT-Security

CertSimple | Why ‘site seals’ are even worse than you thought

Why ‘site seals’ are even worse than you thoughtUltimately benefit the vendor more than their customersBy Mike on 28th Jan 2016

Site seals promote bad user behavior, have questionable impact on conversions, and make your site boost your CA’s SEO.

Read on for more.

Why site seals exists.

Certificate Authorities (CAs) have a problem:

they want to show consumers their branding but can’t. The only area of a browser users can actually trust – the address bar – doesn’t show the CA’s branding. A lock is shown, and extended validation certs show the company ID, but unless the user really likes HTTPS and starts to explore the certificate, that’s all. Validation level aside, a Symantec certificate looks like a Comodo Certificate looks like a GoDaddy Certificate. For CAs, that’s a problem.So traditional CAs created something called a ‘site seal’, ‘trust seal’, ‘secured seal’, ‘trust logo’, or ‘trust symbol’: these are all the same thing: an image showing the CA’s brand, and some JavaScript that sets up a click handler to open a report on the CA’s website (we’ll explain why the JavaScript exists later).

Heads up: we sell certificates, and occasionally get explicit requests from customers for site seals, which we’ll happily fulfill. But we don’t use site seals, and our management tools don’t encourage site seals or mention them at all. Here’s why.

Promoting misplaced trust

The report that appears when you click on a site seal mentions SSL, and may also cover additional services like malware scans, site scans, or insurance policies for misissued certificates.

The report is presented from a secured site – again, the only part of a browser you can trust is the address bar – and the report’s contents are often useful.However the seal image itself has no security value – site seals are easily copied just like any other image on the internet, and anyone wanting to do something bad wouldn’t hesitate to do so. Which is the crux of the issue:

The trust seal UI never encourages users to read the report: merely to trust the presence of the image.

Source: CertSimple | Why ‘site seals’ are even worse than you thought