Re: [OT] Acceso ssh

[User]

On Fri, 02 Oct 2020 18:39:46 +, User wrote:

> On Fri, 02 Oct 2020 05:31:47 +, Andrés DG wrote:
> 
>> Nmap tendría que devolverte los puertos que se encuentrar abiertos.
>> Salvo que este bloqueado el protocolo ICMP (en ese caso creo que las
>> opciones PS y PA funcionaban para obtener info de los hosts conectados
>> a la red nmap -PS ip_a_consultar  o   nmap -PA ip_a_consultar).
>> En mi caso me pasaba con el router de la oficina, que de buenas a
>> primera no me dejaba acceder de forma remota (a través de una IP
>> pública) al servidor por ssh. Tenía que reiniciarlo para poder acceder
>> de forma remota (desde la red local nunca tenía problemas). Terminé
>> solicitando una IP pública estática y de ahí en más, hasta ahora, no
>> tuve problemas. Aun así, en mi caso, creo que debe haber sido alguna
>> falla del router de la oficina.
>> Perdón que no pueda ayudarte más.
> 
> Me ayudastes, gracias.
> 
> Hice nmap a la Lan, y resulta que es el router el que esta filtrando el
> ssh. Probare a entrar via puerto 80!
> 
> Gracias.

Curioso!

Para probar $ssh -R, instale Openssh-server, en mi Buster, e 
inmediatamente, tenia peticiones ssh!

Como lo haran?

Re: docker.io

[Camaleón]

El 2020-10-04 a las 11:27 +0200, franiortiz escribió:

> en un pc que ya no uso, recuerdo instalar docker desde repositorios oficiales 
> de debian (main contrib non-free) y funcionaba bien.
> Ahora pienso en instalarlo de nuevo y googleando' el mismo metodo que usé, 
> pero todos los tutoriales hablan de añadir 
> los repos de dockerhub, que docker.io es antiguo o quedará  obsoleto...
> no me gusta añadir repos distintos a los oficiales, luego la distro me queda 
> echa unos zorros de dependencias.

Si la aplicación está bien empaquetada y preparada (es decir, si detrás 
hay un buen desarrollo), no tendrás problemas de dependencias.

> Que tiene de malo instalar docker.io desde los repos oficiales de debian?
 
Nada, simplemente que la versión que tengas en los repos de Debian será 
más antigua pero poco más.

Saludos,

-- 
Camaleón 

Chat: Soy nuevo aquí necesito ayuda . [...]

[Jose Felipe]

Soy nuevo aquí necesito ayuda .
DIOS los bendiga

-- 
Enviado con mi aplicación de mensajería Delta Chat: https://delta.chat

Chat: Como funciona este sistema de [...]

[Jose Felipe]

Como funciona este sistema de correo ?

-- 
Enviado con mi aplicación de mensajería Delta Chat: https://delta.chat

Chat: Mandame tu correo púes no lo [...]

[Jose Felipe]

Mandame tu correo púes  no lo se.
Saludos.

-- 
Enviado con mi aplicación de mensajería Delta Chat: https://delta.chat

Re : Pinephone et Mobian

[k6dedijon]

Bonjour Jean-Marc,
Je ne connaissais pas le Pinephone, mais je connais la E Foundation :
https://e.foundation/fr/
Celle-ci propose de remplacer la version Android de Google par une version 
libre d'Android.
Get your deGoogled smartphone now!
Version libérée des intrusions concernant la vie privée, version utilisable 
sans compte Google.
Soit vous comprenez et savez l'installer sur votre smartphone, soit ils vendent 
des smartphones avec cette version d'Android pré-installée.
Un tour sur leur site m'a fait découvrir qu'ils allaient prochainement proposer 
d'installer leur version d'Android sur votre smartphone.
(Voir à l'occasion s'ils peuvent installer leur Android libre sur le Pinephone.)
J'en ai un depuis un peu plus d'un an et j'en suis fort content.

Voilà si ça peut aider
Cassis




- Mail d'origine -
De: Jean-Marc 
À: Liste Debian 
Envoyé: Sun, 04 Oct 2020 22:19:41 +0200 (CEST)
Objet: Pinephone et Mobian

salut la liste,

Quelqu'un a déjà essayé ça : Pinephone et Mobian ?

https://www.lafilacroche.com/post/premiers-pas-avec-pinephone-edition-postmarketos.html

Bonne fin de dimanche.

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt
https://6jf.be/keys/ED0B8558.txt

Chat: Bots para delta chat

[Jose Felipe]

Bots para delta chat

-- 
Enviado con mi aplicación de mensajería Delta Chat: https://delta.chat

Pinephone et Mobian

[Jean-Marc]

salut la liste,

Quelqu'un a déjà essayé ça : Pinephone et Mobian ?

https://www.lafilacroche.com/post/premiers-pas-avec-pinephone-edition-postmarketos.html

Bonne fin de dimanche.

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt
https://6jf.be/keys/ED0B8558.txt


pgpsH22fFJWF3.pgp
Description: PGP signature

Re: Mounting /dev/shm noexec

[Valter Jaakkola]

Hi, and thank you all for the great replies!

So I added the following line to fstab:
tmpfs /dev/shm tmpfs rw,nosuid,nodev,noexec 0 0
and it works, just as you said it would. No second /dev/shm popping up or other
stuff I had assumed.

(I'm not sure if it now takes a second longer for the GNOME login screen to
appear after boot, but I didn't find any errors in logs and things seem to
work.)

Steve McIntyre wrote:
> Andy Smith wrote:
> 
> > Though note that it seems systemd once did use "noexec" for /dev/shm
> > but stopped 10 years ago because it broke some uses of mmap:
> > 
> >
> > https://github.com/systemd/systemd/commit/501c875bffaef3263ad42c32485c7fde41027175
> 
> libffi also has a habit of using /dev/shm for writing temporary
> trampolines for cross-language calls, and they need to be executable.

I'll keep these in mind if I run into problems later on.

Kind regards,
Valter Jaakkola

Re: preseed ansible problem

[Muhammad Yousuf Khan]

Adding List.

On Sun, Oct 4, 2020 at 7:44 PM Muhammad Yousuf Khan 
wrote:

> > Oct  4 08:01:44 in-target: Ign:1 cdrom://[Official Debian GNU/Linux Live
>> > 10.6.0 xfce 2020-09-26T13:15] buster InRelease
>> > Oct  4 08:01:44 in-target: Err:2 cdrom://[Official Debian GNU/Linux Live
>> > 10.6.0 xfce 2020-09-26T13:15] buster Release
>> > Oct  4 08:01:44 in-target:   Please use apt-cdrom to make this CD-ROM
>> > recognized by APT. apt-get update cannot be used to add new CD-ROMs
>>
>> This seems to be your real issue: the CDROM seems to be (still?) listed
>> in your apt sources list (look around /etc/apt/sources.list and below
>> /etc/apt/sources.list.d).
>>
>> To fix that, you'll first have to get clear on where your to-be Debian
>> install is going to get its packages from (really from the CDROM?) and
>> adjust those files accordingly.
>>
>
> Thank you for the response. can you please help me fix this actually i
> tried the following but still i am getting the same issue.
> d-i apt-setup/disable-cdrom-entries boolean true
> But this seems to be not working and still throwing the same issue. can
> you please help.
>
> Thanks.
>
>
>> Cheers
>>  - t
>>
>

Re: docker.io

[Eduardo Visbal]

Amigo usa la documentacion oficial de Docker para la instalacion; alli no
te da problemas de nada.

https://docs.docker.com/engine/install/debian/




*Eduardo VisbalLinuxero #440451http://esdebianfritto.blogspot.com/
*


El dom., 4 oct. 2020 a las 17:09, franiortiz ()
escribió:

> Hola a todos.
> una pequeña consulta.
> en un pc que ya no uso, recuerdo instalar docker desde repositorios
> oficiales de debian (main contrib non-free) y funcionaba bien.
> Ahora pienso en instalarlo de nuevo y googleando' el mismo metodo que usé,
> pero todos los tutoriales hablan de añadir
> los repos de dockerhub, que docker.io es antiguo o quedará  obsoleto...
> no me gusta añadir repos distintos a los oficiales, luego la distro me
> queda echa unos zorros de dependencias.
> Que tiene de malo instalar docker.io desde los repos oficiales de debian?
>
>

xdm password display [was: How to disable the screen locker on amd64 buster?]

[tomas]

On Sun, Oct 04, 2020 at 07:20:22PM +0100, Brian wrote:
> On Sun 04 Oct 2020 at 14:59:18 +0200, to...@tuxteam.de wrote:
> 
> > On Sun, Oct 04, 2020 at 01:36:45PM +0100, Brian wrote:

[...]

> > > The tradition allows for configuring xdm to show stars when the password
> > > is typed.
> > 
> > That's right, but it's not the default. My advice was just for the
> > case that the OP wasn't "seeing" that things might be working as
> > intended.
> 
> Indeed it's not the default. My advice was for those users of xdm who
> would like some visual feedback when authenticating.

BTW. I looked it up, and the knob for that: set the X resource
xlogin.Login.echoPasswd to 'true' for that (CAVEAT: untested!)
create (or extend, if already present) the file /etc/X11/Xresources/xdm
and add the line

  Xdm*xlogin.Login.echoPasswd: true

Perhaps I come around to testing it tomorrow, then I'll shake
out the five bugs yet in there :)

Cheers
 - t


signature.asc
Description: Digital signature

docker.io

[franiortiz]

Hola a todos.
una pequeña consulta.
en un pc que ya no uso, recuerdo instalar docker desde repositorios oficiales 
de debian (main contrib non-free) y funcionaba bien.
Ahora pienso en instalarlo de nuevo y googleando' el mismo metodo que usé, pero 
todos los tutoriales hablan de añadir 
los repos de dockerhub, que docker.io es antiguo o quedará  obsoleto...
no me gusta añadir repos distintos a los oficiales, luego la distro me queda 
echa unos zorros de dependencias.
Que tiene de malo instalar docker.io desde los repos oficiales de debian?

Re: Chat: Necesito algunos bots para Delta Chat

[Francisco Cid]

Buenas tardes, yo puedo realizar lo que usted necesita, escríbame
directamente a mi correo y le haré llegar una cotización. Saludos cordiales.

El dom., 4 oct. 2020 14:42, Jose Felipe 
escribió:

> Necesito algunos bots para Delta Chat
>
> --
> Enviado con mi aplicación de mensajería Delta Chat: https://delta.chat
>
>

Re: How to disable the screen locker on amd64 buster?

[Brian]

On Sun 04 Oct 2020 at 14:59:18 +0200, to...@tuxteam.de wrote:

> On Sun, Oct 04, 2020 at 01:36:45PM +0100, Brian wrote:
> > On Sun 04 Oct 2020 at 12:14:01 +0200, to...@tuxteam.de wrote:
> 
> [...]
> 
> > > Just a silly shot in the dark: are you sure it isn't taking keypresses?
> > > Note that xdm doesn't display anything when you type into a password
> > > box. No dots, no stars, anything. Good old tradition...
> > 
> > The tradition allows for configuring xdm to show stars when the password
> > is typed.
> 
> That's right, but it's not the default. My advice was just for the
> case that the OP wasn't "seeing" that things might be working as
> intended.

Indeed it's not the default. My advice was for those users of xdm who
would like some visual feedback when authenticating.

-- 
Brian.

Chat: Necesito algunos bots para Delta Chat

[Jose Felipe]

Necesito algunos bots para Delta Chat

-- 
Enviado con mi aplicación de mensajería Delta Chat: https://delta.chat

Bug report - Samba version 4.9.5-Debian

[Martin Kormunda]

Hi,

Sorry, I am not able to use reportbug.

I have installed two debian based OS in Proxmox system. I have a big
issue  with both of them.
1.  Turnkey 16.0  Fileserver
2. OpenMediaVault 5.5.12-1

Both of them are using Samba version 4.9.5-Debian.

It works well in both systems until I try to access, upload or
download more files (35 000 or more)  in total about 300 GB.
Then the samba crashed!!!  The time intervat to crash is various from
20 minutes to 2 hours from try to try.
But the system is not usable as a file server for my use. I can
reproduce the crash but the detail log is too huge.
Is it only my problem?
What should I try?
I am already desperate. I never had such an issue in linux based system before.

Thanks for help

Best Regards
Martin


The example of log at crash:

Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568347

Oct 1 18:29:09 storage smbd[13319]:
===

Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568441

Oct 1 18:29:09 storage smbd[13319]: INTERNAL ERROR: Signal 6 in pid
13319 (4.9.5-Debian)

Oct 1 18:29:09 storage smbd[13319]: Please read the Trouble-Shooting
section of the Samba HOWTO

Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568468

Oct 1 18:29:09 storage smbd[13319]:
===

Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.568483

Oct 1 18:29:09 storage smbd[13319]: PANIC (pid 13319): internal error

Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.599323

Oct 1 18:29:09 storage smbd[13319]: BACKTRACE: 13 stack frames:

Oct 1 18:29:09 storage smbd[13319]: #0
/lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace+0x32)
[0x7efce81058d2]

Oct 1 18:29:09 storage smbd[13319]: #1
/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20)
[0x7efce7d251c0]

Oct 1 18:29:09 storage smbd[13319]: #2
/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f)
[0x7efce81059df]

Oct 1 18:29:09 storage smbd[13319]: #3
/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x24c16) [0x7efce8105c16]

Oct 1 18:29:09 storage smbd[13319]: #4
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7efce8173730]

Oct 1 18:29:09 storage smbd[13319]: #5
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b) [0x7efce740e7bb]

Oct 1 18:29:09 storage smbd[13319]: #6
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7efce73f9535]

Oct 1 18:29:09 storage smbd[13319]: #7
/lib/x86_64-linux-gnu/libc.so.6(+0x79508) [0x7efce7450508]

Oct 1 18:29:09 storage smbd[13319]: #8
/lib/x86_64-linux-gnu/libc.so.6(+0x7fc1a) [0x7efce7456c1a]

Oct 1 18:29:09 storage smbd[13319]: #9
/lib/x86_64-linux-gnu/libc.so.6(+0x818a2) [0x7efce74588a2]

Oct 1 18:29:09 storage smbd[13319]: #10
/lib/x86_64-linux-gnu/libc.so.6(+0x84af3) [0x7efce745baf3]

Oct 1 18:29:09 storage smbd[13319]: #11
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fc9) [0x7efce8168fc9]

Oct 1 18:29:09 storage smbd[13319]: #12
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7efce74d04cf]

Oct 1 18:29:09 storage smbd[13319]: [2020/10/01 18:29:09.599440

Oct 1 18:29:09 storage smbd[13319]: smb_panic(): calling panic action
[/usr/share/samba/panic-action 13319]

Oct 1 18:29:10 storage postfix/sendmail[13329]: fatal: chdir
/var/spool/postfix: Permission denied

Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.68

Oct 1 18:29:31 storage smbd[13405]:
===

Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.644533

Oct 1 18:29:31 storage smbd[13405]: INTERNAL ERROR: Signal 6 in pid
13405 (4.9.5-Debian)

Oct 1 18:29:31 storage smbd[13405]: Please read the Trouble-Shooting
section of the Samba HOWTO

Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.644559

Oct 1 18:29:31 storage smbd[13405]:
===

Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.644584

Oct 1 18:29:31 storage smbd[13405]: PANIC (pid 13405): internal error

Oct 1 18:29:31 storage smbd[13405]: [2020/10/01 18:29:31.645098

Oct 1 18:29:31 storage smbd[13405]: BACKTRACE: 13 stack frames:

Oct 1 18:29:31 storage smbd[13405]: #0
/lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace+0x32)
[0x7efce81058d2]

Oct 1 18:29:31 storage smbd[13405]: #1
/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20)
[0x7efce7d251c0]

Oct 1 18:29:31 storage smbd[13405]: #2
/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f)
[0x7efce81059df]

Oct 1 18:29:31 storage smbd[13405]: #3
/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x24c16) [0x7efce8105c16]

Oct 1 18:29:31 storage smbd[13405]: #4
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730) [0x7efce8173730]

Oct 1 18:29:31 storage smbd[13405]: #5
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b) [0x7efce740e7bb]

Oct 1 18:29:31 storage smbd[13405]: #6
/lib/x86_64-linux-gnu/libc.so.6(abort+0x121) [0x7efce73f9535]

Oct 1 18:29:31 storage smbd[13405]: #7
/lib/x86_64-linux-gnu/libc.so.6(+0x79508) 

Re: [testing] noyau 5.8 => plus de sortie audio analogique

[Gaëtan Perrier]

Actuellement c'est du grand n'importe quoi. Hier j'avais récupéré la config
"stéréo" qui a redisparu aujourd'hui ...


Le samedi 03 octobre 2020 à 08:46 +0200, Orion a écrit :
> Bonjour,
> 
> je suis confronté au même problème (SID), mais c'est assez systématique  :
> un pulseaudio -k puis pulseaudio -D ne résoud pasle pb chez moi.
> je cherche une solution
> 
> en comparant la  sortie pactl info d'une fedora Fedora 32:
> fedora:
> Profils :
> input:analog-stereo: Entrée Stéréo analogique (sinks: 0, sources: 1,
> priority: 65, available: oui)
> output:analog-stereo: Sortie Stéréo analogique (sinks: 1, sources: 0,
> priority: 6500, available: oui)
> output:analog-stereo+input:analog-stereo: Duplex stéréo analogique (sinks: 1,
> sources: 1, priority: 6565, available: oui)
> output:iec958-stereo: Sortie Stéréo numérique (IEC958) (sinks: 1, sources: 0,
> priority: 5500, available: oui)
> output:iec958-stereo+input:analog-stereo: Sortie Stéréo numérique (IEC958) +
> Entrée Stéréo analogique (sinks: 1, sources: 1, priority: 5565, available:
> oui)
> 
> debian :
> Profils :
> input:analog-stereo: Entrée Stéréo analogique (sinks: 0, sources: 1,
> priority: 65, available: oui)
> output:iec958-stereo: Sortie Stéréo numérique (IEC958) (sinks: 1, sources: 0,
> priority: 5500, available: oui)
> output:iec958-stereo+input:analog-stereo: Sortie Stéréo numérique (IEC958) +
> Entrée Stéréo analogique (sinks: 1, sources: 1, priority: 5565, available:
> oui)
> 
> j''ai pas les profils
> output:analog-stereo: Sortie Stéréo analogique (sinks: 1, sources: 0,
> priority: 6500, available: oui)
> output:analog-stereo+input:analog-stereo: Duplex stéréo analogique (sinks: 1,
> sources: 1, priority: 6565, available: oui)
> sous debian, je peux les rajouter?
> 
> On Thu, Sep 24, 2020 at 9:15 PM Gaëtan Perrier 
> wrote:
> > Le jeudi 24 septembre 2020 à 06:54 +0200, F. Dubois a écrit :
> > > Le 24/09/2020 à 01:11, Gaëtan Perrier a écrit :
> > > > Bonjour,
> > > > 
> > > > Je viens de passer en 5.8 sur ma testing et je constate que je n'ai
> > plus de
> > > > sortie audio analogique. Seule une sortie SPDIF est présentée ...
> > > > Est-ce pareil pour vous ?
> > > > 
> > > > Gaëtan
> > > 
> > > Bonjour,
> > > 
> > > Oui, c'est très aléatoire. Pulseaudio débloque complètement. Je suis en 
> > > Sid mais ça correspond bien, on dirait, au changement de noyau.
> > > 
> > > Normalement un pulseaudio -k puis pulseaudio -D résout le problème... 
> > > jusqu'au prochain reboot.
> > > Pas plus à dire, donc si il y a plus d'explications je suis preneur
> > aussi.
> > > 
> > > Fabien
> > > 
> > 
> > Bonjour,
> > 
> > Je ne sais pas si c'est lié aux mises à jours de udev et systemd
> > aujourd'hui
> > mais j'ai récupéré ma sortie analogique. Par contre il me semblait que dans
> > le
> > temps on pouvait sélectionner une config 2.0 ou 2.1 ? Maintenant c'est 5.0
> > mini
> > ...
> > 
> > Gaëtan



signature.asc
Description: This is a digitally signed message part

Re: How to disable the screen locker on amd64 buster?

[Gene Heskett]

On Sunday 04 October 2020 06:14:01 to...@tuxteam.de wrote:

> On Sun, Oct 04, 2020 at 05:46:05AM -0400, Gene Heskett wrote:
>
> [...]
>
> > Except I now have a different initial login screen that does not
> > accept my passwd.  It accepts and displays my username, but it loses
> > the keyboard once it highlights the passwd box
>
> Just a silly shot in the dark: are you sure it isn't taking
> keypresses? Note that xdm doesn't display anything when you type into
> a password box. No dots, no stars, anything. Good old tradition...
>
> Just hack in your password and hit ENTER.

That keyboard has a dirt/swarf cover that makes error free typeing a much 
sought after experience, but if I hammer it one punch at a time, it 
works. That got me in and let me disable the rest of the niggles.  
Obviously I rarely write code on that keyboard.

Thanks Tomas.

> Cheers
>  - t


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Advice and/or help

[kdibble]

I don't know to whom these should go to, or how to get them fixed.



Documentation:



Having read the fine manual:



Neither 

man apparmor

or

man apparmor.d



have any mention of apparmor.d/local



There is no mention of proper formatting of apparmor.d/local files.



At https://gitlab.com/apparmor/apparmor/-/wikis/Policy_Layout

there is a mention of

${APPARMOR.D}/local/

and

${HOME}/.apparmor/



but there does not appear to be any documentation on

formatting of the files in the local subdirectory, 

which is different from the profiles.



Profiles and packaging:



FIREFOX-ESR

There is no apparmor profile for FIREFOX-ESR



There is a firefox profile in apparmor-profiles-extra.deb 

which appears to work after changing the name appropriately.



MSMTP

The apparmor profile is part of the package.





The point of these last items is the inconsistent packaging.



There should probably be a guideline that profiles go with the package

or in a separate package.



I discovered this after installing MSMTP and having it mysteriously fail

when the log directory was changed by the command line switch.



I imagine that I am not the first person to have the learning opportunity

that inconsistent packaging creates.



Regards,



Ken

Re: Device to use with cryptsetup Buster encrypted lvm

[john doe]

On 10/4/2020 4:52 PM, David Wright wrote:

On Sun 04 Oct 2020 at 16:39:38 (+0200), john doe wrote:

On 10/4/2020 4:35 PM, David Wright wrote:

On Sun 04 Oct 2020 at 16:16:33 (+0200), john doe wrote:

I just installed Debian Buster with encrypted LVM.

In my fstab file, I have:
#
/dev/mapper/try02--vg-root /   ext4errors=remount-ro 0
   1

I can't figure out what device I should pass to cryptsetup to avoid the
below error:

$ cryptsetup -v luksAddKey /dev/mapper/try02--vg-root /etc/keys/root.key
--key-slot=1
Device /dev/mapper/try02--vg-root doesn't exist or access denied.
Command failed with code -4 (wrong device or file specified).


How can I know what device cryptsetupt will accept?


It looks as if you're trying to add the key to the decrypted device,
ie the /dev/mapper/ device that gets mounted as /.
You add keys to the encrypted device, ie the device that contains the
encrypted filesystem, the argument you used in the command
# cryptsetup luksFormat 



The debian -installer has done that for me, I don't understand how I can
get the encrypted device.


I've not done that with the installer. I would expect there to be
an entry in /etc/crypttab for the root filesystem, so that it gets
mounted at boot time. It's the second field in that line.



In /etc/crypttab, the first column in the file has the device name
followed by '_crypt'.
Alternatively, use the UUID from the second column with the uuid option
of the blkid command.

$ blkid -U 


Thanks to you David and to 'Ulf Volmer '.


I appriciated.


--
John Doe

Chat: Ayuda

[Jose Felipe]

Ayuda

-- 
Enviado con mi aplicación de mensajería Delta Chat: https://delta.chat

Re: Device to use with cryptsetup Buster encrypted lvm

[Ulf Volmer]

On Sun, Oct 04, 2020 at 04:16:33PM +0200, john doe wrote:

> I just installed Debian Buster with encrypted LVM.
> 
> In my fstab file, I have:
> #
> /dev/mapper/try02--vg-root /   ext4errors=remount-ro 0
>  1
> 
> I can't figure out what device I should pass to cryptsetup to avoid the
> below error:
> 
> $ cryptsetup -v luksAddKey /dev/mapper/try02--vg-root /etc/keys/root.key
> --key-slot=1
> Device /dev/mapper/try02--vg-root doesn't exist or access denied.
> Command failed with code -4 (wrong device or file specified).
> 
> 
> How can I know what device cryptsetupt will accept?

You have to use your underlaying physical device.
This is stored in /etc/crypttab. lsblk may be also helpfull.

And root rights are required for this operation.

Best regards
Ulf

Re: Device to use with cryptsetup Buster encrypted lvm

[David Wright]

On Sun 04 Oct 2020 at 16:39:38 (+0200), john doe wrote:
> On 10/4/2020 4:35 PM, David Wright wrote:
> > On Sun 04 Oct 2020 at 16:16:33 (+0200), john doe wrote:
> > > I just installed Debian Buster with encrypted LVM.
> > > 
> > > In my fstab file, I have:
> > > #
> > > /dev/mapper/try02--vg-root /   ext4errors=remount-ro 0
> > >   1
> > > 
> > > I can't figure out what device I should pass to cryptsetup to avoid the
> > > below error:
> > > 
> > > $ cryptsetup -v luksAddKey /dev/mapper/try02--vg-root /etc/keys/root.key
> > > --key-slot=1
> > > Device /dev/mapper/try02--vg-root doesn't exist or access denied.
> > > Command failed with code -4 (wrong device or file specified).
> > > 
> > > 
> > > How can I know what device cryptsetupt will accept?
> > 
> > It looks as if you're trying to add the key to the decrypted device,
> > ie the /dev/mapper/ device that gets mounted as /.
> > You add keys to the encrypted device, ie the device that contains the
> > encrypted filesystem, the argument you used in the command
> > # cryptsetup luksFormat 
> > 
> 
> The debian -installer has done that for me, I don't understand how I can
> get the encrypted device.

I've not done that with the installer. I would expect there to be
an entry in /etc/crypttab for the root filesystem, so that it gets
mounted at boot time. It's the second field in that line.

Cheers,
David.

Re: Device to use with cryptsetup Buster encrypted lvm

[john doe]

On 10/4/2020 4:35 PM, David Wright wrote:

On Sun 04 Oct 2020 at 16:16:33 (+0200), john doe wrote:

I just installed Debian Buster with encrypted LVM.

In my fstab file, I have:
#
/dev/mapper/try02--vg-root /   ext4errors=remount-ro 0
  1

I can't figure out what device I should pass to cryptsetup to avoid the
below error:

$ cryptsetup -v luksAddKey /dev/mapper/try02--vg-root /etc/keys/root.key
--key-slot=1
Device /dev/mapper/try02--vg-root doesn't exist or access denied.
Command failed with code -4 (wrong device or file specified).


How can I know what device cryptsetupt will accept?


It looks as if you're trying to add the key to the decrypted device,
ie the /dev/mapper/ device that gets mounted as /.
You add keys to the encrypted device, ie the device that contains the
encrypted filesystem, the argument you used in the command
# cryptsetup luksFormat 



The debian -installer has done that for me, I don't understand how I can
get the encrypted device.

--
John Doe

Re: Device to use with cryptsetup Buster encrypted lvm

[David Wright]

On Sun 04 Oct 2020 at 16:16:33 (+0200), john doe wrote:
> I just installed Debian Buster with encrypted LVM.
> 
> In my fstab file, I have:
> #
> /dev/mapper/try02--vg-root /   ext4errors=remount-ro 0
>  1
> 
> I can't figure out what device I should pass to cryptsetup to avoid the
> below error:
> 
> $ cryptsetup -v luksAddKey /dev/mapper/try02--vg-root /etc/keys/root.key
> --key-slot=1
> Device /dev/mapper/try02--vg-root doesn't exist or access denied.
> Command failed with code -4 (wrong device or file specified).
> 
> 
> How can I know what device cryptsetupt will accept?

It looks as if you're trying to add the key to the decrypted device,
ie the /dev/mapper/ device that gets mounted as /.
You add keys to the encrypted device, ie the device that contains the
encrypted filesystem, the argument you used in the command
# cryptsetup luksFormat 

Cheers,
David.

Device to use with cryptsetup Buster encrypted lvm

[john doe]

Debians,

I just installed Debian Buster with encrypted LVM.

In my fstab file, I have:
#
/dev/mapper/try02--vg-root /   ext4errors=remount-ro 0
 1

I can't figure out what device I should pass to cryptsetup to avoid the
below error:

$ cryptsetup -v luksAddKey /dev/mapper/try02--vg-root /etc/keys/root.key
--key-slot=1
Device /dev/mapper/try02--vg-root doesn't exist or access denied.
Command failed with code -4 (wrong device or file specified).


How can I know what device cryptsetupt will accept?

--
John Doe

Re: How to disable the screen locker on amd64 buster?

[tomas]

On Sun, Oct 04, 2020 at 01:36:45PM +0100, Brian wrote:
> On Sun 04 Oct 2020 at 12:14:01 +0200, to...@tuxteam.de wrote:

[...]

> > Just a silly shot in the dark: are you sure it isn't taking keypresses?
> > Note that xdm doesn't display anything when you type into a password
> > box. No dots, no stars, anything. Good old tradition...
> 
> The tradition allows for configuring xdm to show stars when the password
> is typed.

That's right, but it's not the default. My advice was just for the
case that the OP wasn't "seeing" that things might be working as
intended.

Cheers
 - t


signature.asc
Description: Digital signature

Re: How to disable the screen locker on amd64 buster?

[Brian]

On Sun 04 Oct 2020 at 12:14:01 +0200, to...@tuxteam.de wrote:

> On Sun, Oct 04, 2020 at 05:46:05AM -0400, Gene Heskett wrote:
> 
> [...]
> 
> > Except I now have a different initial login screen that does not accept 
> > my passwd.  It accepts and displays my username, but it loses the 
> > keyboard once it highlights the passwd box
> 
> Just a silly shot in the dark: are you sure it isn't taking keypresses?
> Note that xdm doesn't display anything when you type into a password
> box. No dots, no stars, anything. Good old tradition...

The tradition allows for configuring xdm to show stars when the password
is typed.

-- 
Brian.

[SOLVED] Re: Missing i915 activity at boot time

[Rafa]

Hi,

Solved after installing linux-image-5.7.0-0.bpo.2-amd64 from
buster-backports.

Thank you all.

Rafa.



signature.asc
Description: PGP signature

Re: How to disable the screen locker on amd64 buster?

[tomas]

On Sun, Oct 04, 2020 at 05:46:05AM -0400, Gene Heskett wrote:

[...]

> Except I now have a different initial login screen that does not accept 
> my passwd.  It accepts and displays my username, but it loses the 
> keyboard once it highlights the passwd box

Just a silly shot in the dark: are you sure it isn't taking keypresses?
Note that xdm doesn't display anything when you type into a password
box. No dots, no stars, anything. Good old tradition...

Just hack in your password and hit ENTER.

Cheers
 - t


signature.asc
Description: Digital signature

Re: preseed ansible problem

[tomas]

On Sun, Oct 04, 2020 at 02:05:58PM +0500, Muhammad Yousuf Khan wrote:
> Hi all,
> 
> I am trying to run a ansible playbook [...]

I know barely enough about ansible to make me dangerous...

>  preseed: running preseed command preseed/late_command:

[...]

> Oct  4 08:01:44 log-output: dpkg-divert: warning: diverting file
> '/sbin/start-stop-daemon' from an Essential package with rename is
> dangerous, use --no-rename

This is just a warning. But being you, I'd try to understand what
is trying to divert start-stop-daemon. Might come back to bite you,
dunno.

> Oct  4 08:01:44 in-target: Ign:1 cdrom://[Official Debian GNU/Linux Live
> 10.6.0 xfce 2020-09-26T13:15] buster InRelease
> Oct  4 08:01:44 in-target: Err:2 cdrom://[Official Debian GNU/Linux Live
> 10.6.0 xfce 2020-09-26T13:15] buster Release
> Oct  4 08:01:44 in-target:   Please use apt-cdrom to make this CD-ROM
> recognized by APT. apt-get update cannot be used to add new CD-ROMs

This seems to be your real issue: the CDROM seems to be (still?) listed
in your apt sources list (look around /etc/apt/sources.list and below
/etc/apt/sources.list.d).

To fix that, you'll first have to get clear on where your to-be Debian
install is going to get its packages from (really from the CDROM?) and
adjust those files accordingly.

Cheers
 - t


signature.asc
Description: Digital signature

Re: How to disable the screen locker on amd64 buster?

[Gene Heskett]

On Sunday 04 October 2020 04:29:36 Andrei POPESCU wrote:

> On Sb, 03 oct 20, 10:45:13, Gene Heskett wrote:
> > On Saturday 03 October 2020 08:12:56 Dan Ritter wrote:
> > > Gene Heskett wrote:
> > > > The computer is controlling high powered machinery. Having the
> > > > screen locker kick in, disabling our access to the application
> > > > until we have wasted a minute typing on a poor keyboard trying
> > > > to log back in can be quite dangerous when the machine has a
> > > > runaway. Anything we do with xset is overridden before the 10
> > > > minute timeout is done.
> > > >
> > > > Some of us like xfce4, please advise how to permanently disable
> > > > lightdm and its light-locker. _Forever_. We do know how to turn
> > > > off the monitor at the end of the day.
> > >
> > > I would try
> > >
> > > apt remove lightdm light-locker
> >
> > and task-xfce, the meta installer file was also selected
> >
> > > and either installing xdm or just using startx to get X11 and
> > > XFCE up when you want it.
> >
> > Which is for me, 100% of the time, so xdm installed.
> >
> > > -dsr
> >
> > did that and installed xdm, reboot is next. But apt claimed there
> > were several hundred packages (353 count) that could be autoremoved.
> >  Is that normal after an iso install and update to 10.6?
>
> It's to be expected when you remove a high level meta-package, like
> task-xfce you mentioned above.
>
> > I did the autoremove, linuxcnc still runs, so I think we are in
> > business.

Except I now have a different initial login screen that does not accept 
my passwd.  It accepts and displays my username, but it loses the 
keyboard once it highlights the passwd box. ssh logins from here work 
just fine, but I am locked out of logging in on its own 
keyboard/mouse/monitor.

How do I fix that?

Thanks.

> For the archives:
>
>   1. Inspect the list carefully, for any package you might need.
>   2. Use 'apt-mark manual ' for the package(s) you need.
>   3. Let 'apt autoremove' (with '--purge' if you prefer) take care of
>   the rest.
>
> Kind regards,
> Andrei


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Missing i915 activity at boot time

[Rafa]

Hi,

On Sat, Oct 03, 2020 at 05:03:40PM -0400, Felix Miata wrote:

> 
> looks likely relevant to your needs.

Indeed, it does.

Thanks a lot.

Rafa.



signature.asc
Description: PGP signature

preseed ansible problem

[Muhammad Yousuf Khan]

Hi all,

I am trying to run a ansible playbook through preseed file. everything is
going good. but  when i try to run ansible-playbook via in-target command
via preseed it ends with an error here is the syslog output of preseed
installation

 preseed: running preseed command preseed/late_command: in-target apt-get
update; in-target apt-get -y upgrade; in-target apt-get -y dist-upgrade;
in-target apt-get -y install sudo less ssh ansible htop openssh-server
wget; in-target --pass-stdout /usr/bin/mkdir /opt/newfolder; in-target
--pass-stdout wget -P /opt/newfolder http://10.51.100.35/install.yml;
in-target --pass-stdout ansible-playbook /opt/newfolder/install.yml;

Oct  4 08:01:44 log-output: dpkg-divert: warning: diverting file
'/sbin/start-stop-daemon' from an Essential package with rename is
dangerous, use --no-rename
Oct  4 08:01:44 in-target: Ign:1 cdrom://[Official Debian GNU/Linux Live
10.6.0 xfce 2020-09-26T13:15] buster InRelease
Oct  4 08:01:44 in-target: Err:2 cdrom://[Official Debian GNU/Linux Live
10.6.0 xfce 2020-09-26T13:15] buster Release
Oct  4 08:01:44 in-target:   Please use apt-cdrom to make this CD-ROM
recognized by APT. apt-get update cannot be used to add new CD-ROMs
Oct  4 08:01:45 in-target: Hit:3 http://http.us.debian.org/debian buster
InRelease
Oct  4 08:01:45 in-target: Hit:4 http://security.debian.org/debian-security
buster/updates InRelease
Oct  4 08:01:45 in-target: Hit:5 http://http.us.debian.org/debian
buster-updates InRelease
Oct  4 08:01:46 in-target: Reading package lists...
Oct  4 08:01:47 in-target:
Oct  4 08:01:47 in-target: E
Oct  4 08:01:47 in-target: :
Oct  4 08:01:47 in-target: The repository 'cdrom://[Official Debian
GNU/Linux Live 10.6.0 xfce 2020-09-26T13:15] buster Release' does not have
a Release file.
Oct  4 08:01:47 in-target:
Oct  4 08:01:47 log-output: dpkg-divert: warning: diverting file
'/sbin/start-stop-daemon' from an Essential package with rename is
dangerous, use --no-rename
Oct  4 08:01:47 in-target: Reading package lists...
Oct  4 08:01:47 in-target:
Oct  4 08:01:47 in-target: Building dependency tree...
Oct  4 08:01:48 in-target:
Oct  4 08:01:48 in-target: Reading state information...
Oct  4 08:01:48 in-target:
Oct  4 08:01:48 in-target: Calculating upgrade...
Oct  4 08:01:48 in-target:
Oct  4 08:01:48 in-target: The following package was automatically
installed and is no longer required:
Oct  4 08:01:48 in-target:   libjsoncpp1
Oct  4 08:01:48 in-target: Use 'apt autoremove' to remove it.
Oct  4 08:01:48 in-target: The following packages will be upgraded:

Any help will be highly appreciated.

Thanks,
yousuf

Re: Bug Report

[Andrei POPESCU]

On Sb, 03 oct 20, 16:35:00, thinkingtw...@tutanota.com wrote:
> Hello,
> 
> Having gone through Debian's ReportBug system, I am unsure which 
> packages the issue is coming from hence the email contact.
> 
> The problem is quite straightforward. After the last update from Linux 
> Kernel 4.19.0-10amd64 to 4.19.0-11amd64 on Debian Buster, there seems 
> to be a sound input/output issue with the Headphone Jack port.
> 
> The sound comes out perfectly well through the speakers, however there 
> is a complete loss of sound output and voice input when using 
> headphones/earphones.
> 
> Reverting back to Linux Kernel 4.19.0-10amd64 when in Grub fixes the 
> issue, therefore it seems to be related to the latest update?

Indeed it suggests the issue was introduced by the kernel update, so you 
should file it against the kernel image package. Based on the above you 
should run something like

reportbug linux-image-4.19.0-11-amd64


Please do check carefully that you wrote the correct package name (e.g.  
above you missed a hyphen). Even if it can be corrected later a lot of 
important information will be completely missing from your report.

Especially for kernel packages reportbug should be including *lots* of 
information. You might want to inspect that to make sure everything is 
fine to be published in the open (the Debian Bug Tracking System is 
completely open).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: How to disable the screen locker on amd64 buster?

[Andrei POPESCU]

On Sb, 03 oct 20, 10:45:13, Gene Heskett wrote:
> On Saturday 03 October 2020 08:12:56 Dan Ritter wrote:
> 
> > Gene Heskett wrote:
> > > The computer is controlling high powered machinery. Having the
> > > screen locker kick in, disabling our access to the application until
> > > we have wasted a minute typing on a poor keyboard trying to log back
> > > in can be quite dangerous when the machine has a runaway. Anything
> > > we do with xset is overridden before the 10 minute timeout is done.
> > >
> > > Some of us like xfce4, please advise how to permanently disable
> > > lightdm and its light-locker. _Forever_. We do know how to turn off
> > > the monitor at the end of the day.
> >
> > I would try
> >
> > apt remove lightdm light-locker
> and task-xfce, the meta installer file was also selected
> > and either installing xdm or just using startx to get X11 and
> > XFCE up when you want it.
> 
> Which is for me, 100% of the time, so xdm installed.
> 
> > -dsr
> 
> did that and installed xdm, reboot is next. But apt claimed there were 
> several hundred packages (353 count) that could be autoremoved.  Is 
> that normal after an iso install and update to 10.6?

It's to be expected when you remove a high level meta-package, like 
task-xfce you mentioned above.

> I did the autoremove, linuxcnc still runs, so I think we are in 
> business. 

For the archives:

  1. Inspect the list carefully, for any package you might need.
  2. Use 'apt-mark manual ' for the package(s) you need.
  3. Let 'apt autoremove' (with '--purge' if you prefer) take care of 
  the rest.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: LaTeX et LaTeXila

[benoit]

https://www.gutenberg.eu.org/listes


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
Le jeudi 1 octobre 2020 19:54, F. Dubois  a écrit :

> Bonsoir la liste,
> Un petit souci depuis quelques jours avec les deux logiciels cités dans
> le titre. J'espère ne pas être trop HS, tout ça m'arrive avec une debian
> sid.
> Tout d'abord j'ai une petite commande pour faire des beaux encadrés avec
> un fond coloré. Or la compilation ps2pdf m'indique que dorénavant
>
>  WARNING: Transparency operations ignored - need to use
> -dALLOWPSTRANSPARENCY
>
> Error: /undefined in .setopacityalpha
>
> ... (si vous insistez je peux fournir ce qui se place ici)
>
> GPL Ghostscript 9.53.3: Unrecoverable error, exit code 1
>
> suite semblerait-il à des problèmes de sécurité.
>
> Bon j'ai contourné le problème en me créant mon propre ps2pdf avec les
> options qui vont bien. Mais ce n'est pas trop satisfaisant à long terme.
> J'ai pas trouvé grand chose sur le net... Si quelqu'un a des infos.
> Voici la commande qui pose souci :
>
> \newcommand{\encadrecouleur}[2]{\psframebox[fillstyle=solid,fillcolor=#1,framearc=0.15]{\begin{minipage}{\columnwidth-25\fboxsep}#2\end{minipage}}}
>
> Ensuite, j'utilise donc LaTeXila comme éditeur (oui, je sais, emacs fait
> tout mieux avec un mode LaTeX... mais bon). Et, depuis la dernière MAJ
> texlive -je ne saisis pas vraiment si il y a un lien et je n'ai pas vu
> passer de MAJ de LaTeXila-, l'éditeur se fige, je suis obligé de partir
> et revenir (et je ne suis pas du tout fan des 2BE3 !) de et dans la
> fenêtre pour débloquer la situation et rafraichir l'affichage (je
> préfère de loin rafraichir mes amis et moi même). Un peu lassant à la
> fin (en fait un glissement de la souris vers le coin supérieur gauche
> pour afficher toutes les fenêtres, j'utilise Gnome).
>
> Alors si quelqu'un a des idées à me soumettre. Merci
>
> Et bonne soirée, au chaud et au sec, Alex arrive !
>
> Fabien