> Quoting Arnt Karlsen (a...@iaksess.no):
>
> > ..my /etc/cron.d/machine-id:
> > PATH=/bin:/usr/bin:/sbin:/usr/sbin
> >
> > # ..a new /etc/machine-id every minute... ;o)
> > * * * * * root date |md5sum |cut -d" " -f-1 >/etc/machine-id |tee
> > >/dev/null 2>&1
>
> _Very_ nice solution. I thin
On 2019-03-09 02:05, marc wrote:
Quoting Arnt Karlsen (a...@iaksess.no):
> ..my /etc/cron.d/machine-id:
> PATH=/bin:/usr/bin:/sbin:/usr/sbin
>
> # ..a new /etc/machine-id every minute... ;o)
> * * * * * root date |md5sum |cut -d" " -f-1 >/etc/machine-id |tee
> >/dev/null 2>&1
_Very_ nice sol
Le 09/03/2019 à 00:28, Arnt Karlsen a écrit :
I might go: " * * * * * root \
fortune &&date |md5sum |cut -d" " -f-1 >/etc/machine-id |tee \
>/dev/null 2>&1 " to keep this lightweight in my end and not
in the other end. :o)
Arnt, Could you be less cryptic please?
I found fortune in p
Le 09/03/2019 à 09:34, goli...@dyne.org a écrit :
I'd recommend adding an inotify rule to record which processes
look at these files, and publishing this - here.
Unfortunately inotify doesn't tell which process accessed the file )~:
___
Dng mail
Le 09/03/2019 à 10:03, Didier Kryn a écrit :
Le 09/03/2019 à 09:34, goli...@dyne.org a écrit :
I'd recommend adding an inotify rule to record which processes
look at these files, and publishing this - here.
Unfortunately inotify doesn't tell which process accessed the file
)~:
But f
Anno domini 2019 Sat, 9 Mar 10:03:59 +0100
Didier Kryn scripsit:
> Le 09/03/2019 à 09:34, goli...@dyne.org a écrit :
> > I'd recommend adding an inotify rule to record which processes
> > look at these files, and publishing this - here.
>
> Unfortunately inotify doesn't tell which process ac
> Le 09/03/2019 ?? 10:03, Didier Kryn a ??crit??:
> >Le 09/03/2019 ?? 09:34, goli...@dyne.org a ??crit??:
> >>I'd recommend adding an inotify rule to record which processes
> >>look at these files, and publishing this - here.
> >
> >Unfortunately inotify doesn't tell which process accessed the file
On Sat, Mar 09, 2019 at 09:05:20AM +0100, marc wrote:
[cut]
>
> But what really blows me away is that these ids exist on
> Debian to begin with. I had been under the assumption that
> free systems are built according to the needs and desires
> of their users, and few users go "what I really need
Il 09/03/19 09:53, Didier Kryn ha scritto:
> Le 09/03/2019 à 00:28, Arnt Karlsen a écrit :
>> I might go: " * * * * * root \
>> fortune &&date |md5sum |cut -d" " -f-1 >/etc/machine-id |tee \
>> >/dev/null 2>&1 " to keep this lightweight in my end and not
>> in the other end. :o)
>
> Arnt, C
> Mark, I think you are probably shooting the wrong bird here. Host ids
> have been around for the best part of the last 40 years in the unix
> world. And I am not talking about proprietary unix. The syscalls
> gethostid/sethostid were introduced in 4.2BSD (ca. 1983), at Berkeley,
> and are suppose
Hi,
On 9/3/19 8:37, aitor_czr wrote:
My latest image of gnuinos beowulf (not uploaded yet) waits for a
keyboard press event during live boots.
I'm still not sure if this is related with the new version of slim.
I'll check it soon. Another possible cause might be
the non configured live-config s
On Sat, Mar 09, 2019 at 11:16:51AM +0100, marc wrote:
[cut]
>
> I also agree with your sentiment that free and open source
> software is necessary to track down information leakage. But it
> seems it may be necessary but not sufficient - what one also
> needs is a distribution which makes it cle
Il 09/03/19 11:16, marc ha scritto:
>> Mark, I think you are probably shooting the wrong bird here. Host ids
>> have been around for the best part of the last 40 years in the unix
>> world. And I am not talking about proprietary unix. The syscalls
>> gethostid/sethostid were introduced in 4.2BSD (
On Sat, 9 Mar 2019 08:21:18 +0100, Alessandro wrote in message
:
> On 09/03/19 at 00:28, Arnt Karlsen wrote:
>
> > ..both valid improvements, me, I might go: " * * * * * root \
> > fortune &&date |md5sum |cut -d" " -f-1 >/etc/machine-id |tee \
> > >/dev/null 2>&1 " to keep this lightweight
On Sat, 9 Mar 2019 09:05:20 +0100, marc wrote in message
<20190309080520.GA32402@localhost.localdomain>:
> So instead of adding crontab rules to obfuscate the ids,
...er, say "to flood them with useless IDs," if you want
my agreement.
> I'd recommend adding an inotify rule to record which pro
> > So you are correct that gethostid has been around for a while,
> > but this call returns a 32bit number, typically the IP.
>
> ?? No, it returns a value that's unique to the local machine even if it
> was not configured on any network.?? Plus, the IP can change, but the
> hostid is supposed to
> Dear marc,
>
> unwanted "calls-home" are normally found and disclosed if the software
> is free, so I really don't think this is a problem. Asking the
> development team of a distribution with 50k+ packages to guarantee
> that nothing ever uses user information for unwanted means is just
> plain
On 09/03/19 at 12:46, marc wrote:
>>> So you are correct that gethostid has been around for a while,
>>> but this call returns a 32bit number, typically the IP.
>> ?? No, it returns a value that's unique to the local machine even if it
>> was not configured on any network.?? Plus, the IP can change
On Sat, Mar 09, 2019 at 01:11:31PM +0100, marc wrote:
[cut]
>
> B) I am more concerned about the other part, where code is
> known to phone home, but the developers or packagers
> have decided that this is fine. The examples range from popcon
> to systemd's resolver (which I am told falls back o
Il giorno sabato 09/03/2019 10:54:08 +0100
KatolaZ ha scritto:
> On Sat, Mar 09, 2019 at 09:05:20AM +0100, marc wrote:
>
> [cut]
>
> > [cut]
>
> [cut]
>
> In any case, there are dozens of ways to identify a host and a user
> with very good accuracy, even across reboots and even when it travels
Il giorno sabato 09/03/2019 13:25:29 +0100
Alessandro Selli ha scritto:
> [cut]
> > Maybe your system is different to mine, but try compiling the below
> > and find out for yourself:
> >
> > #include
> > #include
> >
> > int main()
> > {
> > int id;
> >
> > id = gethostid();
> >
> > pri
On 09/03/19 at 14:04, al3xu5 / dotcommon wrote:
>
>> my id is 0x007f0101
>>
>> [...]
>>
>> my id is 0x007f0101
>>
>> [...]
>>
>> my id is 0x007f0101
>>
> using the `hostid` command, I have (Devuan ASCII):
>
> $ hostid
> 007f0101
>
> which is the same value!!!
>
> I wonder... is it a "fixed" id for
On Saturday 09 March 2019 at 14:21:30, Alessandro Selli wrote:
> On 09/03/19 at 14:04, al3xu5 / dotcommon wrote:
> >> my id is 0x007f0101
> >>
> >> [...]
> >>
> >> my id is 0x007f0101
> >>
> >> [...]
> >>
> >> my id is 0x007f0101
> >
> > using the `hostid` command, I have (Devuan ASCII):
> >
On Sat, Mar 09, 2019 at 02:28:10PM +0100, Antony Stone wrote:
[cut]
> > >
> > > I wonder... is it a "fixed" id for all Devuan installation as it seems to
> > > be?
> > >
> > > And if it is so,is it correct that it is?
> >
> > How intriguing!
>
> I get the same value on a Debian Wheezy machi
On Sat, 9 Mar 2019 14:04:13 +0100, al3xu5 wrote in message
<20190309130422.386f8f60...@vm6.ganeti.dyne.org>:
> Il giorno sabato 09/03/2019 13:25:29 +0100
> Alessandro Selli ha scritto:
>
> > [cut]
>
> > > Maybe your system is different to mine, but try compiling the
> > > below and find out
On Sat, Mar 09, 2019 at 02:34:28AM -0600, goli...@dyne.org wrote:
>
> Oh, my . . . how fast and how hard Debian has fallen . . I am all for
> shining light into dark, dank places. What a terrific idea to track
> down all the offending packages that are "leaking" information and then
> publish an
On 2019-03-09 03:03, Didier Kryn wrote:
Le 09/03/2019 à 09:34, goli...@dyne.org a écrit :
I'd recommend adding an inotify rule to record which processes
look at these files, and publishing this - here.
Unfortunately inotify doesn't tell which process accessed the file
)~:
___
On Sat, 9 Mar 2019 16:27:10 +0100
Arnt Karlsen wrote:
> On Sat, 9 Mar 2019 14:04:13 +0100, al3xu5 wrote in message
> <20190309130422.386f8f60...@vm6.ganeti.dyne.org>:
> >
> > I wonder... is it a "fixed" id for all Devuan installation as it
> > seems to be?
>
> ..yes and no and no etc, I have:
On 2019-03-09 07:21, Alessandro Selli wrote:
On 09/03/19 at 14:04, al3xu5 / dotcommon wrote:
my id is 0x007f0101
[...]
my id is 0x007f0101
[...]
my id is 0x007f0101
using the `hostid` command, I have (Devuan ASCII):
$ hostid
007f0101
which is the same value!!!
I wonder... is it a "fix
Le 09/03/2019 à 17:25, goli...@dyne.org a écrit :
On 2019-03-09 03:03, Didier Kryn wrote:
Le 09/03/2019 à 09:34, goli...@dyne.org a écrit :
I'd recommend adding an inotify rule to record which processes
look at these files, and publishing this - here.
Unfortunately inotify doesn't tell wh
Hello
> > B) I am more concerned about the other part, where code is
> > known to phone home, but the developers or packagers
> > have decided that this is fine. The examples range from popcon
> > to systemd's resolver (which I am told falls back on to google
> > at 8.8.8.8) to chromium or firefo
I find it comic that dbus, which is a middleware restricted to a
single host, builds a unique id to identify this host. We know that the
systemd team likes to catch up everything to control it from their blob,
even if it looks like pure crap. This makes me think the intention is
probably no
On Sat, 9 Mar 2019 08:37:03 +0100
aitor_czr wrote:
> My latest image of gnuinos beowulf (not uploaded yet) waits for a
> keyboard press event during live boots.
If openssh-server is installed, it's waiting for entropy. Install
haveged and make sure it starts before ssh. I made a modified
live-
On Sat, 9 Mar 2019 18:12:55 +0100, Didier wrote in message
<42982bbd-6ccc-6ed4-2bcc-4d969319c...@in2p3.fr>:
> I find it comic that dbus, which is a middleware restricted to a
> single host, builds a unique id to identify this host. We know that
> the systemd team likes to catch up everythin
On Sat, Mar 09, 2019 at 11:01:43AM -0500, Hendrik Boom wrote:
> On Sat, Mar 09, 2019 at 02:34:28AM -0600, goli...@dyne.org wrote:
> > Oh, my . . . how fast and how hard Debian has fallen . . I am all for
> > shining light into dark, dank places. What a terrific idea to track
> > down all the offe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Devuan.org website seams to be down. I can't reach it, and neither can
that checker page: https://www.isitdownrightnow.com/devuan.org.html
Could someone fix that please?
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEZT8xKpcJ1eXNKSM1cASjafdLVoEFAlyE
On Sat, 9 Mar 2019 22:15:46 +, Daniel wrote in message
:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Devuan.org website seams to be down. I can't reach it, and neither can
> that checker page: https://www.isitdownrightnow.com/devuan.org.html
>
> Could someone fix that please?
Le 09/03/2019 à 21:48, Arnt Karlsen a écrit :
On Sat, 9 Mar 2019 18:12:55 +0100, Didier wrote in message
<42982bbd-6ccc-6ed4-2bcc-4d969319c...@in2p3.fr>:
I find it comic that dbus, which is a middleware restricted to a
single host, builds a unique id to identify this host. We know that
th
On 9/3/19 23:43, Arnt Karlsen wrote:
On Sat, 9 Mar 2019 22:15:46 +, Daniel wrote in message
:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Devuan.org website seams to be down. I can't reach it, and neither can
that checker page:https://www.isitdownrightnow.com/devuan.org.html
Could som
On Sat, Mar 09, 2019 at 10:38:57AM -0600, goli...@dyne.org wrote:
On 2019-03-09 07:21, Alessandro Selli wrote:
> On 09/03/19 at 14:04, al3xu5 / dotcommon wrote:
> >
> > > my id is 0x007f0101
> > >
> > > [...]
> > >
> > > my id is 0x007f0101
> > >
> > > [...]
> > >
> > > my id is 0x007f0101
>
On 2019-03-09 16:53, aitor_czr wrote:
On 9/3/19 23:43, Arnt Karlsen wrote:
On Sat, 9 Mar 2019 22:15:46 +, Daniel wrote in message
:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Devuan.org website seams to be down. I can't reach it, and neither
can
that checker page:https://www.isitdo
Antoine via Dng wrote on 10/3/19 10:00 am:
> I tried changing the IPaddress on my loopback interface, but the
> returned hostid didn't change.
Try editing /etc/hosts and move your hostname entry to something else
Ralph.
___
Dng mailing list
Dng@lists.
On 3/8/19 10:04 PM, Mark Hindley wrote:
> Would people who are experiencing missing slim utmp entries mind trying again
> with the following configuration added to /etc/slim.conf, please?
>
> sessionstop_cmd exec /usr/bin/sessreg -d -l $DISPLAY %user
> sessionstart_cmd exec /usr/bin/sessreg -a -l
fsmithred via Dng writes:
> On Sat, 9 Mar 2019 16:27:10 +0100
> Arnt Karlsen wrote:
>
>> On Sat, 9 Mar 2019 14:04:13 +0100, al3xu5 wrote in message
>> <20190309130422.386f8f60...@vm6.ganeti.dyne.org>:
>> >
>> > I wonder... is it a "fixed" id for all Devuan installation as it
>> > seems to be?
>>
Hendrik Boom writes:
> On Sat, Mar 09, 2019 at 02:34:28AM -0600, goli...@dyne.org wrote:
>>
>> Oh, my . . . how fast and how hard Debian has fallen . . I am all for
>> shining light into dark, dank places. What a terrific idea to track
>> down all the offending packages that are "leaking" infor
On Sun, Mar 10, 2019 at 09:06:50AM +0900, Olaf Meeuwissen wrote:
[cut]
> > I get 007f0100 on one jessie, 007f0101 on another jessie and 007f0101
> > on ascii. (Three different computers)
> >
> > The ascii install is on a laptop that has several installations. When I
> > reboot it into jessie, I g
46 matches
Mail list logo
