Digest for sci.electronics.repair@googlegroups.com - 3 updates in 2 topics

Mad Roger <rogermadd@yahoo.com>: Jul 21 03:25PM

On Fri, 21 Jul 2017 14:52:17 +0200,
Yrrah wrote:
 
>> On Ubuntu 16.04, is there a way for a non programmer to "trap" this unique
>> browser ID to see what it looks like?
 
> FYI, there is a Ubuntu newsgroup: alt.os.linux.ubuntu
 
Thanks for the admonition that there is a ubuntu-specific ng.
 
It might have been best to originally crosspost to a.o.l & a.o.l.u; but
there's little utility in starting a new thread because there is no
indication that this is an operating-system specific quest.
 
Given that Opera, on all operating systems, generates and transmits a
unique id to someone somehow, where would you hazard a guess as to
specifically how the unique id is generated (so that we may spoof its
parameters perhaps) and where the ID is stored (so that we may look at it
perhaps) & in what form do you think it's transmitted & to whom (so that we
may watch and intercept it perhaps)?
Mad Roger <rogermadd@yahoo.com>: Jul 21 03:25PM

On Fri, 21 Jul 2017 07:47:16 -0400,
Caver1 wrote:
 
> If you did some research Opera's free VPN isn't a VPN at all, it's more
> of a proxy.
 
Where do you think the ID is stored & in what form do you think it's
transmitted & to whom?
 
I did plenty of research (but I am not an expert!), where four things are
of note, two of which everyone knows (so it has no value in this thread),
and two of which are not posted anywhere in the web so you could sort of
say only we know.
 
Everyone knows this:
1. Opera is a fast free unlimited (pseudo)proxy service for web browsing
2. It's based on Chromium (which may mean it uses Chrome-like unique iDs)
 
Only we seem to know this:
3. Opera is one of the rare (psuedo)vpn's that work with most web forums
4. There must be a way to trap & identify the unique install ID assigned
 
If this thread was about the first two items, the thread wouldn't exist.
The thread is about the latter two items, specifically that last item.
 
If that last item were obvious, then it would have been resolved already.
 
The question at hand is how to trap that unique id with the end goal in
mind being to spoof it eventually; but you can't spoof that which you can't
see.
 
There's either a unique static binary ID, or a static config file ID, or
the unique ID is generated on the fly.
 
Where do you think the ID is stored & in what form do you think it's
transmitted and to whom?
"Michael A. Terrell" <mike.terrell@earthlink.net>: Jul 21 11:20AM -0400

D. Peter Maus wrote:
 
> It also doesn't help that you have everything on-hand, for a job, so
> you can get the job done faster, smoother and without stops or delays.
 
> Clients dig that.
 
A lot of my work was when no wholesaler was open, so you carried it,
or stretched a job out over several days. As far as rentals, I did carry
a lot of adapters, since we would have to connect to existing wiring, or
give a feed to a radio station. We also carried tools and spare parts to
make equipment repairs, on site if needed.
 
My customers were school boards, local governments and factories who
rarely saw what I carried. All they saw was that I could get a job done
on time, and at a fair price.
 
Work at schools often meant evening hours, or getting there at six
AM when their intercom was down.
 
Factories was almost always noisy and sometimes dangerous work
around running machinery.
 
Churches were always looking for the cheapest jobs they could find,
so some got no bids because of the cobbled together messes left by
whatever was there before you.
 
Amusement parks were often scheduled for after they closed for the
night. Like installing new dual 12VDC electrical and sound systems in a
pair of paddle boats J.I.T. for an after Prom party.
 
 
--
Never piss off an Engineer!
 
They don't get mad.
 
They don't get even.
 
They go for over unity! ;-)
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to sci.electronics.repair+unsubscribe@googlegroups.com.

No Response to "Digest for sci.electronics.repair@googlegroups.com - 3 updates in 2 topics"

Post a Comment