SanDisk Mobile Ultra Micro SDHC
Screen Shot 2014-12-14 at 11.36.02 PM

SanDisk Ultra Micro SDHC
Screen Shot 2014-12-14 at 11.36.25 PM

There’s no differences in term of performance or physical appearance. I found this solid answer:

I rang Technical Support at SanDisk to ask what’s the difference between “Mobile Ultra” and “Ultra”

“Mobile Ultra” and “Ultra” are the same card, the name difference was just for marketing purposes, to show people the card could be used in mobiles. However the plan backfired and people thought they couldn’t use “Mobile Ultra” in their camera, so the name was dropped.

To decipher the codes such as SDSDQUA-032G-U46A:
SDSD=sd card
Q =class 4 (black) available in 2,4,8,16,32GB
QY =class 6 “Ultra” (red & grey) available in 4GB (8,16,32gb discontinued but still on sale)
QUA=class 10 “Ultra” 8,16,32=SDHC 64=SDXC* (UHS-I = UHS class 1 = 10mb/s #)
QUI=class 10 “Ultra” apparently “designed for cameras” and NOT the same card (black packaging)
-032G=32GB
-U46=EU [email protected]
-A11=US [email protected]
-FFP=Amazon frustration free [email protected]
A=picture of android on package

NOTES
* Compatible devices only
# If used in a non UHS-I compliant phone, it will revert to class 10
@ If it doesn’t have a code at the end, it’s not covered by SanDisk warranty

Source:
http://forums.sandisk.com/t5/Mobile-memory-professional-cards/No-difference-between-Mobile-Ultra-and-Ultra/m-p/289540/highlight/true#M1911

Incoming search terms:

  • difference between sandisk ultra and sandisk mobile ultra

What is SSL Cipher Suite?
A cipher suite is a named combination of authentication, encryption, message authentication code (MAC) and key exchange algorithms used to negotiate the security settings for a network connection using the Transport Layer Security (TLS) / Secure Sockets Layer (SSL) network protocol

Below bash script gets a list of supported cipher suites from OpenSSL and tries to connect using each one. If the handshake is successful, it prints YES. If the handshake isn’t successful, it prints NO, followed by the OpenSSL error text.

#!/usr/bin/env bash

# OpenSSL requires the port number.
SERVER=192.168.1.11:443
DELAY=1
ciphers=$(openssl ciphers 'ALL:eNULL' | sed -e 's/:/ /g')

echo Obtaining cipher list from $(openssl version).

for cipher in ${ciphers[@]}
do
echo -n Testing $cipher...
result=$(echo -n | openssl s_client -cipher "$cipher" -connect $SERVER 2>&1)
if [[ "$result" =~ "Cipher is ${cipher}" || "$result" =~ "Cipher    :" ]] ; then
  echo YES
else
  if [[ "$result" =~ ":error:" ]] ; then
    error=$(echo -n $result | cut -d':' -f6)
    echo NO \($error\)
  else
    echo UNKNOWN RESPONSE
    echo $result
  fi
fi
sleep $DELAY
done

Here’s sample output showing 3 unsupported ciphers, and 1 supported cipher:


[@linux ~]$ ./test_ciphers
Obtaining cipher list from OpenSSL 0.9.8k 25 Mar 2009.
Testing ADH-AES256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-RSA-AES256-SHA...NO (sslv3 alert handshake failure)
Testing DHE-DSS-AES256-SHA...NO (sslv3 alert handshake failure)
Testing AES256-SHA...YES

Reference:
http://en.wikipedia.org/wiki/Cipher_suite
http://superuser.com/questions/109213/is-there-a-tool-that-can-test-what-ssl-tls-cipher-suites-a-particular-website-of
https://www.ssllabs.com/ssltest/index.html

Posted in OS.

Scenario:

Using Microsoft Windows built in VPN Client to connect to remote PPTP VPN server through Cisco ASA firewall.

Symptom:

Error 619

Solution:

In ASA Firewall, enter below command.
ASA-active#conf t
ASA-active(config)#policy-map global_policy
ASA-active(config-pmap)# class inspection_default
ASA-active(config-pmap-c)#inspect pptp
ASA-active(config-pmap-c)#exit
ASA-active(config)#access-list $Inbound_Interface_ACL permit gre $source_ip/network any
ASA-active(config)#access-list $Inbound_Interface_ACL permit permit tcp $source_ip/network any eq pptp

Common Troubleshooting in Windows VPN Client

1. Open VPN Properties window, go to Security tab.
2. Change “Type of VPN” to PPTP

Incoming search terms:

  • pptp through cisco vpn