Twój profil na Facebooku, zobacz

2019-12-15 Thread Daniel Lichosik - prowadzenie FanPage

Dzień dobry,

zdobycieklientów to najważniejsza kwestia przy prowadzeniu firmy.

Dobrze prosperującyFanpage na Facebookuto wizytówka Państwa 
działalności.

Wiemy jak skuteczniegoadministrować i jak docierać do klientów z 
Państwa branży.

Wiadomość o treściTAK,umożliwi nam kontakt w tej sprawie.


/Z wyrazami szacunku,
Specjaliści ds. Social Mediów./


Re: apparent change in hostnames on LAN without admin intervention

2019-12-15 Thread mick crane

On 2019-12-16 05:43, David Wright wrote:

On Sat 14 Dec 2019 at 10:08:56 (+), mick crane wrote:

On 2019-12-14 03:04, Jape Person wrote:

> I could be quite wrong, but I thought that "local" was actually
> suggested as a domain name at one time by the installer. (And I could
> be remembering a different distro, though I've been using Debian for a
> long time -- at least 10 years, I think.) I suppose I just continued
> to use it over the years out of habit.

I had the same thing a while back. I too always thought .local was the
recommendation and at the time .home was used by a phone company so
thought it best not to use that.


Which phone company was that, and when?


That would have been BT 15 years or so ago.
I know they use home.bt.com but I must have seen ( or thought I did 
).home as the top level domain somewhere to do with them.


mick



--
Key ID4BFEBB31



Re: apparent change in hostnames on LAN without admin intervention

2019-12-15 Thread tv.deb...@googlemail.com

I am not the OP, but questions seems directed to me, see inline answers.

On 16/12/2019 11:12, David Wright wrote:

On Sun 15 Dec 2019 at 11:49:55 (+0530), tv.deb...@googlemail.com wrote:

On 15/12/2019 00:35, Jape Person wrote:

On 12/14/19 3:56 AM, Andrei POPESCU wrote:

On Vi, 13 dec 19, 19:33:51, Jape Person wrote:

Hi folks. Did I miss something?

I've had 3 Sid/testing systems running on the same LAN behind the same
router for just shy of 3 years. Their static IP addresses
have always been
issued by the DHCP server on the router. Everything has
been copacetic among
the systems, with local and outside name resolution
working with no issue.

A little over a week ago the systems stopped being able to
access each other
by name. No changes were made in the settings or firmware
of the router or
of the local network settings on the systems.

I discovered that all of the hostnames had changed from xx.local to
xx. I've tried to determine the cause of this alteration in the
hostnames on the LAN.


Please provide more info on this, specifically where / how are the
hostnames configured and where / how did you discover they changed.

Do note that .local is typically used by mDNS and in my understanding it
should not be used with a DNS server.

https://en.wikipedia.org/wiki/.local


The hostnames and local domain name were used during installation.

The static DHCP addresses are issued by a Luxul XWR-1750 router
which associates the hostnames with the MAC and IP addresses.

Contents of /etc/resolv.conf:

search local
nameserver 208.67.220.220

I discovered the change a few days ago when I was doing my daily
check for updates by using SSH to connect to two of the systems. I
received the following response to the connection command:

ssh: Could not resolve hostname chip-nuc.local: Name or service not known

I checked to make sure I could connect to everything by IP
address, and I checked DNS on the outside world. Everything looked
okay.

On a hunch I tried omitting the .local from the connection
command, and it work on each client.

I figured any time the name of a client changes without deliberate
action on the part of the network admin (however incompetent he
may be), that could be a security issue. That's why I asked here.


Hi, I am running a very similar setup, also on Sid/Testing (updated
daily), and didn't notice any change. My local domain is not ".local"
or ".home", it is custom.


That might be a reason for no change to have occurred.

Just out of curiosity, is your custom name registered or just made up?


Made up, it exists only on my LAN.


My resolv.conf looks like yours (modulo the domain name), I have an
additional nameserver line for my router address. My router only
resolves names for the local network, public DNS is resolved though a
VPN.

My hosts file is just standard :

   

one line per host on the network, the router has the same hosts file,
the IP are reserved by the router DHCP and associated with (static
spoofed) MAC addresses. Routers are running on Asuswrt-Merlin and
openWRT (one is AP mode only).


Again, curious, why do you maintain hosts files on each host? As you
resolve that other hosts on your network by DNS at the router, I
would have expected all your hosts files to look like:

127.0.0.1   localhost
127.0.1.1   foo.custom   foo

for host foo.



One of the PC is serving various services to the LAN, some bypassing the 
router for load/performances reason, this PC is carrying an up to date 
version of the hosts file. It's not one hosts file on every machines on 
the network, it's one hosts file with every machines on the LAN 
registered in it on one of the node on the LAN.



ssh here works with both hostnames short alias (no domain), full name or IP.

 

works as expected and return the host IP.

Since we probably have the same packages versions let me know if you
need me to check anything that could differ from your system.


Cheers,
David.


Hope it satisfies your curiosity.



Re: apparent change in hostnames on LAN without admin intervention

2019-12-15 Thread David Wright
On Sun 15 Dec 2019 at 11:49:55 (+0530), tv.deb...@googlemail.com wrote:
> On 15/12/2019 00:35, Jape Person wrote:
> > On 12/14/19 3:56 AM, Andrei POPESCU wrote:
> > > On Vi, 13 dec 19, 19:33:51, Jape Person wrote:
> > > > Hi folks. Did I miss something?
> > > > 
> > > > I've had 3 Sid/testing systems running on the same LAN behind the same
> > > > router for just shy of 3 years. Their static IP addresses
> > > > have always been
> > > > issued by the DHCP server on the router. Everything has
> > > > been copacetic among
> > > > the systems, with local and outside name resolution
> > > > working with no issue.
> > > > 
> > > > A little over a week ago the systems stopped being able to
> > > > access each other
> > > > by name. No changes were made in the settings or firmware
> > > > of the router or
> > > > of the local network settings on the systems.
> > > > 
> > > > I discovered that all of the hostnames had changed from xx.local to
> > > > xx. I've tried to determine the cause of this alteration in the
> > > > hostnames on the LAN.
> > > 
> > > Please provide more info on this, specifically where / how are the
> > > hostnames configured and where / how did you discover they changed.
> > > 
> > > Do note that .local is typically used by mDNS and in my understanding it
> > > should not be used with a DNS server.
> > > 
> > > https://en.wikipedia.org/wiki/.local
> > 
> > The hostnames and local domain name were used during installation.
> > 
> > The static DHCP addresses are issued by a Luxul XWR-1750 router
> > which associates the hostnames with the MAC and IP addresses.
> > 
> > Contents of /etc/resolv.conf:
> > 
> > search local
> > nameserver 208.67.220.220
> > 
> > I discovered the change a few days ago when I was doing my daily
> > check for updates by using SSH to connect to two of the systems. I
> > received the following response to the connection command:
> > 
> > ssh: Could not resolve hostname chip-nuc.local: Name or service not known
> > 
> > I checked to make sure I could connect to everything by IP
> > address, and I checked DNS on the outside world. Everything looked
> > okay.
> > 
> > On a hunch I tried omitting the .local from the connection
> > command, and it work on each client.
> > 
> > I figured any time the name of a client changes without deliberate
> > action on the part of the network admin (however incompetent he
> > may be), that could be a security issue. That's why I asked here.
> 
> Hi, I am running a very similar setup, also on Sid/Testing (updated
> daily), and didn't notice any change. My local domain is not ".local"
> or ".home", it is custom.

That might be a reason for no change to have occurred.

Just out of curiosity, is your custom name registered or just made up?

> My resolv.conf looks like yours (modulo the domain name), I have an
> additional nameserver line for my router address. My router only
> resolves names for the local network, public DNS is resolved though a
> VPN.
> 
> My hosts file is just standard :
> 
>  
> 
> one line per host on the network, the router has the same hosts file,
> the IP are reserved by the router DHCP and associated with (static
> spoofed) MAC addresses. Routers are running on Asuswrt-Merlin and
> openWRT (one is AP mode only).

Again, curious, why do you maintain hosts files on each host? As you
resolve that other hosts on your network by DNS at the router, I
would have expected all your hosts files to look like:

127.0.0.1   localhost
127.0.1.1   foo.custom   foo

for host foo.

> ssh here works with both hostnames short alias (no domain), full name or IP.
> 
>
> 
> works as expected and return the host IP.
> 
> Since we probably have the same packages versions let me know if you
> need me to check anything that could differ from your system.

Cheers,
David.



Re: apparent change in hostnames on LAN without admin intervention

2019-12-15 Thread David Wright
On Sat 14 Dec 2019 at 13:36:28 (-), Curt wrote:
> On 2019-12-14, David Wright  wrote:
> > On Fri 13 Dec 2019 at 19:33:51 (-0500), Jape Person wrote:
> >> Hi folks. Did I miss something?
> >
> > Perhaps a couple of references:
> > https://features.icann.org/addressing-new-gtld-program-applications-corp-home-and-mail
> > which points out that any of .home, .mail and .corp are ideal for the
> > domain name of a home LAN, and RFC 6762 on Multicast DNS which
> > explains why .local is not a good choice.
> 
> I'm trying to fathom why .home would remain ideal for home LAN users in
> light of RFC 8375, which replaces the previously advised '.home' with
> 'home.arpa' as the default domain name for homenets, the former being
> known to often leak out to the root name servers.
> 
> https://tools.ietf.org/html/rfc8375

As I see it, what you're looking for in choosing a domain name at home
is a name¹ that isn't already a TLD on the Internet, and is not going
to become one in the future. In addition, you don't want something
that's going to become the domain name² for some new protocol that's
around the corner.

My understanding of RFC 8375 is that .home got hit as a category ²,
but that this was seen as a mistake which this RFC corrected.

As for leaking out to the root name servers, this is the reason that
ICANN chose not to issue .home, .mail and .corp as TLDs, but instead
to refund any money taken from organisations trying to register such
domains. That intention is what makes them good candidates for being
future-proof in category ¹.

> Or does RFC 8378[5] only apply to toasters and the like (what will they
> think of next)?

I think the idea is that toasters and so on will configure themselves
on homenet, but this means that people doing their own configuration
have to steer clear rather than get in their way. AIUI that is why
mDNS resulted in pushing .local into category ², to the dismay of the
many who thought .local to be a good choice under category ¹.

Cheers,
David.



Re: apparent change in hostnames on LAN without admin intervention

2019-12-15 Thread David Wright
On Sat 14 Dec 2019 at 10:08:56 (+), mick crane wrote:
> On 2019-12-14 03:04, Jape Person wrote:
> 
> > I could be quite wrong, but I thought that "local" was actually
> > suggested as a domain name at one time by the installer. (And I could
> > be remembering a different distro, though I've been using Debian for a
> > long time -- at least 10 years, I think.) I suppose I just continued
> > to use it over the years out of habit.
> 
> I had the same thing a while back. I too always thought .local was the
> recommendation and at the time .home was used by a phone company so
> thought it best not to use that.

Which phone company was that, and when?

> Seem to remember having trouble tracking down everywhere it is
> mentioned.

That's one reason I use corp: grepping /etc hits occurrences of home
and mail, but none of corp (except the ones I've added).

Cheers,
David.



Re: apparent change in hostnames on LAN without admin intervention

2019-12-15 Thread David Wright
On Sat 14 Dec 2019 at 13:49:25 (-0500), Jape Person wrote:
> On 12/14/19 1:24 AM, john doe wrote:
> > 
> > Assuming that you are using the router from your ISP, it is possible
> > that the firmware has been upgraded without your nolage.
> > 
> > One way to prevent this could be (1), that is, use your own
> > router/server/gateway so you control everything on your LAN.
> > 
> > I use an EMTA modem only from my ISP which is plugged into a perimiter
> > firewall.
> > 
> > If you can't have an modem from your ISP, look at 'bridgemode'.
> > 
> > If your not comfortable building your server from scratch, you can
> > simply buy a router that is accepted by your ISP .
> > 
> > In other words, you need to choose one or the other if you go this way:
> > - Modem connected to router (most flexible of all)
> > - Combo modem/router in one box (les flexible but is more compact)
> > 
> > If you use DHCP static lease, you should look at what the DHCP server is
> > providing as hostname and 'TLD', and also in the dhcp client (dhclient'
> > to see what you get from the DHCP server.
> > 
> > The file '/etc/resolv.conf' should let you know what TLD is sent from
> > the DHCP server.
> > 
> > Debian shouldn't modify your configuration files '/etc' without your nolage.

Depending on the packages chosen, /etc/resolv.conf is one file in /etc
that is modified by Debian. The resolvconf package lists 23 other
programs that it is designed to adjudicate between, for want of a
better term.

> > Note that the TLD '.lan' is sometime used.

That's another choice, like .local, that could always be issued as a
real TLD at some point in the future.

> > 1)  https://www.xfinity.com/support/articles/list-of-approved-cable-modems
> 
> I'm using my own router behind the modem provided by the ISP. I've
> never used a router provided by an ISP for controlling my network.
> 
> I'm using a Luxul XWR-1750 which has been kept on the latest firmware
> available. Last upgrade was done early this year, long before the
> noted change in names.
> 
> The router is set to provide static IP addresses and has the names of
> each of the systems associated with their MAC Addresses and IP
> Addresses.

Can you just clarify this? My router provides static IP addresses on
the basis of the MAC addresses, all the information being typed in¹
by me. It also lists the names of the other hosts, but only because
those hosts told it their names. IOW the router (cheap, $35) doesn't
issue hostnames, nor provide a DNS service itself. It also neither
knows nor cares what the domain name of the network is.

How much of this is the same on the router in your network?

¹ actually, of course, it deduces all but the last number in the
dotted quad.

Cheers,
David.



Re: Alternative to dhcp?

2019-12-15 Thread Carl Johnson
X-Rcmultipart/mixed;
boundary="Add_By_Label_Mail_Nextpart_001"Spam: 2008-11-04_01
Resent-Message-ID: 
Resent-From: debian-user@lists.debian.org
X-Mailing-List:  archive/latest/574188
X-Loop: debian-user@lists.debian.org
List-Id: 
List-Post: 
List-Help: 
List-Subscribe: 
List-Unsubscribe: 

Precedence: list
Resent-Sender: debian-user-requ...@lists.debian.org
Resent-Date: Thu, 15 Apr 2010 17:24:11 + (UTC)

Ed Jabbour 
--Add_By_Label_Mail_Nextpart_001
Content-Type: text/plain;

 writes:

> On Wed, 14 Apr 2010 17:31:54 -0400, Celejar wrote:
>
>>> Ed Jabbour  wrote:
>
>>> I edited /etc/resolv.conf to add a nameserver, edited
>>> etc/dhcp3/dhclient.conf to do the same and added the dns to wicd.  
>>> However, I keep getting the same old dns from the router, i.e., 
>>> resolv.conf keeps changing to the router's 192 ip.  The router does not
>>> allow editing dns.  I think this is due to using dhcp.  Is there an
>>> alternative which wouldn't cause a default to the router's dns?  Any 
>>> pointers appreciated.
>>
>>Do 'man dhclient.conf' and look at the prepend and supersede options.
>
> I had already done that.  I tried either one and both.  I had also already 
> done the wicd gui edit.  As I said above, my chosen dns doesn't stick, as 
> resolv.conf keeps reverting to the router's.   

Has the dhclient been restarted since you edited the configuration
file, either manually or through a reboot?  I use the prepend- option,
but I assume that it isn't reread automatically so I kill and restart
the client manually when I change the file.

-- 
Carl Johnsonca...@peak.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87vdbsy6hl.fsf@cjlinux.localnet




Re: looking for a replacement for debian since systemd

2019-12-15 Thread 0...@caiway.net
On Fri, 13 Dec 2019 15:36:00 -0800
Peter Ehlert  wrote:

> drama queen much?
> 

I did not like the idea of systemd.
But I do like systemd-container very much.
I am using it for years now.
Run services in a container, easy backup, easy migrate, reboot in 3
seconds.

So nowadays I tolerate systemd in my systems.



Re: looking for a replacement for debian since systemd

2019-12-15 Thread Jimmy Johnson

On 12/14/19 5:29 AM, Jonas Smedegaard wrote:

Hi Alessandro,

Quoting Alessandro Vesely (2019-12-14 13:23:14)

On Sat 14/Dec/2019 03:18:39 +0100 Kenneth Parker wrote:


I use Devuan, especially on older hardware.   Works well.



Good to know.  For the time being, I see SysV is working.  I'm on
old-stable Debian.  As, in a few months, it will be time to migrate,
I'll have to decide on Devuan (current) vs. Buster.  Any
recommendation on that?  Will the voted resolution shred any light on
migration strategies?


Since this is a Debian list, I recommend to discuss Debian here, and
consult Devuan mailinglist for details of what they can offer.

The vote currently in Debian will affect _future_ releases of Debian,
not the current stable release, Buster.

For Debian Buster (regardless of the outcome of the vote) SysV is a
supported init system: Please do report any flaws you may encounter!


Kde5 on buster without systemd don't work, all kde5 is config for 
systemd, screen settings and pluseaudio will not save settings, to bad, 
so sad.


Give it a try and see for yourself.
--
Jimmy Johnson

Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda5
Registered Linux User #380263



Re: looking for a replacement for debian since systemd

2019-12-15 Thread Jimmy Johnson

On 12/13/19 1:55 PM, Britton Kerin wrote:

I see from below vote that we're working on dumping other init systems
now as expected.  Luckily I've given up on debian since systemd in the
first place and am in long process of finding a replacement.


Some options are slackware it comes with xfce and kde4, slackware live 
with kde5, another is mxlinux for xfce, it's real nice, probably the 
best xfce desktop I've seen if you like xfce and it's using debian, and 
another is pclinuxos it has xfce and kde5. I'm running pclos kde5, 
slackware 14.2, slackware current and slackware live kde5 and I'm still 
testing debian but I don't think it's linux anymore than windows10 is, 
just another mainstream backdoor. Already mentioned are bsd and devuan 
and devuan has some forks to look at too.

--
Jimmy Johnson

Slackware64 14.2 - KDE 4.14.32 - AMD A8-7600 - EXT4 at sda5
Registered Linux User #380263



Re : Re: Erreur d'URL pour la liste debian user french

2019-12-15 Thread k6dedijon
Bonjour,
Je viens d'avoir un message disant que le site avait changé.
Il sont sur :
https://www.lip6.fr/
reste à chercher ce qui t'intéresse.
Cassis




- Mail d'origine -
De: G2PC 
À: debian-user-french@lists.debian.org
Envoyé: Sun, 15 Dec 2019 19:01:52 +0100 (CET)
Objet: Re: Erreur d'URL pour la liste debian user french


Le 15/12/2019 à 18:36, daniel huhardeaux a écrit :
> Le 15/12/2019 à 17:51, G2PC a écrit :
>> Le 15/12/2019 à 17:17, daniel huhardeaux a écrit :
>>> Le 15/12/2019 à 17:10, G2PC a écrit :
 https://www.debian.org/doc/manuals/fr/debian-fr-howto/ch1.html

 Le lien suivant ne fonctionne pas :

 La dernière version de ce document se trouve à l'adresse :
 |http://www.poleia.lip6.fr/~sabouret/debian/debian-french.html|.

>>>
>>> Bonsoir,
>>>
>>> je ne comprends pas ton message mais je peux dire, si tel était
>>> l'affirmation,  que le lien debian.org fonctionne et celui de lip6.fr
>>> non.
>>
>>
>> C'est bien ça, sur le premier lien, la référence du second lien n'est
>> pas fonctionnel.
>>
> Et, quel est le message que tu veux passer ?

Je te laisse y penser.




Build Kernel 5.5 RC1 for Raspberry4

2019-12-15 Thread basti
Hello,

i have try as follows:

- export ARCH=arm ; export CROSS_COMPILE=aarch64-linux-gnu-
- copy config-4.19.0-6-arm64 to .config
- run make olddefconfig
- make menuconfig to add cpu-freq driver for bcm2711
- make -j'nproc' bindeb-pkg
- copy content of package to sd-card
- use Image to boot instead of vmlinuz

When i try to use the dtb from build process the following is shown on uart:

��>���p�p���|p�|�|��p�pp�ppp�p|p�|���p�p||p�p�|pp�p�p|p�pp�p�pp|pp�pp�ppp�p�p�pp�pp�p|p�p��p��|�pp�|ppp��p�|pp��pp

I don't know what this mean.

When i try to boot via u-boot with the original rasbian
bcm2711-rpi-4-b.dtb the following in shown on uart:

U-Boot 2020.01-rc4-g85432c69 (Dec 14 2019 - 20:08:51 +0100)

DRAM: 3.9 GiB
RPI 4 Model B (0xc03111)
MMC: emmc2@7e34: 0, mmcnr@7e30: 1
Loading Environment from FAT... *** Warning - bad CRC, using default
environment

In: serial
Out: serial
Err: serial
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
U-Boot> fatload mmc 0:1 ${fdt_addr_r} bcm2711-rpi-4-b.dtb
40559 bytes read in 30 ms (1.3 MiB/s)
U-Boot> fatload mmc 0:1 ${kernel_addr_r} Image.5.5
20996608 bytes read in 1374 ms (14.6 MiB/s)
U-Boot> setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait rw
U-Boot> booti ${kernel_addr_r} - ${fdt_addr_r}
## Flattened Device Tree blob at 0260
Booting using the fdt blob at 0x260
Using Device Tree in place at 0260, end 0260ce6e

Starting kernel ...

it hangs here.

I try to boot directly via kernel=Image in config.txt bit nothing is shown.
I have compare vmlinuz-4.19.0-2-arm64 (from
https://wiki.debian.org/RaspberryPiImages) and my build Image with
'file' both are MS-DOS executable.

My config.txt looks like:

arm_64bit=1
enable_uart=1
#kernel=u-boot.bin
kernel=Image5.5

Has someone try to build upstream kernel 5.5-rc1 for raspi4?

best regards



Re: Erreur d'URL pour la liste debian user french

2019-12-15 Thread G2PC


Le 15/12/2019 à 18:36, daniel huhardeaux a écrit :
> Le 15/12/2019 à 17:51, G2PC a écrit :
>> Le 15/12/2019 à 17:17, daniel huhardeaux a écrit :
>>> Le 15/12/2019 à 17:10, G2PC a écrit :
 https://www.debian.org/doc/manuals/fr/debian-fr-howto/ch1.html

 Le lien suivant ne fonctionne pas :

 La dernière version de ce document se trouve à l'adresse :
 |http://www.poleia.lip6.fr/~sabouret/debian/debian-french.html|.

>>>
>>> Bonsoir,
>>>
>>> je ne comprends pas ton message mais je peux dire, si tel était
>>> l'affirmation,  que le lien debian.org fonctionne et celui de lip6.fr
>>> non.
>>
>>
>> C'est bien ça, sur le premier lien, la référence du second lien n'est
>> pas fonctionnel.
>>
> Et, quel est le message que tu veux passer ?

Je te laisse y penser.



Re:debian 10.2 installation guide

2019-12-15 Thread Mindaugas Celiesius
Hello. Please, check this link:

https://www.debian.org/releases/stable/installmanual



Re: Erreur d'URL pour la liste debian user french

2019-12-15 Thread daniel huhardeaux

Le 15/12/2019 à 17:51, G2PC a écrit :

Le 15/12/2019 à 17:17, daniel huhardeaux a écrit :

Le 15/12/2019 à 17:10, G2PC a écrit :

https://www.debian.org/doc/manuals/fr/debian-fr-howto/ch1.html

Le lien suivant ne fonctionne pas :

La dernière version de ce document se trouve à l'adresse :
|http://www.poleia.lip6.fr/~sabouret/debian/debian-french.html|.



Bonsoir,

je ne comprends pas ton message mais je peux dire, si tel était
l'affirmation,  que le lien debian.org fonctionne et celui de lip6.fr
non.



C'est bien ça, sur le premier lien, la référence du second lien n'est
pas fonctionnel.


Et, quel est le message que tu veux passer ?
--
Daniel



Re: [OT] Master Password (was: dropbox security situation)

2019-12-15 Thread Brian
On Sat 14 Dec 2019 at 19:09:44 +0100, l0f...@tuta.io wrote:

> Hi,
> 
> 13 déc. 2019 à 00:29 de a...@cityscape.co.uk:
> 
> > On Thu 12 Dec 2019 at 21:13:06 +0100, l0f...@tuta.io wrote:
> >
> >> 10 déc. 2019 à 23:11 de a...@cityscape.co.uk:
> >>
> >> > On Tue 10 Dec 2019 at 22:34:07 +0100, l0f...@tuta.io wrote:
> >> >
> >> >
> >> I've read the documentation. User needs to remember all of
> >> this:
> >>
> >
> > > user-name
> >
> > Real name actually. If you do not know your name you have problems. :)
> > Can be set in ~/.bash_rc. Cross this off the list.
> >
> You are weakening security if you write down or save in specific files
> some elements used for the password generation. But I agree with you,
> it's not the most problematic one ;)
> 
> >> site-name
> >>
> > It is in the address bar of the site you are accessing. google.com,
> > debian.org, bt.com etc. What is there to remember? We cross this off
> > your list too.
> >
> As I was explaining before, I'm pretty sure some cases are not so
> obvious (like sites where authentication page is deported/redirected
> so as time is passing you don't remember which "site" you used the
> first time, same issue with websites on multiple domains, sometimes
> you need to specify the subdomain as well...).

Using the website name is merely a suggestion. It can be anything you
like, provided you can remember it. For example, I use "doctor" for one
site; "surgery" or "prescription" would be equally as good.

> >> site-counter
> >>
> > I'll give you this. But it would be very unusual to want it. The
> > default is generally good enough.
> >
> As discussed after my answer, this is a point.
> >> site-template.
> >>
> You didn't answer to that but that's one more thing to remember
> especially if you needed a custom password initially.

I did not respond in detail to this because I did not recognise it as a
requirement.

> Let's be clear, I think this solution Master Password is original and
> I'm not saying it's impossible to remember all these criteria for most
> of us. But I know it can be problematic for some people, especially
> site-counter and site-template in addition to a master password. Each
> element is generally easy but all of them can be a burden for some
> people with time passing.

I have everything in a script, so in the normal course of events have
nothing to remember - apart from the master password. Master Password
is essentially a calculator; it is not a password vault. Something
for a user to play with:

  https://js.masterpassword.app/

-- 
Brian.



debian 10.2 installation guide

2019-12-15 Thread Leonardo Dijava

Hi !

I trust you are well. I have downloaded debian 10.2 CD  on debian.org zebsite. 
I would like knoz toinstall it. Can you please send me the installation guide 
for 64 and 32bits  if possible in pdf in order to launchthat linux distribution 
?

Regards



Re: Erreur d'URL pour la liste debian user french

2019-12-15 Thread G2PC
Le 15/12/2019 à 17:17, daniel huhardeaux a écrit :
> Le 15/12/2019 à 17:10, G2PC a écrit :
>> https://www.debian.org/doc/manuals/fr/debian-fr-howto/ch1.html
>>
>> Le lien suivant ne fonctionne pas :
>>
>> La dernière version de ce document se trouve à l'adresse :
>> |http://www.poleia.lip6.fr/~sabouret/debian/debian-french.html|.
>>
>
> Bonsoir,
>
> je ne comprends pas ton message mais je peux dire, si tel était
> l'affirmation,  que le lien debian.org fonctionne et celui de lip6.fr
> non.


C'est bien ça, sur le premier lien, la référence du second lien n'est
pas fonctionnel.




Re: apparent change in hostnames on LAN without admin intervention

2019-12-15 Thread Jape Person

On 12/15/19 1:19 AM, tv.deb...@googlemail.com wrote:
...


Hi, I am running a very similar setup, also on Sid/Testing (updated
daily), and didn't notice any change. My local domain is not ".local" or
".home", it is custom.

My resolv.conf looks like yours (modulo the domain name), I have an
additional nameserver line for my router address. My router only
resolves names for the local network, public DNS is resolved though a VPN.

My hosts file is just standard :

   

one line per host on the network, the router has the same hosts file,
the IP are reserved by the router DHCP and associated with (static
spoofed) MAC addresses. Routers are running on Asuswrt-Merlin and
openWRT (one is AP mode only).

ssh here works with both hostnames short alias (no domain), full name or IP.

 

works as expected and return the host IP.

Since we probably have the same packages versions let me know if you
need me to check anything that could differ from your system.



Thank you very much for your kind offer! I am interested in figuring this out, but it will probably 
be at least after the first of the year before I'll be able to devote much time to it.


I'm happy to have things apparently working as they should, for now. But this experience has made me 
curious.


The information you provided, and your offer of help are much appreciated!

Best,
JP



Re: Erreur d'URL pour la liste debian user french

2019-12-15 Thread daniel huhardeaux

Le 15/12/2019 à 17:10, G2PC a écrit :

https://www.debian.org/doc/manuals/fr/debian-fr-howto/ch1.html

Le lien suivant ne fonctionne pas :

La dernière version de ce document se trouve à l'adresse : 
|http://www.poleia.lip6.fr/~sabouret/debian/debian-french.html|.




Bonsoir,

je ne comprends pas ton message mais je peux dire, si tel était 
l'affirmation,  que le lien debian.org fonctionne et celui de lip6.fr non.


--
Daniel



Erreur d'URL pour la liste debian user french

2019-12-15 Thread G2PC
https://www.debian.org/doc/manuals/fr/debian-fr-howto/ch1.html

Le lien suivant ne fonctionne pas :

La dernière version de ce document se trouve à l'adresse :
|http://www.poleia.lip6.fr/~sabouret/debian/debian-french.html|.



Re: Debian 10.2 ne démarre pas

2019-12-15 Thread G2PC
Le 15/12/2019 à 09:55, didier.gau...@gmail.com a écrit :
> - ça te dit de vérifier /var/log/Xorg.0.log pour plus de détails: l'as-tu 
> fait? peut-être y trouveras-tu d'autres indices...
> - ça te dit aussi que tel quel X ne peut se lancer en mode framebuffer: 
> vérifier si tu as paramétré une option vga=nnn dans ton grub et la virer si 
> c'est le cas pourrait aider (ce n'est qu'une supposition parce que je ne 
> connais pas les mécanismes en marche dans ce cas mais si le PC boote en mode 
> framebuffer via grub, peut-être est-il difficile (par ssh?) voire impossible 
> de le faire passer en mode direct plus tard?

Bonne question :/
Entre temps j'ai tenté de démarrer avec une live usb Debian 10.2
non-free mais même soucis, écran noir.

J'ai ensuite tenté quelques fois d'installer Mint 19.3
lmde-3-201808-cinnamon-64bit.iso mais je n'arrivais pas à obtenir un
boot en étant toujours en UEFI activé dans le BIOS.
Je rappel que, avec le BIOS par défaut, j'avais pu mener l'installation
de Debian, qui avait finalisé l'installation du Grub.

Finalement, j'ai désactivé dans le UEFI BIOS Utility, les 2 options
suivantes :
Advanced mode / Démarrage / Configuration du démarrage / Démarrage
rapide : Disabled
Advanced mode / Démarrage / Démarrage sécurisé / Type de système
d'exploitation : Autre SE

Avec cette configuration du Bios, j'ai pu installer Mint, mais, qui n'a
reconnu que le système Mint nouvellement installé et, le système Mint
sur le disque secondaire.
Les deux systèmes Windows n'ont pas été identifiés lors de
l'installation du Grub.
En mettant à jour le Grub avec "update-grub" et "update-grub2", une fois
connecté sur le nouveau Mint installé, j'ai pu récupérer les deux
entrées de Windows dans le menu de démarrage.


Super, ça fonctionne et le Grub m'affiche les bons choix ( 2x mint, 2x
Windows, et un choix de setup pour redémarrer sur le Bios )
Dommage, ce n'est pas Debian qui a pu être installé.


Étrange tout de même, si je vais dans le Bios, je vois afficher dans les
" Séquences de démarrage " :

Debian (M2.2_1:Samsung SSD EVO Plus 500GB) (500.1GB)
Debian (M2.2_1:Samsung SSD EVO Plus 500GB) (500.1GB)
... autres séquences de démarrage ( le windows sur le 500Go , le windows
sur le disque secondaire 2000Go, le mint sur le disque secondaire
2000Go, la carte éthernet avec 2 entrées ipv4 et ipv6, et, une dernière
entrée pour UEFI: MultipleCard Reader )

Je ne comprend pas pourquoi ses deux entrées de debian sont encore
présentes dans le BIOS, alors que j'ai finalement pu installer Mint.
Si je comprend bien, ses entrées la affichées dans le BIOS ne sont pas
liées au Grub.
Ne faudrait t'il pas tenter de s'en débarasser ?




Re: Debian 10.2 ne démarre pas

2019-12-15 Thread didier . gaumet


- ça te dit de vérifier /var/log/Xorg.0.log pour plus de détails: l'as-tu fait? 
peut-être y trouveras-tu d'autres indices...
- ça te dit aussi que tel quel X ne peut se lancer en mode framebuffer: 
vérifier si tu as paramétré une option vga=nnn dans ton grub et la virer si 
c'est le cas pourrait aider (ce n'est qu'une supposition parce que je ne 
connais pas les mécanismes en marche dans ce cas mais si le PC boote en mode 
framebuffer via grub, peut-être est-il difficile (par ssh?) voire impossible de 
le faire passer en mode direct plus tard?