Am 20.01.2017 um 20:54 schrieb Bryan Quigley:
But what information is it carrying that is private?
none - a UUID is by defintion UNIQUE but random stuff generated once and
that's it
https://en.wikipedia.org/wiki/Universally_unique_identifier
___
How about /etc/default/grub.d/ for the kernel parameter drop in file.
That's how I do it at least.
I don't think it's super well documented tho and I forget the suffix it
expects offhand (*.cfg?). Follow the chain of the update-grub scripts and
you should find it.
Cheers,
Brian
On Fri, Jan 20,
20.01.2017 17:51, Patrick Schleizer пишет:
> Hi,
>
> I've learned about the kernel parameter and symlink ways to disable
> predictable network interface names. However, as a Debian derivative, it
> would be much cleaner using a drop-in to disable it.
>
> Is there some drop-in directory
On Fri, Jan 20, 2017 at 12:20 PM, Raghavendra. H. R
wrote:
> Hi All,
>
> I have a scenario in which I have 2 processes and both acts as Server &
> Client.
> Process A starts it server & tries to connect as client with Process B.
> Process B starts it server & tries to
On Fri, Jan 20, 2017 at 12:55:20PM +0100, Lars Knudsen wrote:
> On Fri, Jan 20, 2017 at 12:05 PM, Greg KH wrote:
> > - so if we can make a rule that consistently detects USB devices with a
> WebUSB
> > interface defined, we should get this in as a standard
On Mon, Jan 16, 2017 at 3:23 PM, Simon McVittie <
simon.mcvit...@collabora.co.uk> wrote:
> On Mon, 09 Jan 2017 at 10:20:33 +0100, Lars Knudsen wrote:
> > 2. make sure that webusb devices will be somehow accessible to be used
> by a
> > browser running with user permissions (current temp solution
On Fri, Jan 20, 2017 at 12:05 PM, Greg KH
wrote:
> On Fri, Jan 20, 2017 at 11:43:24AM +0100, Lars Knudsen wrote:
> >
> >
> > On Mon, Jan 16, 2017 at 3:23 PM, Simon McVittie <
> simon.mcvit...@collabora.co.uk
> > > wrote:
> >
> > On Mon, 09 Jan 2017 at 10:20:33
On Fri, Jan 20, 2017 at 11:43:24AM +0100, Lars Knudsen wrote:
>
>
> On Mon, Jan 16, 2017 at 3:23 PM, Simon McVittie
> > wrote:
>
> On Mon, 09 Jan 2017 at 10:20:33 +0100, Lars Knudsen wrote:
> > 2. make sure that webusb devices will be somehow
On Fri, Jan 20, 2017 at 01:18:12PM +0100, Lars Knudsen wrote:
> > The full device should be fine if it has a WebUSB interface (even in a
> > composite scenario)
>
> Really? You want to allow someone "raw" access to a composite device
> just because of one specific interface?
>
>
Hi there,
I see that there is a concern that we need to keep machine-id private
(and local?). I haven't been able to determine exactly why though*.
In most cases it's randomly generated afaict.
I'd consider using it to replace whoopsie-id which is generated from
the machines BIOS information
On Fri, Jan 20, 2017 at 02:02:07PM -0500, Bryan Quigley wrote:
> Hi there,
>
> I see that there is a concern that we need to keep machine-id private
> (and local?). I haven't been able to determine exactly why though*.
> In most cases it's randomly generated afaict.
It's a unique identifier for
Am 20.01.2017 um 11:20 schrieb Raghavendra. H. R:
I have a scenario in which I have 2 processes and both acts as Server &
Client.
Process A starts it server & tries to connect as client with Process B.
Process B starts it server & tries to connect as client with Process A.
We want handle this
12 matches
Mail list logo