On Wed Apr 30, 2025 at 1:04 PM BST, Joe wrote:
I think it is unusual, things don't normally move to testing until
they have functioned reasonably well in unstable for a while.
Packages normally auto-migrate from unstable to testing, usually after 5
days. See
https://www.debian.org/doc/manuals
On Wed, 30 Apr 2025 07:08:04 -0400
Dan Ritter wrote:
> Andy Wood wrote:
> > Is anybody else being hit by a problem with openssh-server after
> > the 1:10.0p1-2 migration into testing the other day?
> >
> > The following packages have unmet dependencies:
> >
On Wednesday, 30 April 2025 12:08 Dan Ritter wrote:
> Andy Wood wrote:
> > Is anybody else being hit by a problem with openssh-server after the
> > 1:10.0p1-2 migration into testing the other day?
> >
> > The following packages have unmet dependencies:
> >
Andy Wood wrote:
> Is anybody else being hit by a problem with openssh-server after the
> 1:10.0p1-2 migration into testing the other day?
>
> The following packages have unmet dependencies:
> openssh-server : Depends: openssh-client (= 1:9.9p2-2) but 1:10.0p1-2 is to
>
On Wed, 30 Apr 2025 09:53:34 +0100
Andy Wood wrote:
>
> Is anybody else being hit by a problem with openssh-server after the
> 1:10.0p1-2 migration into testing the other day?
> [...]
> E: The following information from --solver 3.0 may provide additional
> context:
Is anybody else being hit by a problem with openssh-server after the
1:10.0p1-2 migration into testing the other day?
The following packages have unmet dependencies:
openssh-server : Depends: openssh-client (= 1:9.9p2-2) but 1:10.0p1-2 is to
be installed
E: Unable to correct problems, you have
On Thu, Feb 16, 2023 at 01:56:05PM +0530, jadhav vishwanath wrote:
> The ssh timeout functionality was removed in the OpenSSH-server-8.4, Now
> this functionality has been fixed(restored) in OpenSSH-server-9.2 (refer
> <https://bugzilla.mindrot.org/show_bug.cgi?id=3182#c5>) rel
Hi All,
The ssh timeout functionality was removed in the OpenSSH-server-8.4, Now
this functionality has been fixed(restored) in OpenSSH-server-9.2 (refer
<https://bugzilla.mindrot.org/show_bug.cgi?id=3182#c5>) released in Debian
bookworm. The functionality was working properly in Buster
On 2022-08-22 at 08:42 -0400, Roberto C. Sánchez wrote:
> On Mon, Aug 22, 2022 at 12:33:42PM +0200, Radwan Daoud wrote:
> >I want to install an old version of openssh server on my Debian 11.
> >I want to install Debian 9 ssh version on Debian 11 , is that possible:
On Mon, Aug 22, 2022 at 12:33:42PM +0200, Radwan Daoud wrote:
>I want to install an old version of openssh server on my Debian 11.
>I want to install Debian 9 ssh version on Debian 11 , is that possible:
>[1]https://packages.debian.org/stretch/openssh-server
>Please
On Thu, 21 Oct 2021 15:26:21 -0700
dmacdoug wrote:
>
> Assuming your sshd server is on a computer attached
> to a router which is your gateway to the internet, and
> the router is set to forward port 22 to that computer
> some ISP's don't route port 22 traffic. I know that
> AT&T blocks por
On Sb, 23 oct 21, 09:33:44, Joe wrote:
>
> The ssh protocol by default works on TCP port 22, but the sshd (server)
> configuration file allows different ports to be specified. If you have
> port 22 open to the Internet, you will get many firewall logs for
> people trying brute-force password attac
On Sat, 23 Oct 2021 08:42:09 +0300
Semih Ozlem wrote:
> Are there specific tutorials websites that you can recommend, how
> about port forwarding. From where which sites in particular can I
> learn about these topics?
Here's a good practical guide:
https://www.digitalocean.com/community/tutoria
Are there specific tutorials websites that you can recommend, how about
port forwarding. From where which sites in particular can I learn about
these topics?
Joe , 22 Eki 2021 Cum, 00:08 tarihinde şunu yazdı:
> On Thu, 21 Oct 2021 23:48:38 +0300
> Semih Ozlem wrote:
>
> > I think it was somethin
On Friday, 22 Oct 2021 at 09:46, David Wright wrote:
> I'm guessing it was a BT Home Hub.
EE *before* bought by BT but maybe same supplier even then.
> One might suspect that 100 lies at the lower boundary of its DHCP
> range, leaving 99 static addresses free. But no guess at a product.
I canno
On Fri 22 Oct 2021 at 11:59:40 (+0100), Eric S Fraga wrote:
> On Friday, 22 Oct 2021 at 13:40, Andrei POPESCU wrote:
> > Typically modems and home routers use the .1 address for themselves.
>
> Interesting. My last 2 routers have had *.254 (!)
I'm guessing it was a BT Home Hub. It's idiosyncrati
On Friday, 22 Oct 2021 at 13:40, Andrei POPESCU wrote:
> Typically modems and home routers use the .1 address for themselves.
Interesting. My last 2 routers have had *.254 (!) and *.100 as their
address.
--
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.1
On Jo, 21 oct 21, 22:52:37, Semih Ozlem wrote:
> I am unable to access my modem settings page when writing 192.168.1.100 to
> check if there is a firewall.
Are you sure this is the correct address? How did you establish that?
Typically modems and home routers use the .1 address for themselves.
E
That's 'systemctl status ssh' without the 1) of course.I meant to put more
steps but decided not to
--
James B
portoteache...@fastmail.com
Em Sex, 22 Out ʼ21, às 00:18, James B escreveu:
> Hi Semih,
>
> In my opinion, I would go back to basics first.You may have installed
> openssh but it
Hi Semih,
In my opinion, I would go back to basics first.You may have installed openssh
but it doesn't necessarily run by default (for reasons that will make sense
when you look at it further).Do you know how to start systemd services? It
looks to me like your ssh server isnt' running.So, run (
On Fri, 22 Oct 2021 at 09:53, Semih Ozlem wrote:
> From:Semih Ozlem
> To:Debian Users , ubuntu-us...@lists.ubuntu.com
Please, do not send individual messages to more than one
mailing list.
It is rather unfriendly to everyone else that reads each list, because
we do not see any conversation tha
I am unable to access my modem settings page when writing 192.168.1.100 to
check if there is a firewall.
Below is the web page that I get
Unable to connect
Firefox can’t establish a connection to the server at 192.168.1.100.
The site could be temporarily unavailable or too busy. Try again
On Thu, Oct 21, 2021 at 11:41:43PM +0300, Semih Ozlem wrote:
> Hi everyone,
>
> I set up an openssh server and I am trying to access that machine remotely
> (not from the local network. but from another ip address). I get an error
> (something about port 22). What setting needs to
On Thu, Oct 21, 2021 at 09:07:02PM +, Semih Ozlem wrote:
> Yes the error message is
>
> ssh: connect to host (ip address of remote host) port 22: Connection refused
This message means one of these things:
1) The sshd process is not running, or is not listening on the default port.
2) A fire
On Thu, 21 Oct 2021 23:48:38 +0300
Semih Ozlem wrote:
> I think it was something like "ssh: connect to host port 22:
> Connection refused" It will take me a little while to get the same
> error message again.
>
>
Ideally you need to do more than open the ssh port, particularly if you
inten
es B
>> portoteache...@fastmail.com
>>
>>
>>
>> Em Qui, 21 Out ʼ21, às 21:41, Semih Ozlem escreveu:
>>
>> Hi everyone,
>>
>> I set up an openssh server and I am trying to access that machine
>> remotely (not from the local network. but f
ge please?
>
> Best
>
> JB
>
> --
> James B
> portoteache...@fastmail.com
>
>
>
> Em Qui, 21 Out ʼ21, às 21:41, Semih Ozlem escreveu:
>
> Hi everyone,
>
> I set up an openssh server and I am trying to access that machine remotely
> (no
Hi Semih,
Could you post the exact wording of the error message please?
Best
JB
--
James B
portoteache...@fastmail.com
Em Qui, 21 Out ʼ21, às 21:41, Semih Ozlem escreveu:
> Hi everyone,
>
> I set up an openssh server and I am trying to access that machine remotely
> (
Hi everyone,
I set up an openssh server and I am trying to access that machine remotely
(not from the local network. but from another ip address). I get an error
(something about port 22). What setting needs to be checked and what needs
to be done on the machine that openssh server is running and
On Mon, Aug 17, 2020 at 09:31:20PM +0300, Semih Ozlem wrote:
> Hi Greg,
> Sorry for lack of details in my response, it was just a tiring day because
> almost the whole day passed and finally the issue is at least temporarily
> resolved, and one gets somewhat forgetful. the firewall was enabled on t
Hi Greg,
Sorry for lack of details in my response, it was just a tiring day because
almost the whole day passed and finally the issue is at least temporarily
resolved, and one gets somewhat forgetful. the firewall was enabled on the
debian machine, and I am trying to connect to the debian machine f
On 8/17/2020 8:15 PM, Semih Ozlem wrote:
Sorry for the maybe too simple question, but how does one open and close
ports, and how can ufw firewall be configured so as to allow ssh
connections
Have a look at (1).
In the linux world, it is wise to answer at the bottom of an e-mail as
opposed to
On Mon, Aug 17, 2020 at 08:12:32PM +0200, john doe wrote:
> On 8/17/2020 8:04 PM, Semih Ozlem wrote:
> > And thanks to Greg for the quick response.
> >
> > Semih Ozlem , 17 Ağu 2020 Pzt, 21:03
> > tarihinde şunu yazdı:
> >
> > > Sorry for the trailing list of emails, I just realized the firewall
On 8/17/2020 8:04 PM, Semih Ozlem wrote:
And thanks to Greg for the quick response.
Semih Ozlem , 17 Ağu 2020 Pzt, 21:03
tarihinde şunu yazdı:
Sorry for the trailing list of emails, I just realized the firewall was
preventing the connection. After disabling ssh connection works. However I
woul
Regarding previous question on ssh server
>>> Both machines are in the same home network, connected to the internet
>>> through modem.
>>> One machine is running on windows the other on debian. (I tried running
>>> the windows machine from debian as well a
hine is running on windows the other on debian. (I tried running
>> the windows machine from debian as well and that did not work either.)
>> When I run localhost on the debian machine, the openssh-server is
>> running, and can connect to it from the same machine.
>> When I run
unning
> the windows machine from debian as well and that did not work either.)
> When I run localhost on the debian machine, the openssh-server is running,
> and can connect to it from the same machine.
> When I run openssh-server on the windows machine, I am able to connect to
> it from d
debian machine, the openssh-server is running,
and can connect to it from the same machine.
When I run openssh-server on the windows machine, I am able to connect to
it from debian.
When I run openssh-server from debian, I am not able to connect to it from
the other machine regardless of it working
On Mon, Aug 17, 2020 at 08:49:11PM +0300, Semih Ozlem wrote:
> I am trying to connect to a debian machine with openssh-server installed.
> When I try to connect, I get the message "connection timed out". I am not
> sure if this group is the right place to address this is
Hi,
I am trying to connect to a debian machine with openssh-server installed.
When I try to connect, I get the message "connection timed out". I am not
sure if this group is the right place to address this issue, but is there a
configuration file that needs to be adjusted to fix the i
On Fri, Jul 24, 2020 at 09:49:04PM +0300, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 17:53:53, to...@tuxteam.de wrote:
[...]
> Aren't those files an internal implementation detail? Most users won't
> ever need to interact with those files or even be aware of their
> existence.
Strictly speaking
On Fri, Jul 24, 2020 at 09:49:04PM +0300, Andrei POPESCU wrote:
> Aren't those files an internal implementation detail? Most users won't
> ever need to interact with those files or even be aware of their
> existence.
The whole design is built around "you can do this with systemctl commands,
or b
On Vi, 24 iul 20, 17:53:53, to...@tuxteam.de wrote:
> On Fri, Jul 24, 2020 at 05:18:24PM +0300, Andrei POPESCU wrote:
> > On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> > > On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > > > Seriously?
> > >
> > > Yes seriously. This is
On Fri, Jul 24, 2020 at 05:18:24PM +0300, Andrei POPESCU wrote:
> On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> > On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > > Seriously?
> >
> > Yes seriously. This is a pain point that could be avoided. I'm not a
> > systemd hater.
On Vi, 24 iul 20, 15:00:32, Jonathan Dowland wrote:
> On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
> > Seriously?
>
> Yes seriously. This is a pain point that could be avoided. I'm not a
> systemd hater. I do some quite advanced things with it. But I don't
> think it's above cri
On Fri, Jul 24, 2020 at 09:52:29AM -0400, Greg Wooledge wrote:
[...]
> I don't know of any specific term for a directory's physical
> manifestation, other than "directory".
>
> In the olden days, a directory was basically a series of 16-byte
> records (14 bytes for the filename, 2 bytes for the
On Fri, Jul 24, 2020 at 09:56:27AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
[...]
> Since writing that, I've had occasion to remember the term 'dirent',
> which I think is more the in-memory representation of a directory than
> the on-disk representation, but m
On Thu, Jul 23, 2020 at 01:26:50PM +0300, Andrei POPESCU wrote:
Seriously?
Yes seriously. This is a pain point that could be avoided. I'm not a
systemd hater. I do some quite advanced things with it. But I don't
think it's above criticism, and this is an area I feel is worthy of
criticism.
Co
On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
>
> On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
>
>> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>>> Nitpick: the directory entry is the one carrying the name.
>>
>> I had the impression that even a directory is stored in/as
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
Sounds like a case where directly editing the underlying
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
> On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
>
>> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
>>
>>> Sounds like a case where directly editing the underlying device,
>>> to modify inode-or-equivalent contents s
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> > Sounds like a case where directly editing the underlying device, to
> > modify inode-or-equivalent contents such that the slash is no longer
^
Nitpick:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> Sounds like a case where directly editing the underlying device, to
> modify inode-or-equivalent contents such that the slash is no longer
> there, might even be *advisable*.
Yeah, some sort of direct hex-edit on the unmounted file sy
On 2020-07-24 at 07:45, Greg Wooledge wrote:
> On Thu, Jul 23, 2020 at 07:16:06PM -0400, The Wanderer wrote:
>
>> On 2020-07-23 at 06:26, Andrei POPESCU wrote:
>>> Seriously? Could you please show me how would I create a file on
>>> *nix containing '/' in the name?
>>
>> It's theoretically possi
On Thu, Jul 23, 2020 at 07:16:06PM -0400, The Wanderer wrote:
> On 2020-07-23 at 06:26, Andrei POPESCU wrote:
> > Seriously? Could you please show me how would I create a file on *nix
> > containing '/' in the name?
>
> It's theoretically possible, but AFAIK basically nothing would support
> it or
On Vi, 24 iul 20, 10:58:24, to...@tuxteam.de wrote:
>
> It's as if they were copying the disruptive antipatterns of proprietary
> software companies. But we don't need those antipatterns in the free
> software context, do we?
One person's bug is another's feature.
Kind regards,
Andrei
--
http:/
On Thu, Jul 23, 2020 at 06:48:10PM -0500, David Wright wrote:
> On Thu 23 Jul 2020 at 10:12:09 (+0200), to...@tuxteam.de wrote:
[...]
> > Hours of fun :-)
>
> Sure, I agree. But they're hours I don't really have. That's one
> reason why I don't run a DE: I just don't understand what's going on
>
On Thu 23 Jul 2020 at 10:12:09 (+0200), to...@tuxteam.de wrote:
> On Wed, Jul 22, 2020 at 02:22:32PM -0500, David Wright wrote:
> > On Wed 22 Jul 2020 at 14:23:48 (-0400), rhkramer wrote:
>
> [...]
>
> > > The basic solution involved stopping gparted [...]
>
> > AIUI gparted locks up the disks w
>>> Yes. Unfortunately Systemd decided to forbid '/' in unit names,
You can probably work around that by using '⁄', for example ;-)
Stefan
On 2020-07-23 at 06:26, Andrei POPESCU wrote:
> On Mi, 22 iul 20, 16:26:24, Jonathan Dowland wrote:
>
>> On Wed, Jul 22, 2020 at 07:38:54AM -0400, Greg Wooledge wrote:
>>
>>> Apparently this unit refers to the root file system. I have no
>>> idea why it's masked for you, but that's where I'd st
On Mi, 22 iul 20, 16:26:24, Jonathan Dowland wrote:
> On Wed, Jul 22, 2020 at 07:38:54AM -0400, Greg Wooledge wrote:
> > Apparently this unit refers to the root file system. I have no idea
> > why it's masked for you, but that's where I'd start looking.
>
> Yes. Unfortunately Systemd decided to f
On Wed, Jul 22, 2020 at 02:22:32PM -0500, David Wright wrote:
> On Wed 22 Jul 2020 at 14:23:48 (-0400), rhkramer wrote:
[...]
> > The basic solution involved stopping gparted [...]
> AIUI gparted locks up the disks when you run it [...]
Whatever "locking up the disks" means, in this context.
N
On Wednesday, July 22, 2020 02:54:27 PM Greg Wooledge wrote:
> On Wed, Jul 22, 2020 at 02:23:48PM -0400, rhkramer wrote:
> > The basic solution involved stopping gparted (I don't know why, but
> > google found a page that described the same problem I had and the page
> > said it occurred with gpart
voke-rc.d: initscript ssh, action "start" failed.
> ● ssh.service - OpenBSD Secure Shell server
>Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset:
> enabled)
>Active: inactive (dead)
> Docs: man:sshd(8)
>man:sshd_config(
On Wed, Jul 22, 2020 at 02:23:48PM -0400, rhkramer wrote:
> The basic solution involved stopping gparted (I don't know why, but google
> found a page that described the same problem I had and the page said it
> occurred with gparted running and went away with gparted stopped.
Fascinating.
Greg Wooledge writes:
> unicorn:~$ systemctl status -.mount
> systemctl: invalid option -- '.'
> Hint: to specify units starting with a dash, use "--":
> systemctl [OPTIONS...] {COMMAND} -- -.mount ...
> unicorn:~$ systemctl status -- -.mount
> ● -.mount - /
>Loaded: loaded (/etc/fstab;
reset:
enabled)
Active: inactive (dead)
Docs: man:sshd(8)
man:sshd_config(5)
dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess returned
error exit status 1
Processing triggers for man-db (2.8.5-2) ...
Proce
On Wed, Jul 22, 2020 at 07:38:54AM -0400, Greg Wooledge wrote:
Apparently this unit refers to the root file system. I have no idea
why it's masked for you, but that's where I'd start looking.
Yes. Unfortunately Systemd decided to forbid '/' in unit names, and also
to map all mounts to units. '
On Tue, Jul 21, 2020 at 09:48:22PM -0400, rhkramer wrote:
> I get this error when trying to apt-get install openssh-server on my (up to
> date) Buster system:
>
> Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is
> masked.
>
> I tried (based o
It should "just work" - if you can "ssh localhost" - the server is running.
Hope this helps
Andy C
On Wed, Jul 22, 2020 at 2:06 AM rhkramer wrote:
> I get this error when trying to apt-get install openssh-server on my (up
> to
> d
I get this error when trying to apt-get install openssh-server on my (up to
date) Buster system:
Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is
masked.
I tried (based on the reference below):
root@s32:/# systemctl unmask org.freedesktop.systemd1.UnitMasked
Unit
On Fri, Nov 23, 2018 at 12:29:41PM +0100, owl...@gmail.com wrote:
>
> I have tried to use the right KexAlgorithm and Ciphers, but dropbear
> client fail always
>
Do you have "LogLevel DEBUG3" in sshd_config? Can you specify a high
debug log level on the dropbear side?
Regards,
-Roberto
--
Ro
Il giorno gio 22 nov 2018 alle ore 20:50 owl...@gmail.com
ha scritto:
>
> Il giorno gio 22 nov 2018 alle ore 20:48 Roberto C. Sánchez
> ha scritto:
> >
> > On Thu, Nov 22, 2018 at 08:40:52PM +0100, owl...@gmail.com wrote:
> > > Thanks Roberto,
> > >
> > > I have tried also the latest dropbear ser
Il giorno gio 22 nov 2018 alle ore 20:48 Roberto C. Sánchez
ha scritto:
>
> On Thu, Nov 22, 2018 at 08:40:52PM +0100, owl...@gmail.com wrote:
> > Thanks Roberto,
> >
> > I have tried also the latest dropbear server but this is incompatible too
> >
> > Do you have idea how can I find appropriate ke
On Thu, Nov 22, 2018 at 08:40:52PM +0100, owl...@gmail.com wrote:
> Thanks Roberto,
>
> I have tried also the latest dropbear server but this is incompatible too
>
> Do you have idea how can I find appropriate key exchange and cipher
> algorithms?
>
Please don't top post. It is considered impo
0, owl...@gmail.com wrote:
> >Hi, I have compatibility issues with the latest version of openssh-server
> >and an old dropbear client, the dopbear client stops at preauth
> >ov 22 14:34:03 myhostname sshd[3905]: debug1: Client protocol version
> >2.0; client
On Thu, Nov 22, 2018 at 07:32:07PM +0100, owl...@gmail.com wrote:
>Hi, I have compatibility issues with the latest version of openssh-server
>and an old dropbear client, the dopbear client stops at preauth
>ov 22 14:34:03 myhostname sshd[3905]: debug1: Client protocol version
Hi, I have compatibility issues with the latest version of openssh-server
and an old dropbear client, the dopbear client stops at preauth
*ov 22 14:34:03 * *myhostname **sshd[3905]: debug1: Client protocol version
2.0; client software version dropbear_0.46*
*Nov 22 14:34:03 **myhostname** sshd
Hello,
Just to let you know - the link on Debian website gives 404:
https://packages.debian.org/wheezy/openssh-server
http://metadata.ftp-master.debian.org/changelogs/main/o/openssh/openssh_6.0p1-4+deb7u7_changelog
I got it from the tarball so it's not critical.
Thanks
Adam
On Tue, 17 Jun 2014 22:00:49 -0400
Jerry Stuckle wrote:
> On 6/17/2014 7:41 PM, Celejar wrote:
> > On Sat, 14 Jun 2014 22:32:16 -0400
> > Jerry Stuckle wrote:
> >
> >> On 6/14/2014 2:06 PM, Patrick Chkoreff wrote:
> >
> > ...
> >
> >>> Here's a way to generate a *truly* random password that i
On 6/17/2014 7:41 PM, Celejar wrote:
> On Sat, 14 Jun 2014 22:32:16 -0400
> Jerry Stuckle wrote:
>
>> On 6/14/2014 2:06 PM, Patrick Chkoreff wrote:
>
> ...
>
>>> Here's a way to generate a *truly* random password that is *also* memorable:
>>>
>>> http://diceware.com
>>>
>>> Instead of using you
On Sat, 14 Jun 2014 22:32:16 -0400
Jerry Stuckle wrote:
> On 6/14/2014 2:06 PM, Patrick Chkoreff wrote:
...
> > Here's a way to generate a *truly* random password that is *also* memorable:
> >
> > http://diceware.com
> >
> > Instead of using your computer to generate allegedly random bits, yo
On Sun, Jun 15, 2014 at 12:32 AM, wrote:
> On Sat, 14 Jun 2014, Bob Proulx wrote:
>>
>> The biggest problem I have found using random passwords is that some
>> sites truncate the password to a shorter number of characters. Some
>> of those are fairly high profile sites! http://www.schwab.com/ i
On Saturday 14 June 2014 19:06:40 Patrick Chkoreff wrote:
> Don Armstrong wrote, On 06/14/2014 01:04 PM:
> > If you just want purely random passwords, though, you might try
> > makepasswd instead. pwgen is more biased towards generating
> > distinguishable, memorable passwords instead of truly rand
On Saturday 14 June 2014 11:57:59 Lisi Reisz wrote:
> On Friday 13 June 2014 22:02:06 Bob Proulx wrote:
> > Just to plug a good tool I like using pwgen to generate truly random
> > passwords. A long random password is sufficiently difficult to
> > exploit. If you are using passwords that are easy
On 14/06/14 13:57, Brian wrote:
On Sat 14 Jun 2014 at 11:50:57 +0100, Iain M Conochie wrote:
Can you categorically state what _are_ the preseed options for the
openssh-server package? I can find 4:
The ones you listed below are for a fresh install of Wheezy. Jessie is
different. This output
On Sat, 14 Jun 2014, Bob Proulx wrote:
The biggest problem I have found using random passwords is that some
sites truncate the password to a shorter number of characters. Some
of those are fairly high profile sites! http://www.schwab.com/ is a
good example that truncates passwords at eight cha
On 6/14/2014 2:06 PM, Patrick Chkoreff wrote:
> Don Armstrong wrote, On 06/14/2014 01:04 PM:
>
>> If you just want purely random passwords, though, you might try
>> makepasswd instead. pwgen is more biased towards generating
>> distinguishable, memorable passwords instead of truly random ones.
>
Curt wrote:
> Bob Proulx wrote:
> > Just to plug a good tool I like using pwgen to generate truly random
> > passwords. A long random password is sufficiently difficult to
> > exploit. If you are using passwords that are easy to crack then they
> > should definitely be disabled. Here is an examp
On Sat, 14 Jun 2014 14:06:40 -0400
Patrick Chkoreff wrote:
> Instead of using your computer to generate allegedly random bits,
> you use five six-sided dice to generate truly random bits.
You can also eat peas and count the number of seconds
between two farts, then divide it by the captain's age
Don Armstrong wrote, On 06/14/2014 01:04 PM:
> If you just want purely random passwords, though, you might try
> makepasswd instead. pwgen is more biased towards generating
> distinguishable, memorable passwords instead of truly random ones.
Here's a way to generate a *truly* random password that
On Sat, 14 Jun 2014, Lisi Reisz wrote:
> Can it be set to use anything other than alpha-numeric?
Yes.
$ pwgen -sy 16 1;
Z/;fv!2B:C=^@kvH
If you just want purely random passwords, though, you might try
makepasswd instead. pwgen is more biased towards generating
distinguishable, memorable password
On Sat 14 Jun 2014 at 11:50:57 +0100, Iain M Conochie wrote:
> Can you categorically state what _are_ the preseed options for the
> openssh-server package? I can find 4:
The ones you listed below are for a fresh install of Wheezy. Jessie is
different. This output can be obtained from
d
On Friday 13 June 2014 22:02:06 Bob Proulx wrote:
> Just to plug a good tool I like using pwgen to generate truly random
> passwords. A long random password is sufficiently difficult to
> exploit. If you are using passwords that are easy to crack then they
> should definitely be disabled. Here i
On 06/14/2014 12:57 PM, Lisi Reisz wrote:
> On Friday 13 June 2014 22:02:06 Bob Proulx wrote:
>> Just to plug a good tool I like using pwgen to generate truly random
>> passwords. A long random password is sufficiently difficult to
>> exploit. If you are using passwords that are easy to crack t
seed options for the
openssh-server package? I can find 4:
openssh-server ssh/vulnerable_host_keys note
openssh-server ssh/use_old_init_script boolean true
openssh-server ssh/encrypted_host_key_but_no_keygen note
openssh-server ssh/disable_cr_auth boolean false
Do you know of a
On 2014-06-13, Bob Proulx wrote:
>
>
> Just to plug a good tool I like using pwgen to generate truly random
> passwords. A long random password is sufficiently difficult to
> exploit. If you are using passwords that are easy to crack then they
> should definitely be disabled. Here is an example
On 14/06/14 07:18, Brian wrote:
> On Fri 13 Jun 2014 at 23:36:41 +0530, Murukesh Mohanan wrote:
>
>> That's about the bug report that led to all this:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298138
>
> The usual complaint, I see. password1 is an insecure password for root
> to use so
1 - 100 of 140 matches
Mail list logo