Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #374181

Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router

From GreyCloud <Cumulus@mist.com>
Newsgroups comp.os.linux.advocacy
Subject Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router
Date 2016-10-02 10:21 -0600
Organization A noiseless patient Spider
Message-ID <nsrc5t$e15$1@dont-email.me> (permalink)
References (8 earlier) <ahjdg.ea094@perch.invalid> <nsp45n$459$1@dont-email.me> <ahjdgod3.aug@perch.invalid> <nspdkj$4h2$1@dont-email.me> <nsr1t5$b93$1@dont-email.me>

Show all headers | View raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/02/2016 07:26 AM, Silver Slimer wrote:
> On 2016-10-01 06:34 PM, GreyCloud wrote:
>> On 10/01/2016 02:51 PM, Octavian W. Lagrange wrote:
>>> GreyCloud <Cumulus@mist.com> wrote:
>>>> On 10/01/2016 01:21 PM, Octavian W. Lagrange wrote:
>>>>> GreyCloud <Cumulus@mist.com> wrote:
>>>>>> On 09/30/2016 08:30 PM, Marek Novotny wrote:
>>>>>>> On 2016-09-30, GreyCloud <Cumulus@mist.com> wrote:
>>>>>>>> The instructions I have so far are old and vague for 
>>>>>>>> Thunderbird. Which keyserver do you want?  I need a
>>>>>>>> bit more info on the key and where it is located on
>>>>>>>> my system.  I tried to pgp site and it said my key
>>>>>>>> type is too old for some reason and didn't conform to
>>>>>>>> a newer version.
>>>>>>> 
>>>>>>> I got it now.
>>>>>>> 
>>>>>> 
>>>>>> I have to start over again.  Sorry about that. I'll 
>>>>>> eliminate this old key and start afresh and post the
>>>>>> public key again. Maybe I was off sequence here, so I had
>>>>>> to rethink the sequences again.
>>>>>> 
>>>>> 
>>>>> Your key is fine.  There's really no need to do that.  But 
>>>>> whatever you do, first things first:  Use gpg on the
>>>>> command line to verify that you can decrypt messages
>>>>> encrypted to that key.
>>>>> 
>>>>> gpg -d <message>
>>>>> 
>>>>> After you know that encryption, decryption, and signing
>>>>> are working, then work on the integration with a usenet
>>>>> client. Got to isolate the source of the problem, and it
>>>>> won't help if you don't know that the core stuff is
>>>>> working.
>>>>> 
>>>> The decryption works ok, just that encryption is not. It
>>>> keeps telling me my key has expired.  Not sure why enigmail
>>>> is saying that.
>>>> 
>>> 
>>> Forget enigmail for a minute.  Use gpg commandline:
>>> 
>>> anon@lowtide:~$ cat plaintext.txt some text anon@lowtide:~$
>>> gpg -r owl -o encrypted.asc -a -e plaintext.txt anon@lowtide:~$
>>> head encrypted.asc -----BEGIN PGP MESSAGE----- Version: GnuPG
>>> v1
>>> 
>>> hQEMA2brmWp7kbAKAQgAk2V+Vybk64jVSYCJa+utu7RAcQGgW+mQpkTyITVx7Kts
>>>  
>>> F99QZpFSbbIU8HZBsKC5SyrbgbCtiON231w/+F2Tpac3gOwvwcIMfc+lqCBK320L
>>>  
>>> j8Z87OcUWUhGYnhDpWFtJ5C/anMV0drDfSNLOUqYGl6pNeLzonjAk5amp5JzRnDF
>>>  
>>> lMarDpWwLnGl2z5S0Wh0xbhEspYZ1dW3QQmxMKdwq6NuiU1hXwBGqKpdXhtULJCT
>>>  
>>> 9sBAaJyXaPa2ktB+kkkTnrNIjb1JnzW/grZi8VxhXxw2+Mv3NeNg08qSQVKumw6J
>>>  
>>> CcID4lAOgweK0Ep/fPS8/bZd6F6dIONB2M2G2QvLS9JRAa4Ye9GEWmkD99U2/ctR
>>>  
>>> vWu97IZIYWn+MaVQrBqW3MG/Wp8IJ/i9NB7AtrBEeqng9/fr4ozJ7NrtGnTmHdj0
>>>  anon@lowtide:~$
>>> 
>>> Do that for your my key and post the file encrypted.asc, or do
>>> it for your own key and then decrypt:
>>> 
>>> anon@lowtide:~$ gpg -d encrypted.asc
>>> 
>>> You need a passphrase to unlock the secret key for user: "owl 
>>> (usenet) <owl@rooftop.invalid>" 2048-bit RSA key, ID 7B91B00A, 
>>> created 2015-04-27 (main key ID B0984AAB)
>>> 
>>> gpg: encrypted with 2048-bit RSA key, ID 7B91B00A, created 
>>> 2015-04-27 "owl (usenet) <owl@rooftop.invalid>" some text 
>>> anon@lowtide:~$
>>> 
> 
>> gpg: decryption failed: No secret key
> 
> I'll try to explain this in the manner I wish someone would have to
> me a while back:
> 
> - When you create a GPG key, you have a set of both private and
> public keys. - The private key is the one you have a password on
> and it is what the system will use to encrypt information. This one
> should stay secret at all times and remain local on your computer. 
> - The public key is the one you share with others so that their
> system knows how to encrypt information TO you. However, if you
> want to decrypt their messages, you need their public key as well. 
> - Every time you communicate with those people, you need to be
> select their public key in composing the message to make sure that
> they will be able to read what you just encrypted.
> 
> - If the system tells you that there is no secret key, it means
> that you did not associate a keypair (private+public) with your
> e-mail address somewhere in the settings. There's the Enigmail
> settings but there's also the Account Settings. In the Account
> Settings (Edit - Preferences) there is a section called OpenPGP
> security in which you must choose your secret key and configure the
> defaults. Be careful _NOT_ to use "PGP/MIME."
> 
> 

I didn't do that part.  Really didn't need to after setting the pgp
preferences in enigmail.  Then I refreshed the key servers with the
new one.  It's working fine now.

In the old days of crypto for the NSA, things really haven't changed
that much.  Then you had a crypto card book, and I had to do this
everyday known as changeover.  The other end also had the same crypto
book.  Then both of us by flagging the other guy to change and start
the synching process.  When both machines indicated a synch, we'd set
the switch to run.  Funny part is that all the different types of
crypto machines has a build in card cutter, so that you could never
use it again.  Anyway, the computer part is a bit more complicated and
I'm not used to it yet.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJX8TQIAAoJEMfxH5jgl5XRSxAP/iNuPV0R51WLMlGD4rqDieOW
lelIspU1Jo985BBRSBoXTKvfZU8J5itxKL9VXpmTHJknYZ3Lys8YCIwXQeImyBUZ
bNG2vhB7nA6LEe8LN6KkAWiCM5ISrwzaiqXyf3CByLTc0Gi/8T0r8EMb6wf/rGJ/
ms6SrHtrnmbpukCugr334fYo+0+Inj/vJerhMiFiGrdAVQcX/hmwKkMbZ4jPoiZD
+GF6ohNSzr2wYuc75R3voSxjfFAfLCbj/TN9TKpGhnOkUDRZQAfZ2d3FyyN/Ty5f
DaCShURE7LaUYzlA5uOCG6dxRrQFCt68p7MeTP+Ar1Z5eK8jo2uyMxzHjj7390B9
RAX2q33D6njAKaTNuQqDFnkDY4Wz+IW3oGr0KRy9kpye1MXdne6D+TKf8EXPqb3t
Z33VfFAxyM7IgVxjc0P1LSpzE+irw6IiEjrXRhE4MVjG4otOYIaGh69ral2JQXi6
QI+1Kc/ak67lAps8vRswecn4KzWCpJ080CTtbVd/fwG6i3imVdTlUStYcaArQeL3
WDsE1tDj+ZvOEBBH43Q489f6VRuqtocGUz5gK83UzlnJxlm5nRSYPWI4haUz+A50
27SixFU2LXeCrGfJjlgs2FENKWHWkh87hAegVc1HEG57Zz1LbZdqSb3MhDe0k3eG
+mz6SbbHpEASoXrcQsHt
=Msxp
-----END PGP SIGNATURE-----

Back to comp.os.linux.advocacy | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Multiple Backdoors found in D-Link DWR-932 B LTE Router Marek Novotny <marek.novotny@marspolar.com> - 2016-09-29 15:36 +0000
  Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Snit <usenet@gallopinginsanity.com> - 2016-09-29 08:55 -0700
    Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Takuya Saitoh <taka0038@gmail.com> - 2016-09-30 11:46 -0700
  Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-29 11:23 -0600
    Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 01:15 +0000
      Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Snit <usenet@gallopinginsanity.com> - 2016-09-29 19:02 -0700
        Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-29 22:42 -0600
          Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Snit <usenet@gallopinginsanity.com> - 2016-09-29 21:52 -0700
          Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Silver Slimer <.m@nsn.s> - 2016-09-30 08:43 -0400
            Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Marek Novotny <marek.novotny@marspolar.com> - 2016-09-30 15:10 +0000
              Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Jim Polaski <jpolaski@linuxmail.org> - 2016-09-30 15:38 +0000
            Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Snit <usenet@gallopinginsanity.com> - 2016-09-30 08:24 -0700
              Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Steve Carroll <fretwizzer@gmail.com> - 2016-09-30 08:55 -0700
            Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-30 15:10 -0600
              Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-10-01 01:08 +0200
              Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-30 18:27 -0600
      Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-29 22:41 -0600
      Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-30 15:15 -0600
        Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Marek Novotny <marek.novotny@marspolar.com> - 2016-09-30 21:38 +0000
          Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 22:07 +0000
            Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-30 17:19 -0600
              Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-01 00:15 +0000
            Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Marek Novotny <marek.novotny@marspolar.com> - 2016-10-01 02:29 +0000
          Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-09-30 17:18 -0600
            Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Marek Novotny <marek.novotny@marspolar.com> - 2016-10-01 02:30 +0000
              Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-10-01 13:09 -0600
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-01 19:21 +0000
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Steve Carroll <fretwizzer@gmail.com> - 2016-10-01 12:26 -0700
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-01 19:36 +0000
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-10-01 13:52 -0600
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-01 20:51 +0000
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-10-01 16:34 -0600
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-01 22:49 +0000
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-10-01 17:13 -0600
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Marek Novotny <marek.novotny@marspolar.com> - 2016-10-02 00:29 +0000
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-10-02 01:01 +0000
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Silver Slimer <.m@nsn.s> - 2016-10-02 09:31 -0400
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-10-02 10:16 -0600
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Silver Slimer <.m@nsn.s> - 2016-10-02 09:26 -0400
                Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router GreyCloud <Cumulus@mist.com> - 2016-10-02 10:21 -0600
        Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 21:38 +0000
        Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 21:46 +0000
        Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 21:54 +0000
        Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Silver Slimer <.m@nsn.s> - 2016-09-30 17:57 -0400
        Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 22:36 +0000
  Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-09-30 08:07 -0400
    Re: Multiple Backdoors found in D-Link DWR-932 B LTE Router Marek Novotny <marek.novotny@marspolar.com> - 2016-09-30 15:09 +0000

csiph-web