Using a digital certificate to send an encrypted email.

I want to send an e-mail through my i-pad using a digital certificate, that i have already configurated in my e-mail account. This e-mail i want to send also encrypted. Do i need to have a public certificate code from the person i´m sending the e-mail to? Like outlook express works?
thanks for the answer in advance

Hello,
Your best option will be to use an encoder for feedback in your system. If you use an encoder then at the end of the move, the controller will compare your trajectory position with the position the encoder reads (the actual position) and make the necessary adjustments. Also, this is all handled transparently so you won't have to worry about any complicated programming issues.
Regards,
Andy Bell
Applications Engineer
National Instruments

Similar Messages

  • How do I use outlook digital id's to read encrypted email?

    I'm strugging with this one. I have an exchange account that makes use of digital ID's to encrypt email using MS Digifal ID's. Is there a location or feature on the iPhone4 where I can use the imported ID to let me read email that's been encrypted with s/mime on the iphone4?

    OR... *sorry" is there a third party application that I can put on the iPhone4 to allow me to do this?

  • VPN error when using Microsoft digital certificates.

    Hi,
    I tried implementing site-site VPN between Cisco Router and Cisco ASA using Microsoft digital certificates. After performing the following configurations, I was not able to ping to other site LAN. I enabled debug and got following out put. I sucessfully enrolled digital certificates.
    Cisco ASA config:
    access-list 100 extended permit ip 10.1.1.0 255.255.255.0 192.168.1.0 255.255.255.0
    nat (inside) 0 access-list 100
    static (inside,outside) 1.1.1.10 10.1.1.10 netmask 255.255.255.255
    route outside 0.0.0.0 0.0.0.0 1.1.1.2 1
    crypto ipsec transform-set myset esp-3des esp-sha-hmac
    crypto map mymap 1 match address 100
    crypto map mymap 1 set peer 2.2.2.2
    crypto map mymap 1 set transform-set myset
    crypto map mymap interface outside
    crypto ca trustpoint winca
    enrollment url http://10.1.1.10:80/certsrv/mscep/mscep.dll
    crl configure
    crypto isakmp enable outside
    crypto isakmp policy 10
    authentication rsa-sig
    encryption 3des
    hash sha
    group 2
    lifetime 86400
    tunnel-group 2.2.2.2 type ipsec-l2l
    tunnel-group 2.2.2.2 ipsec-attributes
    trust-point winca
    On router:
    crypto ca trustpoint winca
    enrollment mode ra
    enrollment url http://1.1.1.10:80/certsrv/mscep/mscep.dll
    crypto isakmp policy 19
    encr 3des
    group 2
    authentication rsa-sig
    crypto isakmp key cisco address 1.1.1.1
    crypto map mymap 10 ipsec-isakmp
    set peer 1.1.1.1
    set transform-set myset
    match address 100
    access-list 100 permit ip 192.168.1.0 0.0.0.255 10.1.1.0 0.0.0.255
    crypto ipsec transform-set myset esp-3des esp-sha-hmac
    Debug output on ASA
    CorpASA# Nov 15 02:12:49 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, Removing peer from peer table failed, no match!
    Nov 15 02:12:49 [IKEv1]: Group = 2.2.2.2, IP = 2.2.2.2, Error: Unable to remove PeerTblEntry
    CorpASA#
    CorpASA#
    CorpASA# Nov 15 02:13:06 [IKEv1]: Removing peer from peer table failed, no match!
    Nov 15 02:13:06 [IKEv1]: Error: Unable to remove PeerTblEntry
    Nov 15 02:13:11 [IKEv1]: Removing peer from peer table failed, no match!
    Nov 15 02:13:11 [IKEv1]: Error: Unable to remove PeerTblEntry
    Debug out put on router:
    R2#ping 10.1.1.10 source 192.168.1.1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.1.1.10, timeout is 2 seconds:
    Packet sent with a source address of 192.168.1.1
    Nov 15 02:21:01.067: %SYS-5-CONFIG_I: Configured from console by console
    Nov 15 02:21:02.651: ISAKMP: received ke message (1/1)
    Nov 15 02:21:02.655: ISAKMP (0:0): SA request profile is (NULL)
    Nov 15 02:21:02.655: ISAKMP: local port 500, remote port 500
    Nov 15 02:21:02.655: ISAKMP: set new node 0 to QM_IDLE
    Nov 15 02:21:02.655: ISAKMP: insert sa successfully sa = 64597C20
    Nov 15 02:21:02.655: ISAKMP (0:1): Can not start Aggressive mode, trying Main mode.
    Nov 15 02:21:02.659: ISAKMP: Looking for a matching key for 1.1.1.1 in default : success
    Nov 15 02:21:02.659: ISAKMP (0:1): found peer pre-shared key matching 1.1.1.1
    Nov 15 02:21:02.659: ISAKMP (0:1): constructed NAT-T vendor-07 ID
    Nov 15 02:21:02.659: ISAKMP (0:1): constructed NAT-T vendor-03 ID
    Nov 15 02:21:02.659: ISAKMP (0:1): constructed NAT-T vendor-02 ID
    Nov 15 02:21:02.659: ISAKMP (0:1): Input = IKE_MESG_FROM_IPSEC, IKE_SA_REQ_MM
    Nov 15 02:21:02.663: ISAKMP (0:1): Old State = IKE_READY  New State = IKE_I_MM1
    Nov 15 02:21:02.663: ISAKMP (0:1): beginning Main Mode exchange
    Nov 15 02:21:02.663: ISAKMP (0:1): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) MM_NO_STATE
    Nov 15 02:21:02.703: ISAKMP (0:1): received packet from 1.1.1.1 dport 500 sport 500 Global (I) MM_NO_STATE
    Nov 15 02:21:02.707: ISAKMP (0:1): Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
    Nov 15 02:21:02.707: ISAKMP (0:1): Old State = IKE_I_MM1  New State = IKE_I_MM2
    Nov 15 02:21:02.707: ISAKMP (0:1): processing SA payload. message ID = 0
    Nov 15 02:21:02.707: ISAKMP (0:1): processing vendor id payload
    Nov 15 02:21:02.707: ISAKMP (0:1): vendor ID seems Unity/DPD but major 194 mismatch
    Nov 15 02:21:02.711: ISAKMP : Scanning profiles for xauth ...
    Nov 15 02:21:02.711: ISAKMP (0:1): Checking ISAKMP transform 1 against priority 19 policy
    Nov 15 02:21:02.711: ISAKMP:      encryption 3DES-CBC
    Nov 15 02:21:02.711: ISAKMP:      hash SHA
    Nov 15 02:21:02.711: ISAKMP:      default group 2
    Nov 15 02:21:02.711: ISAKMP.:      auth RSA sig
    Nov 15 02:21:02.711: ISAKMP:      life type in seconds
    Nov 15 02:21:02.711: ISAKMP:      life duration (VPI) of  0x0 0x1 0x51 0x80
    Nov 15 02:21:02.715: ISAKMP (0:1): atts are acceptable. Next payload is 0
    Nov 15 02:21:02.771: ISAKMP (0:1): processing vendor id payload
    Nov 15 02:21:02.771: ISAKMP (0:1): vendor ID seems Unity/DPD but major 194 mismatch
    Nov 15 02:21:02.775: ISAKMP (0:1): Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
    Nov 15 02:21:02.775: ISAKMP (0:1): Old State = IKE_I_MM2  New State = IKE_I_MM2
    Nov 15 02:21:02.783: ISAKMP (0:1): constructing CERT_REQ for issuer cn=md902j-n5dros99,dc=md902j,dc=ca,dc=com
    Nov 15 02:21:02.783: ISAKMP (0:1): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) MM_SA_SETUP
    Nov 15 02:21:02.783: ISAKMP (0:1): Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
    Nov 15 02:21:02.787: ISAKMP (0:1): Old State = IKE_I_MM2  New State = IKE_I_MM3
    Nov 15 02:21:02.903: ISAKMP (0:1): received packet from 1.1.1.1 dport 500 sport 500 Global (I) MM_SA_SETUP
    Nov 15 02:21:02.907: ISAKMP (0:1): Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
    Nov 15 02:21:02.907: ISAKMP (0:1): Old State = IKE_I_MM3  New State = IKE_I_MM4
    Nov 15 02:21:02.907: ISAKMP (0:1): processing KE payload. message ID = 0
    Nov 15 02:21:02.979: ISAKMP (0:1): processing NONCE payload. message ID = 0
    Nov 15 02:21:02.987: ISAKMP (0:1): SKEYID state generated
    Nov 15 02:21:02.991: ISAKMP (0:1): processing CERT_REQ payload. message ID = 0
    Nov 15 02:21:02.991: ISAKMP (0:1): peer wants a CT_X509_SIGNATURE cert
    Nov 15 02:21:02.995: ISAKMP (0:1): peer want cert issued by cn=md902j-n5dros99,dc=md902j,dc=ca,dc=com
    Nov 15 02:21:02.995: ISAKMP (0:1): Choosing trustpoint winca as issuer
    Nov 15 02:21:02.995: ISAKMP (0:1): processing vendor id payload
    Nov 15 02:21:02.995: ISAKMP (0:1): vendor ID is Unity
    Nov 15 02:21:02.999: ISAKMP (0:1): processing vendor id payload
    Nov 15 02:21:02.999: ISAKMP (0:1): vendor ID seems Unity/DPD but major 11 mi.smatch
    Nov 15 02:21:02.999: ISAKMP (0:1): vendor ID is XAUTH
    Nov 15 02:21:02.999: ISAKMP (0:1): processing vendor id payload
    Nov 15 02:21:02.999: ISAKMP (0:1): speaking to another IOS box!
    Nov 15 02:21:02.999: ISAKMP (0:1): processing vendor id payload
    Nov 15 02:21:03.003: ISAKMP (0:1:): vendor ID seems Unity/DPD but hash mismatch
    Nov 15 02:21:03.003: ISAKMP (0:1): Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
    Nov 15 02:21:03.003: ISAKMP (0:1): Old State = IKE_I_MM4  New State = IKE_I_MM4
    Nov 15 02:21:03.007: ISAKMP (0:1): Send initial contact
    Nov 15 02:21:03.067: ISAKMP (1): My ID configured as IPv4 Addr,but Addr not in Cert!
    Nov 15 02:21:03.067: ISAKMP (1): Using FQDN as My ID
    Nov 15 02:21:03.067: ISAKMP (0:1): SA is doing RSA signature authentication using id type ID_FQDN
    Nov 15 02:21:03.067: ISAKMP (0:1): ID payload
            next-payload : 6
            type         : 2
            FQDN name    : R2.cisco.com
            protocol     : 17
            port         : 500
            length       : 20
    Nov 15 02:21:03.067: ISAKMP (1): Total payload length: 20
    Nov 15 02:21:03.095: ISAKMP (0:1): constructing CERT payload for hostname=R2.cisco.com
    Nov 15 02:21:03.095: ISKAMP: growing send buffer from 1024 to 3072
    Nov 15 02:21:03.095: ISAKMP (0:1): using the winca trustpoint's keypair to sign
    Nov 15 02:21:03.215: ISAKMP (0:1): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) MM_KEY_EXCH
    Nov 15 02:21:03.219: ISAKMP (0:1): Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
    Nov 15 02:21:03.219: ISAKMP (0:1): Old State = IKE_I_MM4  New State = IKE_I_MM5
    Nov 15 02:21:03.375: ISAKMP (0:1): received packet from 1.1.1.1 dport 500 sport 500 Global (I) MM_KEY_EXCH
    Nov 15 02:21:03.375: ISAKMP: set new node -1205710646 to QM_IDLE
    Nov 15 02:21:03.379: ISAKMP (0:1): received packet from 1.1.1.1 dport 500 sport 500 Global (I) MM_KEY_EXCH
    Nov 15 02:21:03.379: ISAKMP (0:1): received packet from 1.1.1.1 dport 500 sport 500 Global (I) MM_KEY_EXCH
    Nov 15 02:21:03.383: ISAKMP (0:1): received packe.t from 1.1.1.1 dport 500 sport 500 Global (I) MM_KEY_EXCH
    Nov 15 02:21:03.383: ISAKMP (0:1): received packet from 1.1.1.1 dport 500 sport 500 Global (I) MM_KEY_EXCH
    Nov 15 02:21:03.383: ISAKMP: Info Notify message requeue retry counter exceeded sa request from 1.1.1.1 to 2.2.2.2...
    Success rate is 0 percent (0/5)
    R2#
    Nov 15 02:21:13.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH...
    Nov 15 02:21:13.219: ISAKMP (0:1): incrementing error counter on sa, attempt 1 of 5: retransmit phase 1
    Nov 15 02:21:13.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH
    Nov 15 02:21:13.219: ISAKMP (0:1): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) MM_KEY_EXCH
    R2#
    Nov 15 02:21:23.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH...
    Nov 15 02:21:23.219: ISAKMP (0:1): incrementing error counter on sa, attempt 2 of 5: retransmit phase 1
    Nov 15 02:21:23.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH
    Nov 15 02:21:23.219: ISAKMP (0:1): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) MM_KEY_EXCH
    R2#
    Nov 15 02:21:32.651: ISAKMP: received ke message (1/1)
    Nov 15 02:21:32.651: ISAKMP: set new node 0 to QM_IDLE
    Nov 15 02:21:32.651: ISAKMP (0:1): SA is still budding. Attached new ipsec request to it. (local 2.2.2.2, remote 1.1.1.1)
    Nov 15 02:21:33.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH...
    Nov 15 02:21:33.219: ISAKMP (0:1): incrementing error counter on sa, attempt 3 of 5: retransmit phase 1
    Nov 15 02:21:33.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH
    Nov 15 02:21:33.219: ISAKMP (0:1): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) MM_KEY_EXCH
    R2#
    Nov 15 02:21:43.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH...
    Nov 15 02:21:43.219: ISAKMP (0:1): incrementing error counter on sa, attempt 4 of 5: retransmit phase 1
    Nov 15 02:21:43.219: ISAKMP (0:1): retransmitting phase 1 MM_KEY_EXCH
    Nov 15 02:21:43.219: ISAKMP (0:1): sending packet to 1.1.1.1 my_port 500 peer_port 500 (I) MM_KEY_EXCH
    PLease assist me in sorting this issue, i need to implement on my live network.
    Thanks a lot in advance.
    Regards,
    Mohan.D

    HI Mate ,
    your ASA is sending the ASA certificate :
    but after that we are recieving an isakmp notify message which tears down the connection ?
    somehow the remote peer didn't like the ASA certificate
    do you have access to that peer ? is it a CISCO ASA?
    is the time synchronized with that side ?
    it the CA certificate installed on that peer?
    HTH
    Mohammad.

  • HT4864 Can you use Windows Live Mail to send/recieve iCloud email and share contacts or can I just use iCloud email on my PC without use Live Mail?

    Can you use Windows Live Mail to send/recieve iCloud email and share contacts or can I just use iCloud email on my PC without use Live Mail? I want to use one email adress, one contact list and one calendar. I want to be able to have access to all this on my iphone and pc.

    You can only use Mail, contacts and calendars will not work, for that you need Outlook.

  • ASA site-site VPN error using Microsoft Digital Certificates.

    Hi,
    I configured site-site between ASA's with authentication type as RSA-SIG for Phase1. I got manual certificates from Microsoft CA Server but not able to form the tunnel. Need someones help badly on this issue.
    ASA1 Config:
    crypto isakmp identity address
    crypto isakmp enable outside
    crypto isakmp policy 10
    authentication rsa-sig
    encryption 3des
    hash sha
    group 1
    lifetime 86400
    crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    tunnel-group 200.160.126.30 type ipsec-l2l
    tunnel-group 200.160.126.30 ipsec-attributes
    peer-id-validate cert
    trust-point CA1
    crypto map outside_map 1 match address vpn
    crypto map outside_map 1 set peer 200.160.126.30
    crypto map outside_map 1 set transform-set ESP-3DES-SHA
    crypto map outside_map 1 set trustpoint CA1
    crypto map outside_map interface outside
    access-list vpn extended permit ip 172.16.1.0 255.255.255.0 192.168.1.0 255.255.255.0
    crypto ca trustpoint CA1
    enrollment terminal
    fqdn asa1.cisco.com
    keypair my.ca.key
    crl configure
    ASA-2 Config:
    crypto isakmp identity address
    crypto isakmp enable outside
    crypto isakmp policy 10
    authentication rsa-sig
    encryption 3des
    hash sha
    group 1
    lifetime 86400
    crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
    crypto map outside_map 1 match address vpn
    crypto map outside_map 1 set peer 59.160.128.50
    crypto map outside_map 1 set transform-set ESP-3DES-SHA
    crypto map outside_map 1 set trustpoint CA1
    crypto map outside_map interface outside
    tunnel-group 59.160.128.50 type ipsec-l2l
    tunnel-group 59.160.128.50 ipsec-attributes
    peer-id-validate cert
    trust-point CA1
    access-list vpn extended permit ip 192.168.1.0 255.255.255.0 172.16.1.0 255.255.255.0
    crypto ca trustpoint CA1
    enrollment terminal
    fqdn asa2.cisco.com
    keypair my.ca.key
    crl configure
    Debug Output:
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-5-713041: IP = 59.160.128.50, IKE Initiator: New Phase 1, Intf inside, IKE Peer 59.160.128.50  local Proxy Address 172.16.1.0, remote Proxy Address 192.168.1.0,  Crypto map (outside_map)
    %ASA-7-715046: IP = 59.160.128.50, constructing ISAKMP SA payload
    %ASA-7-715046: IP = 59.160.128.50, constructing Fragmentation VID + extended capabilities payload
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE SENDING Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 108
    %ASA-7-609001: Built local-host NP Identity Ifc:200.160.126.30
    %ASA-7-609001: Built local-host outside:59.160.128.50
    %ASA-6-302015: Built outbound UDP connection 122 for outside:59.160.128.50/500 (59.160.128.50/500) to NP Identity Ifc:200.160.126.30/500 (200.160.126.30/500)
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + SA (1) + VENDOR (13) + NONE (0) total length : 108
    %ASA-7-715047: IP = 59.160.128.50, processing SA payload
    %ASA-7-713906: IP = 59.160.128.50, Oakley proposal is acceptable
    %ASA-7-715047: IP = 59.160.128.50, processing VID payload
    %ASA-7-715049: IP = 59.160.128.50, Received Fragmentation VID
    %ASA-7-715064: IP = 59.160.128.50, IKE Peer included IKE fragmentation capability flags:  Main Mode:        True  Aggressive Mode:  True
    %ASA-7-715046: IP = 59.160.128.50, constructing ke payload
    %ASA-7-715046: IP = 59.160.128.50, constructing nonce payload
    %ASA-7-715046: IP = 59.160.128.50, constructing certreq payload
    %ASA-7-715046: IP = 59.160.128.50, constructing Cisco Unity VID payload
    %ASA-7-715046: IP = 59.160.128.50, constructing xauth V6 VID payload
    %ASA-7-715048: IP = 59.160.128.50, Send IOS VID
    %ASA-7-715038: IP = 59.160.128.50, Constructing ASA spoofing IOS Vendor ID payload (version: 1.0.0, capabilities: 20000001)
    %ASA-7-715046: IP = 59.160.128.50, constructing VID payload
    %ASA-7-715048: IP = 59.160.128.50, Send Altiga/Cisco VPN3000/Cisco ASA GW VID
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE SENDING Message (msgid=0) with payloads : HDR + KE (4) + NONCE (10) + CERT_REQ (7) + VENDOR (13) + VENDOR (13) + VENDOR (13) + VENDOR (13) + NONE (0) total length : 322
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + KE (4) + NONCE (10) + CERT_REQ (7) + VENDOR (13) + VENDOR (13) + VENDOR (13) + VENDOR (13) + NONE (0) total length : 322
    %ASA-7-715047: IP = 59.160.128.50, processing ke payload
    %ASA-7-715047: IP = 59.160.128.50, processing ISA_KE payload
    %ASA-7-715047: IP = 59.160.128.50, processing nonce payload
    %ASA-7-715047: IP = 59.160.128.50, processing cert request payload
    %ASA-7-715047: IP = 59.160.128.50, processing VID payload
    %ASA-7-715049: IP = 59.160.128.50, Received Cisco Unity client VID
    %ASA-7-715047: IP = 59.160.128.50, processing VID payload
    %ASA-7-715049: IP = 59.160.128.50, Received xauth V6 VID
    %ASA-7-715047: IP = 59.160.128.50, processing VID payload
    %ASA-7-715038: IP = 59.160.128.50, Processing VPN3000/ASA spoofing IOS Vendor ID payload (version: 1.0.0, capabilities: 20000001)
    %ASA-7-715047: IP = 59.160.128.50, processing VID payload
    %ASA-7-715049: IP = 59.160.128.50, Received Altiga/Cisco VPN3000/Cisco ASA GW VID
    %ASA-7-713906: IP = 59.160.128.50, Generating keys for Initiator...
    %ASA-7-715046: IP = 59.160.128.50, constructing ID payload
    %ASA-7-715046: IP = 59.160.128.50, constructing cert payload
    %ASA-7-715001: IP = 59.160.128.50, constructing RSA signature
    %ASA-7-715076: IP = 59.160.128.50, Computing hash for ISAKMP
    %ASA-7-713906: Constructed Signature Len: 128
    %ASA-7-713906: Constructed Signature:
    0000: 4FB66432 FCA9DA52 5420E6C1 DF8293AC     O.d2...RT ......
    0010: DE3533F1 7036E5C8 40B11A9D 5C68C884     .53.p6..@...\h..
    0020: D4BCA531 BAE87710 09D1AD06 7994CD1B     ...1..w.....y...
    0030: DCEDB9CE E971F21B 0104C06A 1901FACE     .....q.....j....
    0040: D1E8AED1 7684DFDA 40E98BC2 E195F3C8     ....v...@.......
    0050: 3625E936 E35F47A3 F44BC326 62E99135     6%.6._G..K.&b..5
    0060: 88EB90FF 10938CC3 0FFAA576 A9DBD9AD     ...........v....
    0070: 65592C71 5A13C4C5 8EBA60F6%ASA-7-715034: IP = 59.160.128.50, Constructing IOS keep alive payload: proposal=32767/32767 sec.
    %ASA-7-715046: IP = 59.160.128.50, constructing dpd vid payload
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE SENDING Message (msgid=0) with payloads : HDR + ID (5) + CERT (6) + SIG (9) + IOS KEEPALIVE (128) + VENDOR (13) + NONE (0) total length : 1668
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-609001: Built local-host inside:172.16.1.10
    %ASA-7-609001: Built local-host outside:192.168.1.10
    %ASA-7-609002: Teardown local-host inside:172.16.1.10 duration 0:00:00
    %ASA-7-609002: Teardown local-host outside:192.168.1.10 duration 0:00:00
    %ASA-7-715077: Pitcher: received a key acquire message, spi 0x0
    %ASA-6-713219: IP = 59.160.128.50, Queuing KEY-ACQUIRE messages to be processed when P1 SA is complete.
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE RECEIVED Message (msgid=0) with payloads : HDR + NOTIFY (11) + NONE (0) total length : 68
    %ASA-5-713904: IP = 59.160.128.50, Received an un-encrypted INVALID_COOKIE notify message, dropping
    %ASA-4-713903: IP = 59.160.128.50, Information Exchange processing failed
    %ASA-7-715065: IP = 59.160.128.50, IKE MM Initiator FSM error history (struct &0xd8a30d08)  <state>, <event>:  MM_DONE, EV_ERROR-->MM_WAIT_MSG6, EV_PROB_AUTH_FAIL-->MM_WAIT_MSG6, EV_TIMEOUT-->MM_WAIT_MSG6, NullEvent-->MM_SND_MSG5, EV_SND_MSG-->MM_SND_MSG5, EV_START_TMR-->MM_SND_MSG5, EV_RESEND_MSG-->MM_WAIT_MSG6, EV_TIMEOUT
    %ASA-7-713906: IP = 59.160.128.50, IKE SA MM:f2cbbafa terminating:  flags 0x0100c022, refcnt 0, tuncnt 0
    %ASA-7-713906: IP = 59.160.128.50, sending delete/delete with reason message
    %ASA-7-715046: IP = 59.160.128.50, constructing blank hash payload
    %ASA-7-715046: IP = 59.160.128.50, constructing IKE delete payload
    %ASA-7-715046: IP = 59.160.128.50, constructing qm hash payload
    %ASA-7-713236: IP = 59.160.128.50, IKE_DECODE SENDING Message (msgid=372e03ac) with payloads : HDR + HASH (8) + DELETE (12) + NONE (0) total length : 80
    %ASA-3-713902: IP = 59.160.128.50, Removing peer from peer table failed, no match!
    %ASA-4-713903: IP = 59.160.128.50, Error: Unable to remove PeerTblEntry
    Kindly suggest me for further steps.
    Regards,
    Mon

    HI Mate ,
    your ASA is sending the ASA certificate :
    but after that we are recieving an isakmp notify message which tears down the connection ?
    somehow the remote peer didn't like the ASA certificate
    do you have access to that peer ? is it a CISCO ASA?
    is the time synchronized with that side ?
    it the CA certificate installed on that peer?
    HTH
    Mohammad.

  • Is there a way to authenticate an iPad to our WLAN using a digital certificate and then authorize the user in Active Directory?

    We want to authenticate both a device (iPad) to our corporate WLAN, but after authenticating the device we would also like to authentiate the user in Active Directory if possible.  Has anyone had any experience with this?

    You need to make sure that the server sends the "GeoTrust DV SSL CA" intermediate certificate.
    See:
    * http://www.networking4all.com/en/support/tools/site+check/ (www.ucfs.net)
    * https://knowledge.geotrust.com/support/knowledge-base/index?page=content&id=SO9557
    * https://knowledge.geotrust.com/support/knowledge-base/index?page=content&id=AR1422

  • Can I purchase a iTunes gift certificate to send to an email address via the iTunes app and not via the desktop?

    It would be super convenient to be able to purchase the gift certificate via email option from the iPhone using the iTunes app or even the Apple Store app so the recipient receives immediately but I don't see that this is possible.  I also can't see my purchase history without logging into the computer. This seems super odd for apple not to provide all options from the iPhone directly so I must be overlooking something. At this time of the year and with the economy as bad as it is, I'm not too keen to send gift cards in the mail!
    Thanks much for the help.

    mandyfar wrote:
    I got a gift card that says "Itunes"on it and not "apple"or something like that...
    I was wondering if that gift card can only be used on the itunes store, meaning I can only buy songs, tv shows, music videos , etc.. ...
    That is Correct...
    iTunes Gift Options
    http://support.apple.com/kb/HT2736

  • Is it possible to send encrypted email messages using cfmail ?

    Does anyone know of a way to send an encrypted email message
    using CF?

    Sending an encrypted message is easy. The hard part is
    enabling the recipient to decrypt it.

  • Cant choose which digital certificate to sign outgoing email in Mail.app

    I am posting this here as this post:
    http://discussions.apple.com/message.jspa?messageID=5746197#5746197
    was archived.
    I just wanted to add that this is still an issue for us. We use three digital certificates inside our organization, one from Thawte, one from caCert, and one from our in-house/private CA. All three work perfectly inside all applications that we use them in. There is on issue which is that if the user clicks the icon on the far right side of their outgoing email to "sign" that email, there is no telling which certificate it will use. We want to use the one from Thawte for all outgoing email but it ends up picking one of the other ones instead & as far as I can tell there is no way to control this or change this.
    What I am requesting is that Mail.app ask me which certificate I want to use, either once, in preferences, or each email, or something, as sendind with the wrong one is really not workable.
    I think 10.5.2 is a real step forward. Thanks for all the hardwork to make the improvements in it that we see.
    Thanks so much.
    Sjobeck

    Somewhere online I found mention that you can assign the cert you don't want to use as untrusted and the one you do want to use as trusted. So in Keychain, double click on your Thawte cert, click on the Trust arrow and change the "When using this certificate:" drop down to "Always Trust". Do the opposite for your other certs.
    This way you can still use your other certs for decrypting if anyones uses it to send to you. But you'll always use the trusted cert for signing/encrypting new messages.
    I too wish there was a way to explicitly select the cert you want to use but till they allow that, this is the best way I've found to work around the issue.

  • Sending encrypted emails from the iPad is not working

    I can't get sending encrypted emails working on my iPad3 running iOS 8.0.2
    Let me explain what I did:
    1. I created S/MIME certificates for 2 email addresses on my iMac in Keychain Access. One email address exists only on the iMac the other only on the iPad.
    2. I set "When using this certificate" to "Always Trust" in both certificates.
    3. I exported 1 S/MIME certificate (p12) and installed it on the iPad. Then I deleted this certificate and its private&public keys in iMac Keychain Access
    4. I exchanged public certificates between the 2 devices. I installed one certificate in iMac Keychain Access and the other in iPad/Settings/General/Profiles.
    5. On the iMac in the iPad certificate I set "When using this certificate" to "Always Trust"
    6. I tested whether I can send and receive signed and/or encrypted emails
    Results:
    1. From the iMac I can send signed and/or encrypted emails to the iPad.
        On the iPad I can read the encrypted emails. The signature is not trusted
    2. On the iPad I can send signed messages to the iMac. On the iMac the signature is trusted.
        I cannot send encrypted emails from the iPad to the iMac. The iPad doesn't know about the public certificate in iPad/Settings/General/Profiles
    So much for the straight forward part. Now it gets a bit more complicated and confusing.
    1. I deleted the iMac certificate in the iPad/Settings/General/Profiles. Then in iPad Mail I opened the signed mail coming from the iMac.
        I viewed the untrusted certificate in Mail and installed it. From this point on all signed emails from the iMac are trusted.
        Strangely the by this method installed certificate doesn't appear in iPad/Settings/General/Profiles.
        Furthermore I still cannot send encrypted messages to the iMac. This certificate installation seems to be used only to check trust worthiness of the signature.
        Installing on top the iMac public certificate in iPad/Settings/General/Profiles doesn't enable to send encrypted messages from the iPad either.
    To be sure that this problem relates to the iPad certificate management and is not related to an error by me I did the following:
    1. I transferred a p12 file for a certificate that I created in my iMac to a PC running Windows7.
    2. I transferred a p12 file plus its public key (.pem) that I created in my iMac to another iMac into Keychain Access. (I have not tested if the pem is needed).
    3. On the other iMac and the PC I made sure that the certificates are trusted.
        On the PC that means in the Certificate Manager the p12 needs to be in the "Personal" folder and in the "Trusted Root Certification Authorities" folder.
        The public keys need to be in the "Trusted People" folder and the "Other People" folder. One can just copy/paste the certificates.
    4. In both cases I deleted the certificate and public/private keys on my iMac.
    5. I exchanged public certificates between the devices.
    6. I tested exchanging signed and/or encrypted emails between my iMac and the PC and my iMac and the other iMac.
    Result:
    1. I can send signed and/or encrypted emails to the other iMac and the PC
    2. The PC and the other iMac trust the signature from my iMac and can read the encrypted emails
    3. My iMac can read encrypted emails from the PC and the other iMac
    4. My iMac trusts emails with signatures from the PC and the other iMac.
    Everything is working as it should.
    After the above test I wanted to see whether I can set up encrypted email exchange between the iPad and the PC. Strangely iPad Mail recognized the public certificate from the PC installed in iPad/Settings/General/Profiles and allowed me to send an encrypted email to the PC. However, on the PC I was unable to read the encrypted email. And the other way around, encrypted emails send from the PC to the iPad cannot be read on the iPad.
    My conclusion from all this testing is that iPad mail encryption is still "under construction".

    I was able to resolve the above described problem to some degree. Setting up sending and receiving encrypted emails between iOS and OSX I have working.
    What is still not working is reading encrypted emails on the iPad/iOS8 received from Windows 7 PC. And sending encrypted emails to Windows 7 PC.
    The details about how I solved part of the problem are described here.

  • Unable to send encrypted emails to recipients with valid, trusted certs

    I'm trying to send an encrypted email to a recipient for whom I have a valid, trusted cert. When I view his cert in Keychain, it gets a green check mark for being valid. Under Trust, I have "Always Trust" selected for "Secure Mime (S/MIME)" and "X.509 Basic Policy". All the certs in the chain are in place and trusted with these same settings.
    Signed emails from this user get a black check mark in the Security field of the Mail message viewer. I can also click the lock closed when writing the email. However, when I click Send, I get an error that "An error occurred while trying to encrypt your message. Verify that you have valid certificates in the keychain for all of the recipients."
    I have the cert for the user plus the others in the trust chain in my login keychain as described above. I have a DoD ECA certificate, but this happens with non-ECA recipients. I'm unable to get the lock to close with ECA recipients or even get Mail to show that signatures from users with ECA certificates are valid.
    Any help would be greatly appreciated!
    Thanks,
    Andreas

    You said you were closing the lock on the certificate, or public key, which I've never had to to to send or receive encrypted email.
    There are encryption and signature icons that appear under the Subject field in the compose message window. Both of them default to On when I enter the name of someone for whom I have an ECA cert. If the person has a CAC cert, then the Lock icon appears open and I can't close it.
    However, the error message you're getting suggests that maybe all your recipients haven't provided their public key to you so that you can encrypt email to them.
    This ties into my comment about everything working fine in Vista/Outlook: I'm using the exact same certs and can send everyone encrypted email
    Thanks,
    Andreas

  • Do you have to deal with a CA to get digital certificates?

    Hi,
    I'm investigating the use of digital certificates for communication
    between our WLS internally. I would like to be able to generate my own
    certificates and keys for our testing purposes. I'm under the impression
    that the only way to do this is to deal with a Verisign or somethin like
    that and to buy a license. Am I correct? Or is there another way to do
    this?
    Thanks,
    L
    Laurent Duperval <mailto:[email protected]>
    Je suis le plus fort! ... Je suis encore plus fort que tout à l'heure! ...
    Tiens... pour me définir, le mot fort ne l'est plus assez!
    -Léonard le génie

    thanks everyone, helped alot, cant wait to buy one of these

  • Problem encrypting email when composing New Message

    This may be a bug in Mail app version 4.2 (1078). I am trying to send an encrypted email to a recipient. I already have the recipient's public key in Key Access. If i click on the New Message button and i enter the recipient's email address, the encrypt button is greyed out and i cannot click on it to encrypt the email. However, if i click on the Reply button or if i click on the sender's name and choose the "New Message" option in a digitally signed email sent to me earlier, i can encrypt the email without any problem.
    I have tried deleting the recipient's entry in my address book and add it back by clicking on his name and selecting "Add to Address Book" in the digitally signed email sent to me, but still, that did not help.
    Anyone else seen this before?

    Same problem here.
    I made sure that both certificates were created with the Data Encipherment option set, but the padlock icon never gets enabled.
    Erwin

  • Encryption emails leaving local Exchange 2003 are blank

    I inherited a network with Exchange 2003 where the client is trying to get email encryption going with the outside.  They have email certs and the certs work for digitally signing emails, whether they send to internal or external recipients, and for
    digitally encrypting emails when they send to internal recipients only.
    However, when we send an encrypted email to an external address, the body is blank, the email does not appear to be encrypted, and it shows that there is an attachment (smime.p7m) which, I believe, is the encrypted content.  These same recipients work
    with encrypted emails all of the time, so it is not them.
    Any help you can provide would be enormously appreciated - I am new to Exchange administration and it doesn't seem like the previous tech was too good at it, either.
    Thank you!

    If the size of the message about what you'd expect it to be when it's sent from your organization?
    If ESMTP is used to send the message, and the SIZE keyword is present on the MAIL FROM command, you can find that information in your SMTP protocol log. You can also use a network monitor (e.g. Wireshark) to capture the session and reconstitute the
    message to have a look at it -- if it's not being sent using an encrypted session.
    You may be falling afoul of the old "message sent in RTF" problem. Try sending the message in plain text or HTML and see if the results are different.
    --- Rich Matheisen MCSE&I, Exchange MVP

  • Encrypted email shows up decrypted when recieved from collegues account where it was sent to, w/o his private cert installed

    I have 2 email accounts in Thunderbird 24.5.0.
    Account 1: My Account, s/mime and certs properly setup for signature/encryption
    Account 2: Collegues Account, no s/mime etc. set up, no private cert installed in thunderbird. He has his certificates of course.
    When I send an encrypted email from my account (1) to my collegues account (2), and I receive this email from his account (2) in my Thunderbird it comes up _de_crypted in my inbox. How is that possible w/o having his private certificate installed?
    Also in certificate manager I only have my certificates installed.
    Also in the sent box the message shows up decrypted, but source only shows the encrypted message.
    If I understood encryption properly I use his public key/cert (wich I automatically get from a server) to encrypt a message to him. This message can only be decrypted using his private key/cert. Without me having his private key/cert installed I, as for my understanding, should not be able to read the email I have sent to him when I receive it in my thunderbird (ir in sent items)?
    Is TB somehow recognizing that I myself had the message encrypted and therefor displays it decrypted when I receive it from my collegues account? It shows the message in clear text in send objects too even though the source is encrypted. What mechanism is behind that? Again, w/o my collegues private cert/key I should, as for my understanding, not be able to read the mail, neither in sent nor inbox...
    Thanks a lot,
    Oliver

    Hi Matt,
    I'm fully aware that I use my collegues public key to encrypt the message I send to him. But I would need his private key to display it decrypted. However when receive an email from his account, wich was sent from mine and encrypted with his public key from my side, it shows the decrypted message in my inbox and sent items. How does TB display the decrypted message from my collegues account w/o me having his private cert? If one could decrypt the public key encrypted message with the public key it would render the encryption system useless. So TB must store the pre-encrypted message somewhere and recognize, upon receiving it, that its actually the same message sent from the same thunderbird installation.
    I assume that based on the following:
    When I send an email from my collegues computer from his account to his account and encrypt it, it shows the expected "message can't be decrypted"-message when I receive it on my computer. So the reason for displaying the decrypted/non-encrypted message must be that TB stored the uncrypted content somewhere and recognize it's the same email upon receive.
    Greets,
    Oliver

Maybe you are looking for