Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211847 > unrolled thread
| Started by | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| First post | 2019-07-29 12:50 +0200 |
| Last post | 2019-08-03 17:40 +0200 |
| Articles | 20 on this page of 97 — 25 participants |
Back to article view | Back to linux.debian.user
Wireless home LAN - WiFi vs Bluetooth? Richard Owlett <rowlett@cloud85.net> - 2019-07-29 12:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-07-29 13:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Richard Owlett <rowlett@cloud85.net> - 2019-07-29 14:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-07-29 14:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Dan Ritter <dsr@randomstring.org> - 2019-07-29 15:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? deloptes <deloptes@gmail.com> - 2019-07-30 11:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? John Hasler <jhasler@newsguy.com> - 2019-07-29 16:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Richard Owlett <rowlett@cloud85.net> - 2019-07-29 17:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? john doe <johndoe65534@mail.com> - 2019-07-29 14:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-07-29 15:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Dan Ritter <dsr@randomstring.org> - 2019-07-29 15:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-07-29 15:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Dan Ritter <dsr@randomstring.org> - 2019-07-29 16:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 17:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Dan Ritter <dsr@randomstring.org> - 2019-07-29 18:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? John Hasler <jhasler@newsguy.com> - 2019-07-29 16:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Erik Christiansen <dvalin@internode.on.net> - 2019-07-29 16:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 16:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? rhkramer@gmail.com - 2019-07-30 05:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? John Hasler <jhasler@newsguy.com> - 2019-07-29 17:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-07-29 21:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 22:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-07-29 22:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 23:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? ghe <ghe@slsware.net> - 2019-07-29 23:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Gene Heskett <gheskett@shentel.net> - 2019-07-30 00:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-30 03:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-07-30 09:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Erik Christiansen <dvalin@internode.on.net> - 2019-07-30 13:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? John Hasler <jhasler@newsguy.com> - 2019-07-30 14:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Matthew Crews <mailinglists@mattcrews.com> - 2019-07-30 14:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Michael Stone <mstone@debian.org> - 2019-07-30 15:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-30 21:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-07-30 21:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-31 00:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Michael Stone <mstone@debian.org> - 2019-07-30 21:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-31 00:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? "Martin McCormick" <martin.m@suddenlink.net> - 2019-08-01 14:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? John Hasler <jhasler@newsguy.com> - 2019-07-30 15:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Gene Heskett <gheskett@shentel.net> - 2019-07-30 16:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-30 16:30 +0200
3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? rhkramer@gmail.com - 2019-07-30 17:40 +0200
Re: 3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? Erik Christiansen <dvalin@internode.on.net> - 2019-07-31 09:50 +0200
Re: 3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-07-31 10:00 +0200
Re: 3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-08-01 15:50 +0200
Re: 3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? rhkramer@gmail.com - 2019-08-01 19:10 +0200
Re: 3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-08-01 21:50 +0200
Re: 3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? "James H. H. Lampert" <jamesl@touchtonecorp.com> - 2019-08-01 22:20 +0200
Re: 3 phase power (was Re: Wireless home LAN - WiFi vs Bluetooth? Gene Heskett <gheskett@shentel.net> - 2019-08-01 23:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? mick crane <mick.crane@gmail.com> - 2019-08-03 18:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-08-03 20:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? mick crane <mick.crane@gmail.com> - 2019-08-03 21:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 23:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Patrick Bartek <nemommxiv@gmail.com> - 2019-07-29 17:30 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-07-31 01:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Joe <joe@jretrading.com> - 2019-07-31 09:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-08-02 16:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-07-31 09:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-07-31 14:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-07-31 15:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Brian <ad44@cityscape.co.uk> - 2019-07-31 15:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-07-31 15:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Ben Caradoc-Davies <ben@transient.nz> - 2019-08-01 03:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-08-01 04:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-08-01 04:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-08-01 08:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-08-01 04:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-08-01 08:40 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-01 08:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Reco <recoverym4n@enotuniq.net> - 2019-08-01 10:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-08-02 05:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Celejar <celejar@gmail.com> - 2019-08-02 05:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-31 22:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 17:00 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Patrick Bartek <nemommxiv@gmail.com> - 2019-07-29 17:20 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Richard Owlett <rowlett@cloud85.net> - 2019-07-29 18:00 +0200
PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Richard Owlett <rowlett@cloud85.net> - 2019-07-29 19:00 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 23:10 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Richard Owlett <rowlett@cloud85.net> - 2019-07-30 05:20 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} David Wright <deblis@lionunicorn.co.uk> - 2019-08-03 17:50 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} mick crane <mick.crane@gmail.com> - 2019-08-04 14:00 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} <tomas@tuxteam.de> - 2019-08-04 14:10 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Richard Hector <richard@walnut.gen.nz> - 2019-08-04 17:20 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} rhkramer@gmail.com - 2019-08-05 18:50 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} David Wright <deblis@lionunicorn.co.uk> - 2019-08-05 22:00 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-06 07:50 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} David Wright <deblis@lionunicorn.co.uk> - 2019-08-06 15:40 +0200
Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-07 08:50 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? Patrick Bartek <nemommxiv@gmail.com> - 2019-07-29 19:10 +0200
Re: Wireless home LAN - WiFi vs Bluetooth? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 18:40 +0200
Useful links - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Richard Owlett <rowlett@cloud85.net> - 2019-08-03 15:20 +0200
Re: Useful links - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Lee <ler762@gmail.com> - 2019-08-03 17:00 +0200
Re: Useful links - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Richard Owlett <rowlett@cloud85.net> - 2019-08-03 17:30 +0200
Re: Useful links - was {Re: Wireless home LAN - WiFi vs Bluetooth?} David Wright <deblis@lionunicorn.co.uk> - 2019-08-03 17:50 +0200
Re: Useful links - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Brian <ad44@cityscape.co.uk> - 2019-08-03 21:20 +0200
Re: Useful links - was {Re: Wireless home LAN - WiFi vs Bluetooth?} Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-03 18:20 +0200
Re: Useful links - was {Re: Wireless home LAN - WiFi vs Bluetooth?} David Wright <deblis@lionunicorn.co.uk> - 2019-08-03 17:40 +0200
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2019-07-31 15:40 +0200 |
| Message-ID | <ypWZI-1R7-9@gated-at.bofh.it> |
| In reply to | #211972 |
On Wed 31 Jul 2019 at 16:07:33 +0300, Reco wrote: > On Wed, Jul 31, 2019 at 07:58:54AM -0400, Celejar wrote: > > mathematical analysis of how much hardware would be necessary to crack > > a good WPA2 password. I've seen lots of sites explaining how to use > > hashcat with a GPU, and various real-world tests on lists of hashed > > passwords (e.g., [1]), but can you provide a serious analysis of the > > practical cost, in time or hardware, of cracking a real-world WPA setup? > > Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > Tesla videocard. > Said hour is more than enough to bruteforce 8 character WPA passphrase > with hashcat. In the context of a home user producing a secure wireless configuration, a 64 random character passphrase works wonders. The sky is not about to fall in. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-07-31 15:50 +0200 |
| Message-ID | <ypX9o-1V2-15@gated-at.bofh.it> |
| In reply to | #211974 |
On Wed, Jul 31, 2019 at 02:32:25PM +0100, Brian wrote: > On Wed 31 Jul 2019 at 16:07:33 +0300, Reco wrote: > > > On Wed, Jul 31, 2019 at 07:58:54AM -0400, Celejar wrote: > > > mathematical analysis of how much hardware would be necessary to crack > > > a good WPA2 password. I've seen lots of sites explaining how to use > > > hashcat with a GPU, and various real-world tests on lists of hashed > > > passwords (e.g., [1]), but can you provide a serious analysis of the > > > practical cost, in time or hardware, of cracking a real-world WPA setup? > > > > Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > > Tesla videocard. > > Said hour is more than enough to bruteforce 8 character WPA passphrase > > with hashcat. > > In the context of a home user producing a secure wireless configuration, > a 64 random character passphrase works wonders. The sky is not about to > fall in. Agreed. If 64 character password is reasonably random, bruteforcing it is economically unfeasible. With obvious exceptions, of course. Entering such password to a device is somewhat tedious though. Reco
[toc] | [prev] | [next] | [standalone]
| From | Ben Caradoc-Davies <ben@transient.nz> |
|---|---|
| Date | 2019-08-01 03:20 +0200 |
| Message-ID | <yq7V8-m3-7@gated-at.bofh.it> |
| In reply to | #211975 |
On 01/08/2019 01:44, Reco wrote: > On Wed, Jul 31, 2019 at 02:32:25PM +0100, Brian wrote: >> On Wed 31 Jul 2019 at 16:07:33 +0300, Reco wrote: >>> On Wed, Jul 31, 2019 at 07:58:54AM -0400, Celejar wrote: >>>> mathematical analysis of how much hardware would be necessary to crack >>>> a good WPA2 password. I've seen lots of sites explaining how to use >>>> hashcat with a GPU, and various real-world tests on lists of hashed >>>> passwords (e.g., [1]), but can you provide a serious analysis of the >>>> practical cost, in time or hardware, of cracking a real-world WPA setup? >>> Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA >>> Tesla videocard. >>> Said hour is more than enough to bruteforce 8 character WPA passphrase >>> with hashcat. >> In the context of a home user producing a secure wireless configuration, >> a 64 random character passphrase works wonders. The sky is not about to >> fall in. > Agreed. If 64 character password is reasonably random, bruteforcing it is > economically unfeasible. With obvious exceptions, of course. > Entering such password to a device is somewhat tedious though. Especially tedious on devices with limited input interfaces, such as smart TVs, game consoles, and printers. Restricting the WPA2 passphrase to digits and lowercase letters reduces entropy but makes input more bearable. Seeing the reaction of guests when they are handed a piece of paper with a long random WPA2 passphrase: priceless. It never gets old. :-D Kind regards, -- Ben Caradoc-Davies <ben@transient.nz> Director Transient Software Limited <https://transient.nz/> New Zealand
[toc] | [prev] | [next] | [standalone]
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2019-08-01 04:40 +0200 |
| Message-ID | <yq9ax-19D-1@gated-at.bofh.it> |
| In reply to | #212026 |
On Thu, 1 Aug 2019 11:23:40 +1200 Ben Caradoc-Davies <ben@transient.nz> wrote: > On 01/08/2019 01:44, Reco wrote: > > On Wed, Jul 31, 2019 at 02:32:25PM +0100, Brian wrote: > >> On Wed 31 Jul 2019 at 16:07:33 +0300, Reco wrote: > >>> On Wed, Jul 31, 2019 at 07:58:54AM -0400, Celejar wrote: > >>>> mathematical analysis of how much hardware would be necessary to crack > >>>> a good WPA2 password. I've seen lots of sites explaining how to use > >>>> hashcat with a GPU, and various real-world tests on lists of hashed > >>>> passwords (e.g., [1]), but can you provide a serious analysis of the > >>>> practical cost, in time or hardware, of cracking a real-world WPA setup? > >>> Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > >>> Tesla videocard. > >>> Said hour is more than enough to bruteforce 8 character WPA passphrase > >>> with hashcat. > >> In the context of a home user producing a secure wireless configuration, > >> a 64 random character passphrase works wonders. The sky is not about to > >> fall in. > > Agreed. If 64 character password is reasonably random, bruteforcing it is > > economically unfeasible. With obvious exceptions, of course. > > Entering such password to a device is somewhat tedious though. > > Especially tedious on devices with limited input interfaces, such as > smart TVs, game consoles, and printers. Restricting the WPA2 passphrase True that. I'm embarrassed to admit how much gnashing of teeth I engaged in while trying to enter a WPA passphrase via my printer's keypad / LCD interface, until I realized the right way to do it: hook it up via ethernet, log into the web interface, copy and paste the passphrase, enable the wireless interface, unhook the ethernet cable. > to digits and lowercase letters reduces entropy but makes input more > bearable. Seeing the reaction of guests when they are handed a piece of > paper with a long random WPA2 passphrase: priceless. It never gets old. :-D Indeed ;) Now I just maintain a separate guest network, firewalled off from the main network. Celejar
[toc] | [prev] | [next] | [standalone]
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2019-08-01 04:40 +0200 |
| Message-ID | <yq9az-19D-27@gated-at.bofh.it> |
| In reply to | #211975 |
On Wed, 31 Jul 2019 16:44:23 +0300 Reco <recoverym4n@enotuniq.net> wrote: > On Wed, Jul 31, 2019 at 02:32:25PM +0100, Brian wrote: > > On Wed 31 Jul 2019 at 16:07:33 +0300, Reco wrote: > > > > > On Wed, Jul 31, 2019 at 07:58:54AM -0400, Celejar wrote: > > > > mathematical analysis of how much hardware would be necessary to crack > > > > a good WPA2 password. I've seen lots of sites explaining how to use > > > > hashcat with a GPU, and various real-world tests on lists of hashed > > > > passwords (e.g., [1]), but can you provide a serious analysis of the > > > > practical cost, in time or hardware, of cracking a real-world WPA setup? > > > > > > Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > > > Tesla videocard. > > > Said hour is more than enough to bruteforce 8 character WPA passphrase > > > with hashcat. > > > > In the context of a home user producing a secure wireless configuration, > > a 64 random character passphrase works wonders. The sky is not about to > > fall in. > > Agreed. If 64 character password is reasonably random, bruteforcing it is > economically unfeasible. With obvious exceptions, of course. Explain, please? What exceptions? Celejar
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-08-01 08:20 +0200 |
| Message-ID | <yqcBr-3qz-3@gated-at.bofh.it> |
| In reply to | #212029 |
On Wed, Jul 31, 2019 at 10:35:03PM -0400, Celejar wrote: > On Wed, 31 Jul 2019 16:44:23 +0300 > Reco <recoverym4n@enotuniq.net> wrote: > > > On Wed, Jul 31, 2019 at 02:32:25PM +0100, Brian wrote: > > > On Wed 31 Jul 2019 at 16:07:33 +0300, Reco wrote: > > > > > > > On Wed, Jul 31, 2019 at 07:58:54AM -0400, Celejar wrote: > > > > > mathematical analysis of how much hardware would be necessary to crack > > > > > a good WPA2 password. I've seen lots of sites explaining how to use > > > > > hashcat with a GPU, and various real-world tests on lists of hashed > > > > > passwords (e.g., [1]), but can you provide a serious analysis of the > > > > > practical cost, in time or hardware, of cracking a real-world WPA setup? > > > > > > > > Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > > > > Tesla videocard. > > > > Said hour is more than enough to bruteforce 8 character WPA passphrase > > > > with hashcat. > > > > > > In the context of a home user producing a secure wireless configuration, > > > a 64 random character passphrase works wonders. The sky is not about to > > > fall in. > > > > Agreed. If 64 character password is reasonably random, bruteforcing it is > > economically unfeasible. With obvious exceptions, of course. > > Explain, please? What exceptions? Oh, you know. That three-letter government agencies, Russian and Chineese state-sponsored hackers, all that scary stories of 21st century. Also, never underestimate the computing power of well-built botnet. If you have an access to hundreds of thousands videocards - many things are possible. Reco
[toc] | [prev] | [next] | [standalone]
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2019-08-01 04:40 +0200 |
| Message-ID | <yq9az-19D-25@gated-at.bofh.it> |
| In reply to | #211972 |
On Wed, 31 Jul 2019 16:07:33 +0300 Reco <recoverym4n@enotuniq.net> wrote: > Hi. > > On Wed, Jul 31, 2019 at 07:58:54AM -0400, Celejar wrote: > > On Wed, 31 Jul 2019 10:43:48 +0300 > > Reco <recoverym4n@enotuniq.net> wrote: > > > > > Hi. > > > > > > On Tue, Jul 30, 2019 at 07:06:08PM -0400, Celejar wrote: > > > > On Mon, 29 Jul 2019 13:57:25 +0300 > > > > Reco <recoverym4n@enotuniq.net> wrote: ... > > > > > You have authentication frames that can be intercepted (so WPA > > > > > passphrase can be bruteforced). > > > > > > > > Lots of things (such as TLS, ssh) can theoretically be brute forced - > > > > the question is whether such brute forcing is sufficiently practical to > > > > be a threat. I have seen nothing to indicate that properly configured > > > > WPA2 can be realistically brute forced. > > > > > > For WPA2 it's not that hard really, assuming pre-shared key usage. > > > Can be expensive (all those videocards and ASICs have their cost), but > > > definitely doable. > > > > I'd be interested in seeing some real-world studies, or simply just a > > mathematical analysis of how much hardware would be necessary to crack > > a good WPA2 password. I've seen lots of sites explaining how to use > > hashcat with a GPU, and various real-world tests on lists of hashed > > passwords (e.g., [1]), but can you provide a serious analysis of the > > practical cost, in time or hardware, of cracking a real-world WPA setup? > > Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > Tesla videocard. > Said hour is more than enough to bruteforce 8 character WPA passphrase > with hashcat. Yes, and who said anything about using 8 character passphrase? How about the cost of cracking a 16 character passphrase? Or a 60 character one? > > > You have several encryption algorithms, but: > > > > > b) You may have a hardware that lack support for a good ones. > > > > > > > > I suppose, but my impression is that most hardware from the last few > > > > years is fine. > > > > > > Cheap smartphones and tablets. Whatever they put instead of a proper > > > > This misses the point - we're comparing ethernet to wifi. Cheap > > smartphones and tablets aren't usually going to support ethernet. > > You seem to misunderstand me. > > You have a network that's supposed to be secure. > You have that small herd of assorted client devices, some of them are > better, some are worse. > Excommunicating "bad devices" from the network is usually out of > question if said devices are owned by family members or trusted friends > or, say, business associates. I understand all that, but then your recommendation of "use ethernet" doesn't solve the problem: how is that "herd of assorted client devices", which - by your assumption - includes "cheap smartphones and tablets" that may be owned by family members, trusted friends, or business associates, going to connect via ethernet? > Due to the way APs work you cannot announce one set of encryption > algorithms to one client, and different one to another, hence you bring > down announced algorithms to the lowest common denominator. > > You can announce several, but it's bad for obvious reasons. > You *could* get away with it with mutliple virtual APs, but that adds > complexity. Well, that is what I do (guest network, network for devices that don't support 802.11ac), and it does add some complexity, but I wouldn't call it "fiendishly difficult" - I don't have your network chops, and I probably wouldn't be able to handle it if it were really that difficult ;) Celejar
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-08-01 08:40 +0200 |
| Message-ID | <yqcUN-3xs-9@gated-at.bofh.it> |
| In reply to | #212028 |
On Wed, Jul 31, 2019 at 10:30:05PM -0400, Celejar wrote: > > > > > > You have authentication frames that can be intercepted (so WPA > > > > > > passphrase can be bruteforced). > > > > > > > > > > Lots of things (such as TLS, ssh) can theoretically be brute forced - > > > > > the question is whether such brute forcing is sufficiently practical to > > > > > be a threat. I have seen nothing to indicate that properly configured > > > > > WPA2 can be realistically brute forced. > > > > > > > > For WPA2 it's not that hard really, assuming pre-shared key usage. > > > > Can be expensive (all those videocards and ASICs have their cost), but > > > > definitely doable. > > > > > > I'd be interested in seeing some real-world studies, or simply just a > > > mathematical analysis of how much hardware would be necessary to crack > > > a good WPA2 password. I've seen lots of sites explaining how to use > > > hashcat with a GPU, and various real-world tests on lists of hashed > > > passwords (e.g., [1]), but can you provide a serious analysis of the > > > practical cost, in time or hardware, of cracking a real-world WPA setup? > > > > Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > > Tesla videocard. > > Said hour is more than enough to bruteforce 8 character WPA passphrase > > with hashcat. > > Yes, and who said anything about using 8 character passphrase? How > about the cost of cracking a 16 character passphrase? Or a 60 character > one? Each extra character in WPA passphrase adds roughly two orders of magnitude to the bruteforce time. So you cheat. Dictionary attacks, Markov chain attacks, assumptions on the characters used in passwords - all that really lowers bruteforce time. > > > > You have several encryption algorithms, but: > > > > > > b) You may have a hardware that lack support for a good ones. > > > > > > > > > > I suppose, but my impression is that most hardware from the last few > > > > > years is fine. > > > > > > > > Cheap smartphones and tablets. Whatever they put instead of a proper > > > > > > This misses the point - we're comparing ethernet to wifi. Cheap > > > smartphones and tablets aren't usually going to support ethernet. > > > > You seem to misunderstand me. > > > > You have a network that's supposed to be secure. > > You have that small herd of assorted client devices, some of them are > > better, some are worse. > > Excommunicating "bad devices" from the network is usually out of > > question if said devices are owned by family members or trusted friends > > or, say, business associates. > > I understand all that, but then your recommendation of "use ethernet" > doesn't solve the problem: how is that "herd of assorted client > devices", which - by your assumption - includes "cheap smartphones and > tablets" that may be owned by family members, trusted friends, or > business associates, going to connect via ethernet? Obviously they don't. Does it make WiFi secure somehow? > > Due to the way APs work you cannot announce one set of encryption > > algorithms to one client, and different one to another, hence you bring > > down announced algorithms to the lowest common denominator. > > > > You can announce several, but it's bad for obvious reasons. > > You *could* get away with it with mutliple virtual APs, but that adds > > complexity. > > Well, that is what I do (guest network, network for devices that don't > support 802.11ac), and it does add some complexity, but I wouldn't > call it "fiendishly difficult" - I don't have your network chops, and > I probably wouldn't be able to handle it if it were really that > difficult ;) Ditto. I can handle it, so do you. Don't expect most list members to replicate that approach. Reco
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2019-08-01 08:50 +0200 |
| Message-ID | <yqd4u-3B7-3@gated-at.bofh.it> |
| In reply to | #212034 |
[Multipart message — attachments visible in raw view] — view raw
On Jo, 01 aug 19, 09:32:32, Reco wrote: > On Wed, Jul 31, 2019 at 10:30:05PM -0400, Celejar wrote: > > > > Well, that is what I do (guest network, network for devices that don't > > support 802.11ac), and it does add some complexity, but I wouldn't > > call it "fiendishly difficult" - I don't have your network chops, and > > I probably wouldn't be able to handle it if it were really that > > difficult ;) > > Ditto. > I can handle it, so do you. Don't expect most list members to replicate > that approach. I would expect most list members to be able to replicate that approach. Whether they actually (want to) do it is a different story ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Date | 2019-08-01 10:00 +0200 |
| Message-ID | <yqeae-4eU-1@gated-at.bofh.it> |
| In reply to | #212035 |
Hi. On Thu, Aug 01, 2019 at 09:41:30AM +0300, Andrei POPESCU wrote: > On Jo, 01 aug 19, 09:32:32, Reco wrote: > > On Wed, Jul 31, 2019 at 10:30:05PM -0400, Celejar wrote: > > > > > > Well, that is what I do (guest network, network for devices that don't > > > support 802.11ac), and it does add some complexity, but I wouldn't > > > call it "fiendishly difficult" - I don't have your network chops, and > > > I probably wouldn't be able to handle it if it were really that > > > difficult ;) > > > > Ditto. > > I can handle it, so do you. Don't expect most list members to replicate > > that approach. > > I would expect most list members to be able to replicate that approach. > Whether they actually (want to) do it is a different story ;) Consider me a cynical pessimist then. Regarding WiFi, the most common kind of questions here are (rephrased to hint a solution): 1) Why my WiFi kind refuses to work without non-free firmware? 2) Why using Network Manager prevents me from associating with AP? 3) It wrote all kinds of weird stuff into my resolv.conf, how do I change that? 4) What's Predictable Interface Naming, how do I get my wlan0 back? And regarding hostapd configuration - I recall zero for the last two-three years. Either it works for anyone out of the box without any trouble, or, rather, anyone's using consumer-grade WiFi boxen without any "user-serviceable parts inside". Reco
[toc] | [prev] | [next] | [standalone]
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2019-08-02 05:20 +0200 |
| Message-ID | <yqwgO-7xs-1@gated-at.bofh.it> |
| In reply to | #212039 |
On Thu, 1 Aug 2019 10:50:00 +0300 Reco <recoverym4n@enotuniq.net> wrote: > Hi. > > On Thu, Aug 01, 2019 at 09:41:30AM +0300, Andrei POPESCU wrote: > > On Jo, 01 aug 19, 09:32:32, Reco wrote: > > > On Wed, Jul 31, 2019 at 10:30:05PM -0400, Celejar wrote: > > > > > > > > Well, that is what I do (guest network, network for devices that don't > > > > support 802.11ac), and it does add some complexity, but I wouldn't > > > > call it "fiendishly difficult" - I don't have your network chops, and > > > > I probably wouldn't be able to handle it if it were really that > > > > difficult ;) > > > > > > Ditto. > > > I can handle it, so do you. Don't expect most list members to replicate > > > that approach. > > > > I would expect most list members to be able to replicate that approach. > > Whether they actually (want to) do it is a different story ;) > > Consider me a cynical pessimist then. > Regarding WiFi, the most common kind of questions here are (rephrased to > hint a solution): > > 1) Why my WiFi kind refuses to work without non-free firmware? > 2) Why using Network Manager prevents me from associating with AP? > 3) It wrote all kinds of weird stuff into my resolv.conf, how do I > change that? > 4) What's Predictable Interface Naming, how do I get my wlan0 back? ;) > And regarding hostapd configuration - I recall zero for the last > two-three years. Either it works for anyone out of the box without any > trouble, or, rather, anyone's using consumer-grade WiFi boxen without > any "user-serviceable parts inside". Or we're using consumer-grade wifi hardware but running OpenWrt, so we scrupulously follow the oft-repeated advice to ask only strictly Debian-related questions on this list, and take all our AP configuration questions to the OpenWrt forums ;) > Reco Celejar
[toc] | [prev] | [next] | [standalone]
| From | Celejar <celejar@gmail.com> |
|---|---|
| Date | 2019-08-02 05:20 +0200 |
| Message-ID | <yqwgO-7xs-3@gated-at.bofh.it> |
| In reply to | #212034 |
On Thu, 1 Aug 2019 09:32:32 +0300 Reco <recoverym4n@enotuniq.net> wrote: > On Wed, Jul 31, 2019 at 10:30:05PM -0400, Celejar wrote: > > > > > > > You have authentication frames that can be intercepted (so WPA > > > > > > > passphrase can be bruteforced). > > > > > > > > > > > > Lots of things (such as TLS, ssh) can theoretically be brute forced - > > > > > > the question is whether such brute forcing is sufficiently practical to > > > > > > be a threat. I have seen nothing to indicate that properly configured > > > > > > WPA2 can be realistically brute forced. > > > > > > > > > > For WPA2 it's not that hard really, assuming pre-shared key usage. > > > > > Can be expensive (all those videocards and ASICs have their cost), but > > > > > definitely doable. > > > > > > > > I'd be interested in seeing some real-world studies, or simply just a > > > > mathematical analysis of how much hardware would be necessary to crack > > > > a good WPA2 password. I've seen lots of sites explaining how to use > > > > hashcat with a GPU, and various real-world tests on lists of hashed > > > > passwords (e.g., [1]), but can you provide a serious analysis of the > > > > practical cost, in time or hardware, of cracking a real-world WPA setup? > > > > > > Cost - Amazon will take 11c per hour for that VM that comes with NVIDIA > > > Tesla videocard. > > > Said hour is more than enough to bruteforce 8 character WPA passphrase > > > with hashcat. > > > > Yes, and who said anything about using 8 character passphrase? How > > about the cost of cracking a 16 character passphrase? Or a 60 character > > one? > > Each extra character in WPA passphrase adds roughly two orders of > magnitude to the bruteforce time. > So you cheat. Dictionary attacks, Markov chain attacks, assumptions on > the characters used in passwords - all that really lowers bruteforce > time. But none of that will help if the passphrase is properly (randomly) chosen. Celejar
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2019-07-31 22:20 +0200 |
| Message-ID | <yq3eN-5St-3@gated-at.bofh.it> |
| In reply to | #211943 |
[Multipart message — attachments visible in raw view] — view raw
On Mi, 31 iul 19, 04:43:31, Bonno Bloksma wrote: > > >> You have several encryption algorithms, but: > >> a) They are not equally good. > > Of course not - they never are ;) The trick is to pick a good one, and for wifi, that's WPA2 using AES. > > Indeed, if one uses AES instead of PSK then it gets lots safer but now > we ARE getting in to harder to use protocol. Not all WiFi hardware > knows how to use WPA2 AES encryption. PSK = Pre-shared key AES = Advanced Encryption Standard Encryption It's not "AES instead of PSK", but "WPA2-PSK, with AES encryption". > >> b) You may have a hardware that lack support for a good ones. > > I suppose, but my impression is that most hardware from the last few years is fine. > > All devices should know WPA2 and PSK, maybe not AES. WPA2-PSK with AES has been my wireless configuration for several years. The only complaints I've had were about the length of the password ;) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-07-29 17:00 +0200 |
| Message-ID | <ypfi1-81n-3@gated-at.bofh.it> |
| In reply to | #211847 |
On Mon 29 Jul 2019 at 05:40:40 (-0500), Richard Owlett wrote: > Sneakernet for file transfer has become annoying. > Ethernet is undesirable in my environment so I am only interested is > wireless. > I have only a few machines a max of 6' apart. > My usage would typically be peer-to-peer but I want to communicate > between any two machines. > My web connectivity is via a T-Mobile WiFi Hotspot (WiFi turned off). > I run Debian 9.8. > > I've just begun reading - primarily Wikipedia articles and some links > from them. My primary question is "What should I be reading?" in > order to ask appropriate questions. Specificallty "What?" and "Why?" > much more than "Howto?". You should be reading the shelf prices of cheap wifi routers at the local chain store, or look in the papers for garage sales, students selling up, etc. and make an offer on an old router. The last router I bought was $38 inc tax and it has 5GHz. > A concern is security issues. Why? You're going to encrypt everything that passes through it aren't you. And no one is going to steal your bandwidth if it's not connected to a modem. > Bluetooth, being short range, may thus > have an advantage. IP networking is built into linux. You can't get away from it, it's just there. So use it. Configuring bluetooth is just a distraction. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Patrick Bartek <nemommxiv@gmail.com> |
|---|---|
| Date | 2019-07-29 17:20 +0200 |
| Message-ID | <ypfBn-8oe-3@gated-at.bofh.it> |
| In reply to | #211847 |
On Mon, 29 Jul 2019 05:40:40 -0500 Richard Owlett <rowlett@cloud85.net> wrote: > Sneakernet for file transfer has become annoying. > Ethernet is undesirable in my environment so I am only interested is > wireless. > I have only a few machines a max of 6' apart. > My usage would typically be peer-to-peer but I want to communicate > between any two machines. > My web connectivity is via a T-Mobile WiFi Hotspot (WiFi turned off). > I run Debian 9.8. > > I've just begun reading - primarily Wikipedia articles and some links > from them. My primary question is "What should I be reading?" in order > to ask appropriate questions. Specificallty "What?" and "Why?" much more > than "Howto?". > > A concern is security issues. Bluetooth, being short range, may thus > have an advantage. Speed is not an issue for my expected usage. (I was > one of my ISP's last 6 dial-up clients ;) Since your machines are very close together, take a look at USB to USB networking. It's wired, so more secure than any type of wireless. Fast or reasonably so depending on type of USB -- 2? 3? Minimum investment. USB cables are cheap. With Ethernet, besides extra cables, you'd have to buy at least a switch. And as most computers have multiple USB ports, it's easy to set up. B
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2019-07-29 18:00 +0200 |
| Message-ID | <ypge6-bm-7@gated-at.bofh.it> |
| In reply to | #211868 |
On 07/29/2019 10:10 AM, Patrick Bartek wrote: > [snip] > Since your machines are very close together, take a look at USB to USB > networking. Did ;} One of the first things I thought of as I date back days of everyone having multiple RS-232 null modems. Unfortunately the one I ended up with was extremely Windows-centric. My WinXP machine recognized it with no problem. Whatever version of Debian I was running at the time did not. The cardboard backing of the bubblepak it came in was sticking out of my Misc cubbyholes. It's website [https://plugable.com/products/usb-easy-tran/] claims: > Linux kernels 3.0 and later support the cable as a high-speed > virtual network interface, but offer no special file transfer support. I may have been still using Squeeze - skipped Wheezy and don't recall when I moved to Jessie. I'll search my junk boxes for the cable and see if I can make it work now. Thanks for the reminder. > > It's wired, so more secure than any type of wireless. Fast or reasonably > so depending on type of USB -- 2? 3? Minimum investment. USB cables > are cheap. With Ethernet, besides extra cables, you'd have to buy at > least a switch. And as most computers have multiple USB ports, it's > easy to set up. > > B > > >
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2019-07-29 19:00 +0200 |
| Subject | PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} |
| Message-ID | <yphaa-MJ-9@gated-at.bofh.it> |
| In reply to | #211876 |
On 07/29/2019 10:51 AM, Richard Owlett wrote: > On 07/29/2019 10:10 AM, Patrick Bartek wrote: >> [snip] >> Since your machines are very close together, take a look at USB to USB >> networking. > > Did ;} One of the first things I thought of as I date back days of > everyone having multiple RS-232 null modems. > Unfortunately the one I ended up with was extremely Windows-centric. > My WinXP machine recognized it with no problem. Whatever version of > Debian I was running at the time did not. The cardboard backing of the > bubblepak it came in was sticking out of my Misc cubbyholes. > > It's website [https://plugable.com/products/usb-easy-tran/] claims: >> Linux kernels 3.0 and later support the cable as a high-speed >> virtual network interface, but offer no special file transfer support. Found cable. Plugged in to two Debian 9.8 machines with MATE DE. On both machines the Ethernet icon indicated it was attempting to connect. Both correctly reported manufacturer and model. One reported missing firmware. I have an errand to run and will do a web search for firmware when I get back. QUESTION: What log file(s) should I be watching for diagnostic information? > > I may have been still using Squeeze - skipped Wheezy and don't recall > when I moved to Jessie. I'll search my junk boxes for the cable and see > if I can make it work now. > > Thanks for the reminder. >
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-07-29 23:10 +0200 |
| Subject | Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} |
| Message-ID | <ypl46-3xR-17@gated-at.bofh.it> |
| In reply to | #211880 |
On Mon 29 Jul 2019 at 11:56:25 (-0500), Richard Owlett wrote: > On 07/29/2019 10:51 AM, Richard Owlett wrote: > > On 07/29/2019 10:10 AM, Patrick Bartek wrote: > > > [snip] > > > Since your machines are very close together, take a look at USB to USB > > > networking. > > > > Did ;} One of the first things I thought of as I date back days of > > everyone having multiple RS-232 null modems. > > Unfortunately the one I ended up with was extremely Windows-centric. > > My WinXP machine recognized it with no problem. Whatever version > > of Debian I was running at the time did not. The cardboard backing > > of the bubblepak it came in was sticking out of my Misc > > cubbyholes. > > > > It's website [https://plugable.com/products/usb-easy-tran/] claims: > > > Linux kernels 3.0 and later support the cable as a high-speed > > > virtual network interface, but offer no special file transfer support. > > Found cable. > Plugged in to two Debian 9.8 machines with MATE DE. > On both machines the Ethernet icon indicated it was attempting to connect. > Both correctly reported manufacturer and model. > One reported missing firmware. > > QUESTION: > What log file(s) should I be watching for diagnostic information? # dmesg | grep firmware or # dmesg | less if you want a bit more context. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Richard Owlett <rowlett@cloud85.net> |
|---|---|
| Date | 2019-07-30 05:20 +0200 |
| Subject | Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} |
| Message-ID | <ypqQa-7d8-1@gated-at.bofh.it> |
| In reply to | #211893 |
On 07/29/2019 04:08 PM, David Wright wrote: > On Mon 29 Jul 2019 at 11:56:25 (-0500), Richard Owlett wrote: >> On 07/29/2019 10:51 AM, Richard Owlett wrote: >>> On 07/29/2019 10:10 AM, Patrick Bartek wrote: >>>> [snip] >>>> Since your machines are very close together, take a look at USB to USB >>>> networking. >>> >>> Did ;} One of the first things I thought of as I date back days of >>> everyone having multiple RS-232 null modems. >>> Unfortunately the one I ended up with was extremely Windows-centric. >>> My WinXP machine recognized it with no problem. Whatever version >>> of Debian I was running at the time did not. The cardboard backing >>> of the bubblepak it came in was sticking out of my Misc >>> cubbyholes. >>> >>> It's website [https://plugable.com/products/usb-easy-tran/] claims: >>>> Linux kernels 3.0 and later support the cable as a high-speed >>>> virtual network interface, but offer no special file transfer support. >> >> Found cable. >> Plugged in to two Debian 9.8 machines with MATE DE. >> On both machines the Ethernet icon indicated it was attempting to connect. >> Both correctly reported manufacturer and model. >> One reported missing firmware. >> >> QUESTION: >> What log file(s) should I be watching for diagnostic information? > > # dmesg | grep firmware > > or > > # dmesg | less > > if you want a bit more context. > > Cheers, > David. > Thank you. Thought I was going to be able run test this afternoon. Tomorrow is another day :>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2019-08-03 17:50 +0200 |
| Subject | Re: PROGRESS!! - was {Re: Wireless home LAN - WiFi vs Bluetooth?} |
| Message-ID | <yr4sa-3NQ-7@gated-at.bofh.it> |
| In reply to | #211903 |
On Mon 29 Jul 2019 at 22:09:45 (-0500), Richard Owlett wrote: > On 07/29/2019 04:08 PM, David Wright wrote: > > On Mon 29 Jul 2019 at 11:56:25 (-0500), Richard Owlett wrote: > > > On 07/29/2019 10:51 AM, Richard Owlett wrote: > > > > On 07/29/2019 10:10 AM, Patrick Bartek wrote: > > > > > [snip] > > > > > Since your machines are very close together, take a look at USB to USB > > > > > networking. > > > > > > > > Did ;} One of the first things I thought of as I date back days of > > > > everyone having multiple RS-232 null modems. > > > > Unfortunately the one I ended up with was extremely Windows-centric. > > > > My WinXP machine recognized it with no problem. Whatever version > > > > of Debian I was running at the time did not. The cardboard backing > > > > of the bubblepak it came in was sticking out of my Misc > > > > cubbyholes. > > > > > > > > It's website [https://plugable.com/products/usb-easy-tran/] claims: > > > > > Linux kernels 3.0 and later support the cable as a high-speed > > > > > virtual network interface, but offer no special file transfer support. > > > > > > Found cable. > > > Plugged in to two Debian 9.8 machines with MATE DE. > > > On both machines the Ethernet icon indicated it was attempting to connect. > > > Both correctly reported manufacturer and model. > > > One reported missing firmware. > > > > > > QUESTION: > > > What log file(s) should I be watching for diagnostic information? > > > > # dmesg | grep firmware > > > > or > > > > # dmesg | less > > > > if you want a bit more context. > > Thank you. Thought I was going to be able run test this afternoon. > Tomorrow is another day :> So, did you find out what was missing, have you added it, and did you manage host-host transfers and logins as you should have been able to do? Cheers, David.
[toc] | [prev] | [next] | [standalone]
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web