On 2024-03-19 13:29, debian-u...@howorth.org.uk wrote:
There's a bug in your program above, when used for PNG or JPEG. It's a
perl error and I expect you would have got an answer on perlmonks as I
suggested.
The error is described on
https://docstore.mik.ua/orelly/perl3/tk/ch17_01.htm
Look
> The threats are different for:
>
> - a laptop that travels and can be stolen
> - a desktop that does not leave your residence
> - a server that accepts connections from the outside world
>
>
> Check whether you are running ssh:
>
It is a simple home desktop PC
*@deb:~$ /sbin/service ssh
On Tue, Mar 19, 2024 at 03:33:13PM +, fxkl4...@protonmail.com wrote:
> i saw several instances of
> "This option is ignored for initramfs devices and specific to the Debian
> crypttab format. It's not supported by systemd."
> since i'm using debian and systemd are these options ignored or
"mick.crane" wrote:
> On 2024-03-19 00:42, Michael Lange wrote:
> > Hi,
> >
> > On Mon, 18 Mar 2024 19:23:39 +
> > "mick.crane" wrote:
> >
> >> I try to load images with Perl/Tk but there is message,
> >> "couldn't recognize data in image file "test.jpeg" at
> >>
I have just discovered that my Debian Bullseye server thinks that a file
has allocated 2251799813684984 blocks (!):
root@nuser:/etc/postfix# stat master.cf.bad-size
File: master.cf.bad-size
Size: 10782 Blocks: 2251799813684984 IO Block: 4096 regular
file
Device: 900h/2304d
Am Tue, 19 Mar 2024 17:42:55 +0300
schrieb Jan Krapivin :
> The thing is my password is very easy now
The simplest thin is to change that now.
, and i haven't thought about *"automated connection attempts"*,
> that sounds rather... scary?
Those attempts happen if a server software (like SSH,
On 13/03/2024 12:25, hw wrote:
On Mon, 2024-03-11 at 23:45 +0700, Max Nikulin wrote:
It seems you expect some number that you can use for any QR code. There
is no size that fits for all codes.
It's because you said: "I believed that 300dpi is high enough
resolution for QR-codes of reasonable
Jan Krapivin (12024-03-19):
> The thing is my password is very easy now, and i haven't thought about
> *"automated
> connection attempts"*, that sounds rather... scary? My password is easy
> because i am not afraid of direct physical access to the computer.
Hi.
Do you have some kind of remote
> Do you have some kind of remote access enabled or do you intend to in
> the near future?
>
No and no. Its just a simple home PC.
>
> If not, then you do not need to worry. Even less if you have a firewall
> to block any service that might appear by mistake.
>
I have UFW (gufw) enabled.
Hallo Geert en anderen,
Bedankt voor je uitgebreide reactie. Ondertussen werkt het, maar toch
interessant.
Op 18-03-2024 om 22:34 schreef Geert Stappers:
On Mon, Mar 18, 2024 at 02:13:11PM +0100, Paul van der Vlis wrote:
Hallo,
Ik heb iemand een computer verkocht met een nogal standaard
Hoi Richard en anderen,
Het probleem is ondertussen opgelost, zie ook de reply op het bericht
van Geert.
Op 18-03-2024 om 18:20 schreef Richard Lucassen:
On Mon, 18 Mar 2024 14:13:11 +0100
Paul van der Vlis wrote:
Naast networkmanager heb ik ook een verbinding via
/etc/network/interfaces
I read Debian Administrator's handbook now. And there are such words:
The root user's password should be long (12 characters or more) and
impossible to guess. Indeed, any computer (and a fortiori any server)
connected to the Internet is regularly targeted by automated connection
attempts with the
On Tue, Mar 19, 2024 at 05:42:55PM +0300, Jan Krapivin wrote:
> The root user's password should be long (12 characters or more) and
> impossible to guess. Indeed, any computer (and a fortiori any server)
> connected to the Internet is regularly targeted by automated connection
> attempts with the
Greg Wooledge writes:
> On Tue, Mar 19, 2024 at 05:42:55PM +0300, Jan Krapivin wrote:
>> The root user's password should be long (12 characters or more) and
>> impossible to guess. Indeed, any computer (and a fortiori any server)
>> connected to the Internet is regularly targeted by automated
Dan Ritter wrote:
> Jan Krapivin wrote:
> > I read Debian Administrator's handbook now. And there are such
> > words:
> >
> > The root user's password should be long (12 characters or more) and
> > impossible to guess.
> ...
>
>
> > The thing is my password is very easy now, and i haven't
On Tue 19/03/2024 at 12:00, mick.crane wrote:
> On 2024-03-19 00:42, Michael Lange wrote:
>> Hi,
>>
>> On Mon, 18 Mar 2024 19:23:39 +
>> "mick.crane" wrote:
>>
>>> I try to load images with Perl/Tk but there is message,
>>> "couldn't recognize data in image file "test.jpeg" at
>>>
Jan Krapivin wrote:
> I read Debian Administrator's handbook now. And there are such words:
>
> The root user's password should be long (12 characters or more) and
> impossible to guess.
...
> The thing is my password is very easy now, and i haven't thought about
> *"automated
> connection
i saw several instances of
"This option is ignored for initramfs devices and specific to the Debian
crypttab format. It's not supported by systemd."
since i'm using debian and systemd are these options ignored or used
On Tue, Mar 19, 2024 at 03:49:06PM +, debian-u...@howorth.org.uk wrote:
> Dan Ritter wrote:
> > Check whether you are running ssh:
> >
> > /sbin/service ssh status
>
> It's not called ssh; it is sshd
> Also nowadays it's more usual to say
>
> $ systemctl status sshd
On Debian, the
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> For most values of "you", most attackers don't care about _your_
> account, or _your_ system; they care about _any_ account, or _any_
> system. Actually targeted attacks do happen, but very rarely compared
> to what might be thought of as
On 19 Mar 2024 17:42 +0300, from daydreamer199...@gmail.com (Jan Krapivin):
> The thing is my password is very easy now, and i haven't thought about
> *"automated
> connection attempts"*, that sounds rather... scary? My password is easy
> because i am not afraid of direct physical access to the
On 19/3/24 23:02, Greg Wooledge wrote:
On Tue, Mar 19, 2024 at 05:42:55PM +0300, Jan Krapivin wrote:
The root user's password should be long (12 characters or more) and
impossible to guess. Indeed, any computer (and a fortiori any server)
connected to the Internet is regularly targeted by
On Tue 19 Mar 2024 at 13:09:55 (-0400), Henning Follmann wrote:
> On Tue, Mar 19, 2024 at 03:33:13PM +, fxkl4...@protonmail.com wrote:
> > i saw several instances of
> > "This option is ignored for initramfs devices and specific to the Debian
> > crypttab format. It's not supported by
Hi,
Max Nikulin wrote:
> When vector graphics, that does not match device resolution, is rasterized,
> the result is either non-even sizes of similar elements or fuzzy lines due
> to dithering.
Nitpicking:
"Dithering" in raster graphics is emulation of color resolution at the
expense of space
On 19/03/24 at 15:43, Jesper Dybdal wrote:
My plan is to boot a rescue disk and mount that partition read-only. Then:
* If the file looks ok after reboot, then I'll strongly suspect the RAM
- and run memtest.
* Otherwise, I'll have to run fsck and see what happens.
kernel version:
On Wed, Mar 20, 2024 at 04:22:29AM +0800, jeremy ardley wrote:
> A 'safer' implementation will not even expose an ssh port. Instead there
> will be a certificate based VPN where you first need a certificate to
> connect and then you need a separate certificate to log in as root. A
> further
On 2024-03-19 00:42, Michael Lange wrote:
Hi,
On Mon, 18 Mar 2024 19:23:39 +
"mick.crane" wrote:
I try to load images with Perl/Tk but there is message,
"couldn't recognize data in image file "test.jpeg" at
/usr/lib/x86_64-linux-gnu/perl5/5.38/Tk/Image.pm line 21"
I've tried different
27 matches
Mail list logo
