*Hello!!!Please, I'm looking for guidance to set up a Server, it will not
be public, to host a flight simulator called Falcon BMS, about 12 people
flying online, the machine would be an I5 with 16 GB of RAM, Video Card GTX
1050 TI and a 480 GB SSD, please what would you guide me in this assembly,
I
On Mon, Nov 4, 2013 at 6:35 AM, Antoine Morales wrote:
> Please could you send me the link to download debain server?
You have contacted the debian-project list, which is for non-technical
discussion of topics related to the Debian Project but not for user
support, please contact one of the Debia
Hello
Please could you send me the link to download debain server?
I have ASUS N56V computer for 64 bits, but I need the software to boot.
Many thanks
Andreas Tille <[EMAIL PROTECTED]> writes:
> On Fri, 14 Jul 2006, martin f krafft wrote:
>> As stated in the post, at least all those developers had their accounts
>> locked.
> But shouldn't this be done by a dayly cron job that searches for secret
> keys on gluck and any other public Debian host
On Thu, Jul 13, 2006 at 08:18:27PM +0200, Bas Zoetekouw wrote:
> > An investigation of developer passwords revealed a number of weak
> > passwords whose accounts have been locked in response.
>
> That's not good.
> Should we maybe implement a stricter password policy? Or maybe only
> allow pubk
On Fri, 14 Jul 2006, martin f krafft wrote:
As stated in the post, at least all those developers had their
accounts locked.
But shouldn't this be done by a dayly cron job that searches
for secret keys on gluck and any other public Debian host
each night? If the cron job would not really lock
Hi martin!
* martin f krafft <[EMAIL PROTECTED]> [2006-07-14 09:05]:
> As stated in the post, at least all those developers had their
> accounts locked.
But they can get their account unlocked. Maybe adding no-gpg-secret-keys
to DMUP might help.
yours Martin
--
<[EMAIL PROTECTED]> Debian
also sprach Thomas Viehmann <[EMAIL PROTECTED]> [2006.07.14.0856 +0200]:
> Quite frankly, I'm more surprised and concerned about people
> keeping their Debian GPG secret key on gluck. This poses serious
> questions about trusting the developer's technical aptitude and
> sense of responsibility.
As
Aurelien Jarno wrote:
> Like having both public and private SSH keys on gluck.d.o?
Quite frankly, I'm more surprised and concerned about people keeping
their Debian GPG secret key on gluck. This poses serious questions about
trusting the developer's technical aptitude and sense of responsibility.
On Thu, Jul 13, 2006 at 10:49:04PM +0200, Andreas Tille wrote:
> On Thu, 13 Jul 2006, Bas Zoetekouw wrote:
>
> >Or maybe only allow pubkey ssh authentication?
>
> I'd vote for it and I use it since the last break in exclusively.
> The only drawback is that the mail interface to db.d.o is
> somewh
On Thu, 13 Jul 2006, Bas Zoetekouw wrote:
Or maybe only allow pubkey ssh authentication?
I'd vote for it and I use it since the last break in exclusively.
The only drawback is that the mail interface to db.d.o is
somewhat broken but if more people use it the pressure to fix
it might increase.
Steve Kemp wrote:
On Thu, Jul 13, 2006 at 08:18:27PM +0200, Bas Zoetekouw wrote:
An investigation of developer passwords revealed a number of weak
passwords whose accounts have been locked in response.
That's not good.
Should we maybe implement a stricter password policy? Or maybe only
allo
On Thu, Jul 13, 2006 at 08:18:27PM +0200, Bas Zoetekouw wrote:
> > An investigation of developer passwords revealed a number of weak
> > passwords whose accounts have been locked in response.
>
> That's not good.
> Should we maybe implement a stricter password policy? Or maybe only
> allow pub
On 7/13/06, Bas Zoetekouw <[EMAIL PROTECTED]> wrote:
Hi Martin!
You wrote:
> Debian Server restored after Compromise
Kudos to debian-admin for sorting out the situation so quickly!
Yes!
> An investigation of developer passwords revealed a number of weak
> passwords whos
Hi Martin!
You wrote:
> Debian Server restored after Compromise
Kudos to debian-admin for sorting out the situation so quickly!
> An investigation of developer passwords revealed a number of weak
> passwords whose accounts have been locked in response.
That's not good.
S
15 matches
Mail list logo
