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

Groups > linux.debian.user > #274535 > unrolled thread

debian-to-windows message transfer

Back to article view | Back to linux.debian.user

Contents

  debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-16 05:40 +0100
    Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-16 05:50 +0100
      Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-16 06:50 +0100
        Re: debian-to-windows message transfer Chris Green <cl@isbd.net> - 2024-11-16 10:50 +0100
          Re: debian-to-windows message transfer Joe <joe@jretrading.com> - 2024-11-16 11:50 +0100
      Re: debian-to-windows message transfer Christian Britz <cbritz@t-online.de> - 2024-11-16 17:40 +0100
        Re: debian-to-windows message transfer Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-11-18 23:10 +0100
          Re: debian-to-windows message transfer Jeffrey Walton <noloader@gmail.com> - 2024-11-19 08:50 +0100
    Re: debian-to-windows message transfer Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-11-16 07:40 +0100
      Re: debian-to-windows message transfer Charles Curley <charlescurley@charlescurley.com> - 2024-11-16 17:20 +0100
    Re: debian-to-windows message transfer <tomas@tuxteam.de> - 2024-11-16 11:30 +0100
    Re: debian-to-windows message transfer Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-11-16 11:40 +0100
      Re: debian-to-windows message transfer Henrik Ahlgren <pablo@seestieto.com> - 2024-11-16 18:50 +0100
        Re: debian-to-windows message transfer Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-11-20 08:20 +0100
    Re: debian-to-windows message transfer Andy Smith <andy@strugglers.net> - 2024-11-16 14:20 +0100
      Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-16 19:20 +0100
        Re: debian-to-windows message transfer eben@gmx.us - 2024-11-16 20:20 +0100
    Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-16 19:10 +0100
      Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-16 20:30 +0100
        Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-16 20:50 +0100
          Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-16 22:40 +0100
        Re: debian-to-windows message transfer debian-user@howorth.org.uk - 2024-11-17 10:40 +0100
          Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-17 15:40 +0100
            Re: debian-to-windows message transfer Andy Smith <andy@strugglers.net> - 2024-11-17 15:50 +0100
              Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-17 18:50 +0100
                Re: debian-to-windows message transfer <tomas@tuxteam.de> - 2024-11-17 19:00 +0100
                Re: debian-to-windows message transfer Charles Curley <charlescurley@charlescurley.com> - 2024-11-17 22:10 +0100
                  Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-18 02:20 +0100
                    Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-18 02:40 +0100
                      Re: debian-to-windows message transfer Max Nikulin <manikulin@gmail.com> - 2024-11-18 03:20 +0100
                        Re: debian-to-windows message transfer Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-11-18 03:30 +0100
                          Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-18 04:00 +0100
                        Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-18 03:50 +0100
                          Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-18 04:10 +0100
                          Re: debian-to-windows message transfer Max Nikulin <manikulin@gmail.com> - 2024-11-18 04:40 +0100
                            Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-18 05:30 +0100
                              Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-18 13:10 +0100
                              Re: debian-to-windows message transfer Max Nikulin <manikulin@gmail.com> - 2024-11-18 17:50 +0100
                      Re: debian-to-windows message transfer "Russell L. Harris" <russell@rlharris.org> - 2024-11-18 03:30 +0100
                        Re: debian-to-windows message transfer Greg Wooledge <greg@wooledge.org> - 2024-11-18 03:40 +0100
            Re: debian-to-windows message transfer Joe <joe@jretrading.com> - 2024-11-17 16:30 +0100
              Re: debian-to-windows message transfer Andy Smith <andy@strugglers.net> - 2024-11-17 16:50 +0100
            Re: debian-to-windows message transfer debian-user@howorth.org.uk - 2024-11-17 17:40 +0100
      Re: debian-to-windows message transfer "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-11-16 22:00 +0100
        Re: debian-to-windows message transfer debian-user@howorth.org.uk - 2024-11-17 10:40 +0100
          Re: debian-to-windows message transfer Roger Price <debian@rogerprice.org> - 2024-11-17 11:40 +0100
            Re: debian-to-windows message transfer Joe <joe@jretrading.com> - 2024-11-17 16:30 +0100
              Re: debian-to-windows message transfer John Hasler <john@sugarbit.com> - 2024-11-17 17:00 +0100
                Re: debian-to-windows message transfer Joe <joe@jretrading.com> - 2024-11-17 18:20 +0100
                  Re: debian-to-windows message transfer "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-11-17 20:40 +0100

Page 1 of 3  [1] 2 3  Next page →

#274535 — debian-to-windows message transfer

Debian machines are on the 192.168.1.xxx network.  I keep a W10
machine on the 192.168.2.x network, primarily to access the chewy.com
web site which, since about June, serves my Debian machines a blank
white page.  Only one of the Debian machines is set up for mail.

Now and then a mail message comes in to which I need to respond, but
the response link typically is a URL consisting of dozens of
characters, and it is the URL of a chewy.com web site or another web
site which is hostile to Debian.

Is there an easy way to send the message (or just the URL) to the
Window$ machine?

Example URL:

https://clicks-paws.chewy.com/f/a/uBusczxQ2YB4qWyebLm8UA~~/AAQRxQA~/
RgRpFi0ZP4TxAWh0dHBzOi8vbWVvdy5jaGV3eS5jb20vcC9jcC83NzIxMTI0YjA0NjYzYz
NjL2M_bGlkPXVyY2kzNGEzMzdnbiZtaV9lY21wPTIwMjQtMTEtMTItVHUtQ2hld3lDbGF1
cy1WMiZtaV9pZ249ZDViZmMyMTYtMjEwZi00NTJkLWIyODAtYzVmYWY1OTJkNWVjJnBldF
R5cGU9RG9nJnBldF9uYW1lX3N0cmluZz1FbHNhJnVybD1odHRwcyUzQSUyRiUyRm1lb3cu
Y2hld3kuY29tJTJGcCUyRnJwJTJGMWIwZGI5NmU5NWQwYjQ5YSUyRnVybCZ1cmxfc2lnPV
lWdkI3T256eXJrZTMyJnV0bV9tZWRpdW09ZW1haWwmdXRtX3NvdXJjZT1wcm9tb3Rpb25h
bCZ1dG1fY2FtcGFpZ249ZDViZmMyMTYtMjEwZi00NTJkLWIyODAtYzVmYWY1OTJkNWVjJn
V0bV9hdWRpZW5jZT0yMDI0LTExLTEyLVR1LUNoZXd5Q2xhdXMtVjImbWlfdT0xNDE4ODgy
MDQmbWlfZWNtcD0yMDI0LTExLTEyLVR1LUNoZXd5Q2xhdXMtVjImdXRtX2NvbnRlbnQ9Yz
YwNjA1OGItMWU3My00NWYzLWJiZTItZDVmYjI2MzU5YmU1VwNzcGNCCmcrGagzZ-AYFUdS
FHJ1c3NlbGxAcmxoYXJyaXMub3JnWAQ

[toc] | [next] | [standalone]

#274536

On Sat, Nov 16, 2024 at 04:28:59 +0000, Russell L. Harris wrote:
> Debian machines are on the 192.168.1.xxx network.  I keep a W10
> machine on the 192.168.2.x network, primarily to access the chewy.com
> web site which, since about June, serves my Debian machines a blank
> white page.

chewy.com loads for me in Firefox, after I permit Javascript on that
domain.

> Is there an easy way to send the message (or just the URL) to the
> Window$ machine?

The first thing that comes to mind is using a SOCKS proxy over ssh.
It's been a while since I've done that, but it involves running
"ssh -D ..." on the client (Debian) system, logging into another
system (could be a VPS or something) which can reach the web server
without problems.  Then you'd point the web browser at the proxy.

If your Windows machine can run an ssh daemon that you can log into,
then you could use it as your SOCKS proxy, though I have no idea how
you'd go about setting up an sshd on Windows.

Most importantly, though, I'd try to figure out why your browser on
Debian is having problems.  If you create a brand new user account,
and run the browser with no add-ons, does it also have problems with
this web site?  Maybe it's something in your main account's configuration.

[toc] | [prev] | [next] | [standalone]

#274537

On Fri, Nov 15, 2024 at 11:42:24PM -0500, Greg Wooledge wrote:
>Most importantly, though, I'd try to figure out why your browser on
>Debian is having problems.  If you create a brand new user account,
>and run the browser with no add-ons, does it also have problems with
>this web site?  Maybe it's something in your main account's configuration.

Hi, Greg.  I think it has to do with DRM; a couple of times I have
seen a message to that effect flash on the screen briefly and
disappear.

One day I could access the web site on any of my Debian systems; the
next day I got only a blank white screen on all of them.  CHEWY must
have changed something on the web server.  I have complained to CHEWY
to no avail.

One of the CHEWY customer service people told me that her husband runs
Linux, and she spent about a half hour on the phone having me change
this and that; but the problem remained.  I tried Firefox, Chromium,
and Brave.

I solved the problem by ordering a refurbished Window$ box for about a
hundred dollars (free shipping).  Life is too short to mess around
with things which can be avoided.

RLH

[toc] | [prev] | [next] | [standalone]

#274540

Russell L. Harris <russell@rlharris.org> wrote:
> On Fri, Nov 15, 2024 at 11:42:24PM -0500, Greg Wooledge wrote:
> >Most importantly, though, I'd try to figure out why your browser on
> >Debian is having problems.  If you create a brand new user account,
> >and run the browser with no add-ons, does it also have problems with
> >this web site?  Maybe it's something in your main account's configuration.
> 
> Hi, Greg.  I think it has to do with DRM; a couple of times I have
> seen a message to that effect flash on the screen briefly and
> disappear.
> 
> One day I could access the web site on any of my Debian systems; the
> next day I got only a blank white screen on all of them.  CHEWY must
> have changed something on the web server.  I have complained to CHEWY
> to no avail.
> 
> One of the CHEWY customer service people told me that her husband runs
> Linux, and she spent about a half hour on the phone having me change
> this and that; but the problem remained.  I tried Firefox, Chromium,
> and Brave.
> 
> I solved the problem by ordering a refurbished Window$ box for about a
> hundred dollars (free shipping).  Life is too short to mess around
> with things which can be avoided.
> 
Would running remmina (or something similar) on you Linux systems
allow you to access the Windows box?  I do this so I can run some
Epson scanner software on a windows 10 systme with control from my
Debian (xfce in my case) desktop.  All you need to do at the Windows
end is allow access using RDP and it all 'just works'.

-- 
Chris Green
·

[toc] | [prev] | [next] | [standalone]

#274543

On Sat, 16 Nov 2024 09:21:26 +0000
Chris Green <cl@isbd.net> wrote:

> Russell L. Harris <russell@rlharris.org> wrote:
> > On Fri, Nov 15, 2024 at 11:42:24PM -0500, Greg Wooledge wrote:  
> > >Most importantly, though, I'd try to figure out why your browser on
> > >Debian is having problems.  If you create a brand new user account,
> > >and run the browser with no add-ons, does it also have problems
> > >with this web site?  Maybe it's something in your main account's
> > >configuration.  
> > 
> > Hi, Greg.  I think it has to do with DRM; a couple of times I have
> > seen a message to that effect flash on the screen briefly and
> > disappear.
> > 
> > One day I could access the web site on any of my Debian systems; the
> > next day I got only a blank white screen on all of them.  CHEWY must
> > have changed something on the web server.  I have complained to
> > CHEWY to no avail.
> > 
> > One of the CHEWY customer service people told me that her husband
> > runs Linux, and she spent about a half hour on the phone having me
> > change this and that; but the problem remained.  I tried Firefox,
> > Chromium, and Brave.
> > 
> > I solved the problem by ordering a refurbished Window$ box for
> > about a hundred dollars (free shipping).  Life is too short to mess
> > around with things which can be avoided.
> >   
> Would running remmina (or something similar) on you Linux systems
> allow you to access the Windows box?  I do this so I can run some
> Epson scanner software on a windows 10 systme with control from my
> Debian (xfce in my case) desktop.  All you need to do at the Windows
> end is allow access using RDP and it all 'just works'.
> 

Only in professional or business versions of Windows, not in the home
version. It is possible a refurbished box has the pro version. There
are also third-party remote desktops for Windows.

SSH can certainly be used the other way around, from Windows to Linux.
Simon Tatham's PuTTY has been available on Windows for many years, and
is an SSH client among other things. There is now an sshd on Windows,
but I haven't tried it. There are various ways of getting a Linux
environment on Windows, such as WSL and Cygwin, but these are probably
overkill for this kind of job.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#274561

Am 16.11.24 um 05:42 schrieb Greg Wooledge:

> If your Windows machine can run an ssh daemon that you can log into,
> then you could use it as your SOCKS proxy, though I have no idea how
> you'd go about setting up an sshd on Windows.

Should not be to hard using Windows' built-in WSL (you can even run most
parts of Debian on it) or the free Cygwin environment.

[toc] | [prev] | [next] | [standalone]

#274651

Christian Britz <cbritz@t-online.de> writes:

> Am 16.11.24 um 05:42 schrieb Greg Wooledge:
>
>> If your Windows machine can run an ssh daemon that you can log into,
>> then you could use it as your SOCKS proxy, though I have no idea how
>> you'd go about setting up an sshd on Windows.
>
> Should not be to hard using Windows' built-in WSL (you can even run most
> parts of Debian on it) or the free Cygwin environment.

None of that is needed, Microsoft bundles openssh client and server in
Windows 10 and 11. Probably exempting any limited editions but present
in Windows 10 & 11 Pro. Enabling those is done via "Optional
features" in settings.

[toc] | [prev] | [next] | [standalone]

#274655

On Mon, Nov 18, 2024 at 5:08 PM Anssi Saari
<anssi.saari@debian-user.mail.kapsi.fi> wrote:
> Christian Britz <cbritz@t-online.de> writes:
> > Am 16.11.24 um 05:42 schrieb Greg Wooledge:
> >
> >> If your Windows machine can run an ssh daemon that you can log into,
> >> then you could use it as your SOCKS proxy, though I have no idea how
> >> you'd go about setting up an sshd on Windows.
> >
> > Should not be to hard using Windows' built-in WSL (you can even run most
> > parts of Debian on it) or the free Cygwin environment.
>
> None of that is needed, Microsoft bundles openssh client and server in
> Windows 10 and 11. Probably exempting any limited editions but present
> in Windows 10 & 11 Pro. Enabling those is done via "Optional
> features" in settings.

I have to use WIndoze 10 at $dayjob. I find WIndows Subsystem for
Linux (WSL) a nice addition. It provides Linux in something that feels
like a container, but it is in the Terminal app. The classic Linux
text tools are available, and tools like ssh, scp and sftp are
available.

Jeff

[toc] | [prev] | [next] | [standalone]

#274539

[Multipart message — attachments visible in raw view] — view raw

On Fri, Nov 15, 2024 at 11:31 PM Russell L. Harris <russell@rlharris.org>
wrote:

> Debian machines are on the 192.168.1.xxx network.  I keep a W10
> machine on the 192.168.2.x network, primarily to access the chewy.com
> web site which, since about June, serves my Debian machines a blank
> white page.


I get to the Chewy website with no issues using: Trixie, KDE and Google
Chrome browser. If you are getting a plain white screen on Firefox then it
is likely a firefox issue and not a debian issue. Try installing Google
Chrome.



>   Only one of the Debian machines is set up for mail.
>
> Now and then a mail message comes in to which I need to respond, but
> the response link typically is a URL consisting of dozens of
> characters, and it is the URL of a chewy.com web site or another web
> site which is hostile to Debian.
>
> Is there an easy way to send the message (or just the URL) to the
> Window$ machine?
>
> Example URL:
>
> https://clicks-paws.chewy.com/f/a/uBusczxQ2YB4qWyebLm8UA~~/AAQRxQA~/
> RgRpFi0ZP4TxAWh0dHBzOi8vbWVvdy5jaGV3eS5jb20vcC9jcC83NzIxMTI0YjA0NjYzYz
> <https://clicks-paws.chewy.com/f/a/uBusczxQ2YB4qWyebLm8UA~~/AAQRxQA~/RgRpFi0ZP4TxAWh0dHBzOi8vbWVvdy5jaGV3eS5jb20vcC9jcC83NzIxMTI0YjA0NjYzYz>
> NjL2M_bGlkPXVyY2kzNGEzMzdnbiZtaV9lY21wPTIwMjQtMTEtMTItVHUtQ2hld3lDbGF1
> cy1WMiZtaV9pZ249ZDViZmMyMTYtMjEwZi00NTJkLWIyODAtYzVmYWY1OTJkNWVjJnBldF
> R5cGU9RG9nJnBldF9uYW1lX3N0cmluZz1FbHNhJnVybD1odHRwcyUzQSUyRiUyRm1lb3cu
> Y2hld3kuY29tJTJGcCUyRnJwJTJGMWIwZGI5NmU5NWQwYjQ5YSUyRnVybCZ1cmxfc2lnPV
> lWdkI3T256eXJrZTMyJnV0bV9tZWRpdW09ZW1haWwmdXRtX3NvdXJjZT1wcm9tb3Rpb25h
> bCZ1dG1fY2FtcGFpZ249ZDViZmMyMTYtMjEwZi00NTJkLWIyODAtYzVmYWY1OTJkNWVjJn
> V0bV9hdWRpZW5jZT0yMDI0LTExLTEyLVR1LUNoZXd5Q2xhdXMtVjImbWlfdT0xNDE4ODgy
> MDQmbWlfZWNtcD0yMDI0LTExLTEyLVR1LUNoZXd5Q2xhdXMtVjImdXRtX2NvbnRlbnQ9Yz
> YwNjA1OGItMWU3My00NWYzLWJiZTItZDVmYjI2MzU5YmU1VwNzcGNCCmcrGagzZ-AYFUdS
> FHJ1c3NlbGxAcmxoYXJyaXMub3JnWAQ
>
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

[toc] | [prev] | [next] | [standalone]

#274560

On Sat, 16 Nov 2024 01:33:21 -0500
Timothy M Butterworth <timothy.m.butterworth@gmail.com> wrote:

> I get to the Chewy website with no issues using: Trixie, KDE and
> Google Chrome browser. If you are getting a plain white screen on
> Firefox then it is likely a firefox issue and not a debian issue. Try
> installing Google Chrome.

I visited chewy.com with vivaldi, a chromium based browser. No problems
on a brief look.

The OP, "Russell L. Harris" <russell@rlharris.org>, did not say which
browser(s) he tried. I suggest he locate the browser's user profile
directory, move it aside (i.e. rename it), and try the web site with a
brand spanking new user profile.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#274541

[Multipart message — attachments visible in raw view] — view raw

On Sat, Nov 16, 2024 at 04:28:59AM +0000, Russell L. Harris wrote:
> Debian machines are on the 192.168.1.xxx network.  I keep a W10
> machine on the 192.168.2.x network, primarily to access the chewy.com
> web site which, since about June, serves my Debian machines a blank
> white page.  Only one of the Debian machines is set up for mail.
> 
> Now and then a mail message comes in to which I need to respond, but
> the response link typically is a URL consisting of dozens of
> characters, and it is the URL of a chewy.com web site or another web
> site which is hostile to Debian.
> 
> Is there an easy way to send the message (or just the URL) to the
> Window$ machine?

My Linux machine always has an open SSH port. The windows command
line box (aka console) is preposterous (what is not, in Windows?),
but better than in older versions. And they have an SSH client.

So what I do is ssh into my Linux box. Sometimes, I even run an
Emacs client in that.

This covers my needs, including copy-pasta (what else is that other
operating system good for, anyway?) of things in Windows.

> Example URL:
> 
> https://clicks-paws.chewy.com/f/a/uBusczxQ2YB4qWyebLm8UA~~/AAQRxQA~/
> RgRpFi0ZP4TxAWh0dHBzOi8vbWVvdy5jaGV3eS5jb20vcC9jcC83NzIxMTI0YjA0NjYzYz
  [...]

Jeez. They could send the whole web page content over that URL. I'd
cancel that service =:-o

Cheers
-- 
t

[toc] | [prev] | [next] | [standalone]

#274542

"Russell L. Harris" <russell@rlharris.org> writes:

> Debian machines are on the 192.168.1.xxx network.  I keep a W10
> machine on the 192.168.2.x network, primarily to access the chewy.com
> web site which, since about June, serves my Debian machines a blank
> white page.  Only one of the Debian machines is set up for mail.

I actually did have that sort of issue some years ago, I think it was
https://www.securew2.com/ and specifically Firefox. Works fine today on
Debian 11, Firefox 115.14.0esr. Chewy.com too.

> Now and then a mail message comes in to which I need to respond, but
> the response link typically is a URL consisting of dozens of
> characters, and it is the URL of a chewy.com web site or another web
> site which is hostile to Debian.
>
> Is there an easy way to send the message (or just the URL) to the
> Window$ machine?

Use a pastebin? Setup mail in Windows? Connect to the Windows machine
via remote desktop and remotely use the browser there? There are so many
ways to skin that cat.

I have an occasional need to move small files between Windows and Linux,
I've settled on sshfs from Windows to Linux these days. sshd on Linux is
a given here anyways and the sshfs implementation for Windows has worked
well for me. I've tried the NFS client support in Windows too but it
seemed to have tedious long delays when connecting so not much fun.

I remember I've looked into clipboards that work over the network but I
don't think I found one that'd work between Windows and Linux and would
be simple and easy to use.

[toc] | [prev] | [next] | [standalone]

#274565

On Sat, 2024-11-16 at 12:30 +0200, Anssi Saari wrote:
> > Is there an easy way to send the message (or just the URL) to the
> > Window$ machine?
> 
> Use a pastebin? Setup mail in Windows? Connect to the Windows machine
> via remote desktop and remotely use the browser there? There are so many
> ways to skin that cat.

Perhaps try Magic-Wormhole:

https://magic-wormhole.readthedocs.io/en/latest/

apt install magic-wormhole

[toc] | [prev] | [next] | [standalone]

#274686

Henrik Ahlgren <pablo@seestieto.com> writes:

> Perhaps try Magic-Wormhole:
>
> https://magic-wormhole.readthedocs.io/en/latest/
>
> apt install magic-wormhole

Very interesting, thank you. Maybe not that great for LAN use but I
might have have a use for it.

[toc] | [prev] | [next] | [standalone]

#274548

[Multipart message — attachments visible in raw view] — view raw

Hi,

On Sat, Nov 16, 2024 at 04:28:59AM +0000, Russell L. Harris wrote:
> I keep a W10 machine on the 192.168.2.x network, primarily to access
> the chewy.com web site which, since about June, serves my Debian
> machines a blank white page.

With javascript disabled for chewy,com I get a blank white page with
Debian 12 and Firefox. Allowing javascript seems to result in a fully
functional site.

All of my personal machines run Debian. I seem to spend more than half
of my working hours reading web sites. I don't feel like I have
particular problems in doing so.

It may well be that you have permissions like javascript and cross-site
cookies tightened up so far on Linux that some sites don't work. You
then perhaps go to a Windows machine with no such protections in order
to make that work.

Long term I would suggest that isn't ideal and maybe relaxing some
security features in your Linux browser might be worth it, or running
such a browser in a virtual machine, rather than having to have a whole
separate computer.

Others have made suggestions for getting links from one machine to
another. Pastebins, shortlinkers, even just a social media account that
you an access from both machiens (paste the link in a message to
yourself).

Myself I have also made use of findfox:

    https://github.com/ayosec/findfox

This allows me to send stuff to a running firefox from remote places.
Example:

$ findfox list L2hvbWUvYW5keS8ubW96aWxsYS9maXJlZm94L3ozeWk5dngzLmRlZmF1bHQtcmVsZWFzZQ__        /home/andy/.mozilla/firefox/z3yi9vx3.default-release

Now I know the id of the firefox that runs there (this id will stay the
same for the life of that firefix install).

I can load a URl there:

$ findfox send 'L2hvbWUvYW5keS8ubW96aWxsYS9maXJlZm94L3ozeWk5dngzLmRlZmF1bHQtcmVsZWFzZQ__' https://chewy.com

And I can ssh in to my machine and issue that command and it loads it in
the running Firefox.

I realise you've got Windows in the mix here so perhaps that won't work.

Firefox of course does also have its own ways to sync bookmarks and tabs
between browsers.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#274570

On Sat, Nov 16, 2024 at 01:15:17PM +0000, Andy Smith wrote:
>With javascript disabled for chewy,com I get a blank white page with
>Debian 12 and Firefox. Allowing javascript seems to result in a fully
>functional site.

I know nothing about javascript; how do I "allow" javascript?  Or,
what did I do to disallow javascript?

>It may well be that you have permissions like javascript and cross-site
>cookies tightened up so far on Linux that some sites don't work. You
>then perhaps go to a Windows machine with no such protections in order
>to make that work.

I have installed Debian-12 via netinstal, and Firefox and Chromium
from the Debian repository.  I have not done anything to change
browser configuration, except to add startpage as the default search
engine.  

>Long term I would suggest that isn't ideal and maybe relaxing some
>security features in your Linux browser might be worth it, or running
>such a browser in a virtual machine, rather than having to have a whole
>separate computer.

So long as I can afford the electric bill, running a separate computer
is no problem.  I keep it running 24/7 to monitor news sites.  I don't
mind a little bit of hassle to be able to browse CHEWY.  Their
selection, prices, and delivery are hard to beat.

But something changed at the beginning of summer.  And the change
affected all of my machines, some of which I since have done a
complete reinstall (netinst).

I am way out in the middle of nowhere with poor Internet service; but
the Window$ machine accesses the CHEWY web site properly.

All my machines are behind an ipFire firewall, but even connecting to
the modem upstream of the firewall does not allow me to browse CHEWY.

RLH

[toc] | [prev] | [next] | [standalone]

#274575

On 11/16/24 13:18, Russell L. Harris wrote:
> On Sat, Nov 16, 2024 at 01:15:17PM +0000, Andy Smith wrote:
>> With javascript disabled for chewy,com I get a blank white page with
>> Debian 12 and Firefox. Allowing javascript seems to result in a fully
>> functional site.
>
> I know nothing about javascript; how do I "allow" javascript?  Or,
> what did I do to disallow javascript?

The way I usually do it is with the broser plugin "noscript", though there
probably are other ways.

>> It may well be that you have permissions like javascript and cross-site
>> cookies tightened up so far on Linux that some sites don't work.

Noscript does that too, and I think Firefox does it natively.

--
    While other countries spent 50 years investing in infrastructure,
  health care, social safety nets, etc., America did nothing.  And now
   we're trapped in a cycle of poverty.  -- umair haque (paraphrased)

[toc] | [prev] | [next] | [standalone]

#274569

> Debian machines are on the 192.168.1.xxx network.  I keep a W10
> machine on the 192.168.2.x network, primarily to access the chewy.com
> web site which, since about June, serves my Debian machines a blank
> white page.

I've been thinking about this some more, and I'd like to try to list
all the ways the OP might have caused this to fail.

We start by observing that nobody else has been able to reproduce the
OP's failure.  Several people (including myself) have responded saying
that chewy.com works just fine for them from a Debian web browser.
So, the problem appears to be unique to the OP's setup.

What could cause this?

* Wrong browser.  We don't know which browser the OP is using primarily;
  in a follow-up, they said they've tried Firefox, Chromium, and Brave.
  Other people have reported that it works in Firefox and Chrome.

* Browser configuration.  The OP might have installed an add-on that's
  interfering with this site, or they might have changed a setting.
  A few people have suggested that the OP try a pristine browser profile,
  or a pristine user account with no customizations.

* Firewall.  The OP mentions separate networks.  It's unclear whether
  the configuration of the router/firewall is different between the
  two networks.  A firewall could be blocking traffic to some web
  server(s) that are needed to render this site, or there could be
  a misbehaving proxy, etc.  Moving the Debian host to the other network
  might be a quick way to test this.

* DNS blocking.  Some people edit their /etc/hosts files to prevent
  connections to various hosts, and then they often forget they've
  done this.  The OP might want to check whether their /etc/hosts file
  has been modified.  Or, if the Debian system is running its own
  nameserver, the nameserver's configuration should be checked (or
  temporarily switch the local nameserver to the one used by the
  Windows systems).

Anything else?

[toc] | [prev] | [next] | [standalone]

#274576

On Sat, Nov 16, 2024 at 01:03:34PM -0500, Greg Wooledge wrote:
>I've been thinking about this some more, and I'd like to try to list
>all the ways the OP might have caused this to fail.
>
>We start by observing that nobody else has been able to reproduce the
>OP's failure.

Two or three  months ago, a guy in Australia and a guy in England
reported the same problem (blank white screen).

>So, the problem appears to be unique to the OP's setup.
>
>What could cause this?

>* Wrong browser.  We don't know which browser the OP is using primarily;

Primarily Firefox.  I also routinely use Chromium.

>* Browser configuration.  The OP might have installed an add-on that's
>  interfering with this site, or they might have changed a setting.
>  A few people have suggested that the OP try a pristine browser profile,
>  or a pristine user account with no customizations.

I have approx running on one machine here, so I can reinstall using
netinst fairly quickly.  And I have been given several old machines,
so I several times have done a no-compromise clean install (via
netinst).  Yet, the fresh installation fails to browse CHEWY.

>* Firewall.  The OP mentions separate networks.  It's unclear whether
>  the configuration of the router/firewall is different between the
>  two networks.  A firewall could be blocking traffic to some web
>  server(s) that are needed to render this site, or there could be
>  a misbehaving proxy, etc.  Moving the Debian host to the other network
>  might be a quick way to test this.

I have a machine running iphole.  But that machine is inside the GREEN
network, and the firewall has no special knowledge of it.  Each
machine in the network must be configured individually (through the
network manager) to use iphole.

And I have bypassed everything by connecting directly to the router
(provided by the ISP) to which the firewall is connected.  The problem
remains.
>
>* DNS blocking.  Some people edit their /etc/hosts files to prevent
>  connections to various hosts, and then they often forget they've
>  done this.  The OP might want to check whether their /etc/hosts file
>  has been modified.

Pristine Debian-12 installation.

>  Or, if the Debian system is running its own
>  nameserver, the nameserver's configuration should be checked (or
>  temporarily switch the local nameserver to the one used by the
>  Windows systems).

>Anything else?

Perhaps the quickest solution is to setup a mail client on the Window$
machine -- a time-machine journey back to the year A.D. 2000 when a
genuine Y2K bug (in MS Word 5.0 for DOS) impelled a search which
brought me out of the mire of Windows and to Debian.

RLH

[toc] | [prev] | [next] | [standalone]

#274577

On Sat, Nov 16, 2024 at 19:24:07 +0000, Russell L. Harris wrote:
> On Sat, Nov 16, 2024 at 01:03:34PM -0500, Greg Wooledge wrote:
> > I've been thinking about this some more, and I'd like to try to list
> > all the ways the OP might have caused this to fail.
> > 
> > We start by observing that nobody else has been able to reproduce the
> > OP's failure.
> 
> Two or three  months ago, a guy in Australia and a guy in England
> reported the same problem (blank white screen).

OK, add another item to the list:

* Server-side blocking.  Whether based on the client's IP address or
  user agent or cookies or any other data, the web server might be
  rejecting this client's requests specifically.

If you go to any web site that reports your IP address (for example,
<http://wooledge.org/myip.cgi>), do you get the same address from
the Debian system and from the Windows system?

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web