HyperForum — hyperbola first install experience

Re: hyperbola first install experience

null@example.com (zapper) — Tue, 11 May 2021 18:45:15 +0000

rachad wrote:

for avoiding DUID dhcpcd.conf tells us (send MAC-adress clientdid)
clientid
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid
i think sending nothing by deleting dhcpcd.duid is better than sending MAC-adress clientid, correct me if im wrong!

Commenting it out I believe disables it also.

Re: hyperbola first install experience

null@example.com (rachad) — Mon, 10 May 2021 19:04:58 +0000

for avoiding DUID dhcpcd.conf tells us (send MAC-adress clientdid)
clientid
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

i think sending nothing by deleting dhcpcd.duid is better than sending MAC-adress clientid, correct me if im wrong!

Re: hyperbola first install experience

null@example.com (throgh) — Fri, 13 Nov 2020 01:27:08 +0000

Thanks for the insights about dhcpcd and the configuration!

Re: hyperbola first install experience

null@example.com (dikasp2) — Tue, 10 Nov 2020 23:51:04 +0000

very usefull

im usually cheating with usb tethering connection to bypass all the fuss for first time install tough

hyperbola first install experience

null@example.com (the_hype) — Fri, 06 Nov 2020 08:39:43 +0000

i am quite impressed by hyperbola!

it looks nice , package selection is great (some are quite old though - but that's the price of debian-stability )
((as for request for newer packages i would like a newer cryptsetup - the rest is (mostly) fine for me))

also the blacklist is great.

the installation was straight forward, but the wifi connection failed because the was no

nohook wpa_supplicant

in the dhcpcd.conf (or the dhcpcd-hook clobbers the wpa_supplicant config from before)

also i would like to mention that the dhcpcd-config leads to many data leaks, (vendoridclass is really bad - it sends os, kernel version etc.)
i guess the dhcpcd.conf is the vanilla one, but a commented line like this could be useful:

#uncomment this for a more privacy aware behaviour
#nooption 4 7 14 17 19 20 21 27 40 41 42 69 70 71 72 73 75 76
#nohook hostname

there is a package called dhcpcd_hardened (which calls /usr/libexec/dhcpcd/dhcpcd_hardened.sh
) to achieve this, but it seems really broken to me and i cannot recommend it, because it does tihs:

#!/bin/sh
# This script wipes hostname and DUID so that DHCP can't send it over the network
echo 'hostname="localhost"' > /etc/conf.d/hostname
# Properly sets our new host in /etc/hosts file
sed -i '/127.0.0.1/c\127.0.0.1       localhost.localdomain   localhost 'localhost'' /etc/hosts
# Avoids need to reboot before showing our new hostname in terminals, etc
hostname localhost
# Delete DUID
rm -rf /etc/dhcpcd.duid

for avoiding DUID dhcpcd.conf tells us (send MAC-adress clientdid)

clientid
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

thx and have a nice day!