Simple way to scann all incoming and outgoing e-mails for viruses

2021-11-18 Thread john doe

Debians,

My MUA is connecting to mail.com for imap and smtp.
I have a Debian gateway server that I would like to use to scann e-mails
sent and reseaved.

Is there a way to scann incoming and outcoming e-mails on those ports
for viruses?

What I'm trying to avoid is to change the connection settings in my MUAs.

I'm not sure how realistic this is so I might refine my question based
on the provided answers.

--
John Doe



Re: aboutdebian.com

2021-11-18 Thread Nate Bargmann
* On 2021 18 Nov 23:00 -0600, A_Man_Without_Clue wrote:
> Does anyone remember the site existed in the past, aboutdebian.com?

I can't say that I do.

> I wonder if the contents are moved to somewhere else or they are not
> available at all?

It looks like the last time it was online with content was approximately
29 Feb 2020:

https://web.archive.org/web/20200229050405/http://www.aboutdebian.com/

I see that as of that date, the site had not been updated for Buster
which by that time had been released nearly half a year earlier.

After that the Web archive shows a blank page and captures from last
month show nothing Debian related.

- Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819



signature.asc
Description: PGP signature


aboutdebian.com

2021-11-18 Thread A_Man_Without_Clue
Does anyone remember the site existed in the past, aboutdebian.com?

I wonder if the contents are moved to somewhere else or they are not
available at all?



Re: [HS] Touches A, Q, X inopérante sous Ubuntu 20.04 depuis mise à jour

2021-11-18 Thread Th.A.C

Le 16/11/2021 à 18:24, Olivier a écrit :

Bonjour,

J'ai un PC portable tactile Lenovo assez récent sur lequel j'ai installé 
Ubuntu 20.04.

Après sa mise à jour hebdomadaire de lundi (hier), j'ai constaté que:

plusieurs touches du clavier "n'entraient" rien,
d'autres avaient une action inhabituelle,
le clavier logiciel, quand le PC est en mode tablette, fonctionne 
normalement.


Les touches inopérantes sont assez nombreuses:
A, Q, X


Le plus simple pour vérifier si c'est le clavier qui est en panne est de 
booter sur ton DVD/clé_usb Ubuntu et de regarder s'il fonctionne ou pas...




Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread Arkadiusz Dabrowski
Thank You all guys for help!
If systemd feature is not an option I'll try a .xession solution. Looks
promising.


Re: apache2 et virtualhosts

2021-11-18 Thread François TOURDE
Salut,

Ça manque un peu de détails, ton histoire.

Le 18949ième jour après Epoch,
Kohler Gerard écrivait:

> j'ai un réseau interne dont le nom de domaine est .home

Il est défini où et comment, ce nom ?

> j'ai installé un serveur LAMP avec plusieurs virtualhosts . ça tourne
> bien.

Genre, quels virtualhosts ?

> je me pose cependant une question: je n'arrive pas à créer de
> virtualhost dont le nom de domaine serait yyy.home.

Un message d'erreur peut-être ? C'est bien de savoir à quoi correspond
"je n'arrive pas"



Re: Late encryption of /home Partition

2021-11-18 Thread Klaus Singvogel
Hi,

thanks for all your help. It's working now as expected.

Fun fact: Had a small issue with the UUIDs, where I added a quote on left
side to a system config file, but none was allowed there. Therefore
(auto-)mounting failed (/dev/disk/by-uuid/\x22...) and it took some time
till the system came up without mounted /home.

For the sake of completeness: data loss was never possible, as it was a
fresh installed machine, which was never used productively.

Thanks again.

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27



Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread Greg Wooledge
On Thu, Nov 18, 2021 at 09:21:34PM +, Jonathan Dowland wrote:
> On Thu, Nov 18, 2021 at 03:46:48PM -0500, Greg Wooledge wrote:
> > (I still wonder whether systemd offers anything relevant here.  And if
> > not, what the hell *is* the point of systemctl --user?  I've never used
> > it, nor found any reason to use it.  Yet.)
> 
> systemd certainly does offer something here. It's related to what
> processes are considered to belong to a "session", it came in with
> version 230, and there was quite a stink about it from people who
> wanted this not to happen, at the time:
> 
> 
> It seems that the Debian Xsession setup does start a systemd --user
> service. I've never tried to use it for this purpose.

I've seen that bug before.  That's a change which got reverted, or at
least, the default behavior was returned to the previous norm.

Debian's /etc/systemd/logind.conf has

#KillUserProcesses=no

which indicates that the default is for this "kill everything the user
left running" setting to be disabled, as it was before the controversial
change.

I think this is a dead end for this particular question, because it's
an all-or-nothing setting.  Either *all* background processes that the
user creates get nuked when the user logs out, or *none* of them do.  There
doesn't appear to be a way to "mark" particular processes for reaping
while leaving the rest alone.

Maybe some other part of systemd offers more flexibility, but if so, I
don't know what part it would be.  I'm still waiting to see an actual
user-friendly *document* that describes how to use systemd.



Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread Jonathan Dowland

I'd echo Greg in that the simplest answer might lie with using systemd's
facility for this, but,

On Thu, Nov 18, 2021 at 02:34:52PM -0600, David Wright wrote:

# ~/.xsession contents

…

# now start your clients and programs, all backgrounded with &


^^
This would be the point at which OP would invoke unison,
…


# at the end of the file is one foreground program:

# wait for the window manager in the background to die
wait $Wmpid

# end-of-file


^^
when the WM dies, code here could be used to kill the unison process
(or send it a signal or anything else needed)


--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net



Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread Jonathan Dowland

On Thu, Nov 18, 2021 at 03:46:48PM -0500, Greg Wooledge wrote:

(I still wonder whether systemd offers anything relevant here.  And if
not, what the hell *is* the point of systemctl --user?  I've never used
it, nor found any reason to use it.  Yet.)


systemd certainly does offer something here. It's related to what
processes are considered to belong to a "session", it came in with
version 230, and there was quite a stink about it from people who
wanted this not to happen, at the time:


It seems that the Debian Xsession setup does start a systemd --user
service. I've never tried to use it for this purpose.


--
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net



Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread Mark Neyhart
On 11/17/21 12:39 PM, Arkadiusz Dabrowski wrote:
> Hi all
> I have a problem with unison sync termination when it is started from
> .xsessionrc.
> It works flawlessly but when I log out it is orphaned and not terminated.
> I start it like this:
> nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> Once started the parent is x-session-manager and they the same process
> group.
> What can I do to terminate the process with x-session?
>


/etc/X11/Xreset.d is a directory which holds scripts to be executed
upon termination of a display manager.  It may work to put a kill
script in there.  The /etc/X11/Xreset.d/README file has more details.
I use it to terminate non-X tasks which are started by my window manager.

Mark



apache2 et virtualhosts

2021-11-18 Thread Kohler Gerard

bonjour,

en préambule je signale que je n'ai pas de connaissances approfondies 
sur les réseaux.


je suis sous debian bullseye sur toutes les machines,

j'ai un réseau interne dont le nom de domaine est .home

j'ai installé un serveur LAMP avec plusieurs virtualhosts . ça tourne bien.

je me pose cependant une question: je n'arrive pas à créer de 
virtualhost dont le nom de domaine serait yyy.home.


yyy.com, yy.local marchent.

il y a très certainement une explication mais je ne l'ai pas trouvée. 
merci de m'éclairer .


Gerard



Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread Greg Wooledge
On Thu, Nov 18, 2021 at 02:34:52PM -0600, David Wright wrote:
> On Wed 17 Nov 2021 at 22:39:21 (+0100), Arkadiusz Dabrowski wrote:
> 
> > I have a problem with unison sync termination when it is started from
> > .xsessionrc.
> > It works flawlessly but when I log out it is orphaned and not terminated.
> > I start it like this:
> > nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> > Once started the parent is x-session-manager and they the same process
> > group.
> 
> I think this is because you're starting it in the wrong file.
> Everything in .xsessionrc should complete immediately. Use it
> to set parameters and things like that.

I think of .xsessionrc a little differently.  It's the "novice mode" file,
which you can use regardless of which x-session-manager or x-window-manager
ultimately gets used, and without needing to take control of your whole
session yourself.

That makes it great for quickie "I just want to start xclock too" type
things, where maintaining a whole .xsession file would be overkill.

In the OP's case, though, they want something that "novice mode" can't
handle, so there's a decent reason to move to "advanced mode".

(I still wonder whether systemd offers anything relevant here.  And if
not, what the hell *is* the point of systemctl --user?  I've never used
it, nor found any reason to use it.  Yet.)



Re: Buster (oldstable) install image

2021-11-18 Thread Brian
On Thu 18 Nov 2021 at 14:43:07 -0500, Polyna-Maude Racicot-Summerside wrote:

> Hi,
> Where can I get a "Buster" (10) install image.
> I can only find the 11 version on Debian Server.

https://www.debian.org/releases/buster/debian-installer/

-- 
Brian.



Re: Buster (oldstable) install image

2021-11-18 Thread Jeremy Hendricks
Hello!

Is this what you’re looking for?
https://cdimage.debian.org/cdimage/archive/

On Thu, Nov 18, 2021 at 3:35 PM Polyna-Maude Racicot-Summerside <
deb...@polynamaude.com> wrote:

> Hi,
> Where can I get a "Buster" (10) install image.
> I can only find the 11 version on Debian Server.
> Thanks
> --
> Polyna-Maude R.-Summerside
> -Be smart, Be wise, Support opensource development
>
>


Buster (oldstable) install image

2021-11-18 Thread Polyna-Maude Racicot-Summerside
Hi,
Where can I get a "Buster" (10) install image.
I can only find the 11 version on Debian Server.
Thanks
-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature


Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread David Wright
On Wed 17 Nov 2021 at 22:39:21 (+0100), Arkadiusz Dabrowski wrote:

> I have a problem with unison sync termination when it is started from
> .xsessionrc.
> It works flawlessly but when I log out it is orphaned and not terminated.
> I start it like this:
> nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> Once started the parent is x-session-manager and they the same process
> group.

I think this is because you're starting it in the wrong file.
Everything in .xsessionrc should complete immediately. Use it
to set parameters and things like that.

> What can I do to terminate the process with x-session?

Start all your X clients and programs in .xsession. They should all be
backgrounded with &, as shown in   man xinit. There's an example at
about line 78 (buster version) on that page.

You'll see there that they start the Window Manager last. This has
disadvantages, in that you can't tell programs like xterm where to
map their windows if the WM hasn't yet started. This is solved by
exec'ing the WM early in .xsession, and waiting on its PID at the
end. If and when you close the WM, wait terminates and you fall out
of the end of .xsession, and X terminates.

That way, all these background processes get destroyed, and the same
is true if you are in the habit of using Ctrl-Alt-Backspace to kill
X rather than neatly closing the WM.

Briefly:

# ~/.xsession contents

# very early stuff
# [ … ]

if [ -x /usr/bin/fvwm ]; then
exec /usr/bin/fvwm & Wmpid=$!
else
printf '%s\n' "Error - no window manager found"
fi

# now start your clients and programs, all backgrounded with &
# [ … ]

# at the end of the file is one foreground program:

# wait for the window manager in the background to die
wait $Wmpid

# end-of-file

Cheers,
David.



Re: Late encryption of /home Partition

2021-11-18 Thread Charles Curley
On Thu, 18 Nov 2021 18:17:43 +0100
Hans  wrote:

> as far as I know, you also have to edit /etc/crypttab.

Correct. Sorry, I forget that. "man crypttab".

Do this before you run update-grub.


> 
> If one has forgotten to encrypt a partition, the easiest way is, to
> boot from a livefile system. Then backup the whole content of this
> partition to an external partition. Note, this should be a ext3 or
> ext4 partition, so you preserve all hard- and softlinks.
> 
> I suggest for using rsync doing this.

I find tar easier to use for this, but rsync will do it, as you say,
provided one has an ext[34] partition to copy to.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/



Re: Late encryption of /home Partition

2021-11-18 Thread Hans
Hi all,

as far as I know, you also have to edit /etc/crypttab.

If one has forgotten to encrypt a partition, the easiest way is, to boot from 
a livefile system. Then backup the whole content of this partition to an 
external partition. Note, this should be a ext3 or ext4 partition, so you 
preserve all hard- and softlinks.

I suggest for using rsync doing this.

Then you can encrypt and format this partion and rsync everything back.

Doing so, I never lost data or settings.

Hope this helps.

Best regards

Hans




Re: Late encryption of /home Partition

2021-11-18 Thread Charles Curley
On Thu, 18 Nov 2021 14:40:14 +0100
Klaus Singvogel  wrote:

> I installed Debian 11 (bullseye) on a fresh PC.
> I created 3 partitions: /, swap, /home.
> 
> ...and forgot during installation dialog to encrypt the /home
> partition.
> 
> - how can I encrypt the /home partition now?
> - In such a way that the password is asked for manual input during
> every boot?
> 

You can. These instructions are adapted from notes I took on a similar,
related project. You do risk making your system unbootable, and
requiring a fresh installation, so proceed with caution.

Copy everything you want to preserve from the /home partition to
somewhere else. Use tar or the like to preserve permissions.

Log out all non-root users, and umount /home.

Encrypt that partition:

cryptsetup -y -v luksFormat /dev/sdaX
cryptsetup luksOpen /dev/sdaX encryptedhome

Check your work:

cryptsetup -v status encryptedhome
cryptsetup luksDump /dev/sdaX

cryptsetup luksHeaderBackup /dev/sdaX --header-backup-file ${HOSTNAME}.$(date 
+%Y.%m.%d).luks.home.backup

Then build the LVM on top of /dev/mapper/encryptedhome:

See: https://www.linuxsysadmins.com/create-logical-volume-filesystem-in-linux/

pvcreate /dev/mapper/encryptedhome  # create the physical volume.
vgcreate ${HOSTNAME}-vg /dev/mapper/encryptedhome   # Create the volume 
group.
lvcreate -n homelv -L  ${HOSTNAME}-vg # Create a logical volume the 
size of the old /crc partition.

where  is the available space less some 20 GB so 1) you have
room to grow, and 2) a background task in Bullseye has a place to
create snapshots and fsck them.

And finally, create and (optionally) tune the file system:

mkfs.ext4 /dev/mapper/${HOSTNAME}-vg-homelv
tune2fs -i 3m -c 15 /dev/mapper/${HOSTNAME}-vg-homelv

When you've done that, mount /dev/mapper/${HOSTNAME}-vg-homelv on
/home, and restore your data.

Then edit /etc/fstab to suit. Then run update-grub. Then reboot to see
if you got everything right.

> - does it make sense to use a LVM atop? How?

It may. I mentioned two reasons to do so and leave some empty
space. It would have been better to include the encryption and LVM as
part of installing,

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/



Re : [HS] Touches A, Q, X inopérante sous Ubuntu 20.04 depuis mise à jour

2021-11-18 Thread benoit
Perso j’essayerais en premier un test simple sur une touche au choix :

– avec xev, je regarderais le numéro de la touche du clavier, par exemple chez 
moi la touche A c’est keycode 24.

- Tu regardes avec xev ce que renvois cette touche défectueuse (toujours pour A)

keycode 24 (keysym 0x61, a)

- Si xev ne réagit pas à la pression d’une touche défectueuse t’es mal et il 
faut aller l’associer, je ne sais plus comment.

- Si tu obtiens un truc qui ne correspond pas, tu lui affectes a comme premier 
test :

xmodmap -e "keycode 24 = a"

Et puis il faut aller lire la doc de l’ordre des modificateurs tels que Shif, 
Alt, Ctrl…

Voici l’ordre dans le man xmodmap :

«Le premier keysym est utilisé quand aucune touche de modificateur n'est 
pressée en même temps que la touche, le second quand la touche majus‐cule 
(Shift) est pressée, le troisième en combinaison avec la touche Mode_switch 
(Alt Gr) et le quatrième en combinaison avec les touches majuscule et 
Mode_switch.»

Ce qui donne en suivant l’ordre indiqué dans le man :

xmodmap -e "keycode 24 = a A @"

Et si tu arrives à t’en sortir comme ça pour chaque touche défectueuse, ce 
n’est qu’une cafouille logiciel facile à régler provisoirement avec un peu de 
patience.

Pour pérenniser le résultat, tu écris chaque ligne ainsi

keycode 24 = a A @

dans le fichier $HOME/.xmodmaprc

Pour les signes, ils ont tous un nom à écrire en toute lettre.

Ex :

keycode 105 = less greater backslash

xmodmap -pk

Te donnera la liste complète.

--
Benoit

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

‐‐‐ Original Message ‐‐‐
Le mardi 16 novembre 2021 à 18:24, Olivier  a écrit :

> Bonjour,
>
> J'ai un PC portable tactile Lenovo assez récent sur lequel j'ai installé 
> Ubuntu 20.04.
> Après sa mise à jour hebdomadaire de lundi (hier), j'ai constaté que:
>
> plusieurs touches du clavier "n'entraient" rien,
> d'autres avaient une action inhabituelle,
> le clavier logiciel, quand le PC est en mode tablette, fonctionne normalement.
>
> Les touches inopérantes sont assez nombreuses:
> A, Q, X
>
> La touche S génère une copie d'écran. La touche W génère un beep.
>
> Beaucoup d'autres touches fonctionnent normalement.
>
> J'ai pensé à une simple passage à un clavier Qwerty au lieu d'Azerty mais ce 
> n'est visiblement pas le cas.
>
> Voici les paquets mis à jour lundi:
> python3-ldb, linux-modules, linux-image, linux-modules-extra, linux-hwe, 
> linux-headers
>
> Dans quelle direction chercher ?
> Comment décrire cette anomalie ?
> Qui a déjà vécu ça ?
>
> Slts

Re: [HS] Touches A, Q, X inopérante sous Ubuntu 20.04 depuis mise à jour

2021-11-18 Thread Olivier
1. En branchant (à tout moment) un clavier USB, ce dernier est totalement
opérationnel (layout français, ...). Sa présence ne change rien au
comportement des 2 autres clavier (le physique et le virtuel).

2. Grâce au clavier USB (et sa touche ESC), j'ai pu (assez difficilement)
accéder au menu Grub et choisir parmi 2 versions du noyau, chacun en 2
variantes (normal et recovery). En démarrant sur chacune des 4, le clavier
reste inopérant.

En tout cas, je suis certain que le clavier marchait normalement lundi:
sans lui, je n'aurai pas pu opérer la modification.


Le mer. 17 nov. 2021 à 07:12, Jean-Michel OLTRA 
a écrit :

>
> Bonjour,
>
>
> Le mardi 16 novembre 2021, Olivier a écrit...
>
>
> > Voici les paquets mis à jour lundi:
> > python3-ldb, linux-modules, linux-image, linux-modules-extra, linux-hwe,
> > linux-headers
> >
> > Dans quelle direction chercher ?
>
> Revenir au noyau précédent, si tu ne l'as pas supprimé ? Ça permettrait
> déjà
> de voir si c'est la mise à jour du noyau qui perturbe le clavier.
>
> --
> jm
>
>


(ssh-1 ongefixst maar probleem anders opgelost) Re: Debian 11, openssh server, ssh-1 toegang voor 1 client, hoe?

2021-11-18 Thread Gijs Hillenius


Wellicht wijst iemand me binnenkort terecht terecht dat ik niet moet
peuteren aan de veiligheidsknoppen van SSH.

Ik heb mijn onderliggende probleem (met een legacy Android app)
inmiddels op een andere manier opgelost.


Dank voor het meeluisteren


Gijs



Late encryption of /home Partition

2021-11-18 Thread Klaus Singvogel


Hi,

I installed Debian 11 (bullseye) on a fresh PC.
I created 3 partitions: /, swap, /home.

...and forgot during installation dialog to encrypt the /home partition.

- how can I encrypt the /home partition now?
- In such a way that the password is asked for manual input during every boot?

- does it make sense to use a LVM atop? How?

I usually prefer using shell commands before graphical stuff, but will accept 
GUI tools either.

Thanks in advance.

Best regards,
Klaus Singvogel.



Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread Greg Wooledge
On Wed, Nov 17, 2021 at 08:21:00PM -0500, songbird wrote:
> Arkadiusz Dabrowski wrote:
> ...
> > It works flawlessly but when I log out it is orphaned and not terminated.
> > I start it like this:
> > nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> > Once started the parent is x-session-manager and they the same process
> > group.
> > What can I do to terminate the process with x-session?
> 
>   does it work if you don't put it in the background?

That would prevent the rest of the X session from running, until the
unison process terminates.



Re: How to cause a process started in .xsessionrc to terminate with x-session termination?

2021-11-18 Thread songbird
Arkadiusz Dabrowski wrote:
...
> It works flawlessly but when I log out it is orphaned and not terminated.
> I start it like this:
> nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> Once started the parent is x-session-manager and they the same process
> group.
> What can I do to terminate the process with x-session?

  does it work if you don't put it in the background?


  songbird