the equivalent of a `request system snapshot` from the shell,
rather than through the cli.
Thanks
--
Chip Marshall
http://2bithacker.net/
signature.asc
Description: PGP signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puc
rt "/var/db/scripts/import/junos.xsl";
--
Chip Marshall
http://2bithacker.net/
pgpPrEbS2B4Ct.pgp
Description: PGP signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
10:18 lib
drwxrws--- 2 root wheel 512 Dec 13 18:19 op
This is on an SRX running 12.1X44-D10.4.
Any ideas?
--
Chip Marshall
http://2bithacker.net/
pgpJl2aePRazq.pgp
Description: PGP signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.ne
rypt(3) library function after it
> generates a salt.
>
> Digging through the sources, we find the following comment block
> in src/lib/libcrypt/crypt-sha1.c
Ah ha! Perfect! It appears this is specifically a NetBSD thing,
or at least my OpenBSD and FreeBSD boxes don't have cryp
calculated?
>
> we do this calculation I believe your intended format is:
> $1$salt$hash
>
> or that seems to be what our code does.
That's for MD5 passwords. I have a requirement to use SHA-1.
--
Chip Marshall
http://2bithacker.net/
umented anywhere.
I get things like "$sha1$19418$aoTClyGU$cix8MhZsXwG6OrwUgeHAoOA8f.AX"
where it appears to have the format, some number, what I think is
the salt, and then the hash.
Anyone know how these things are calculated?
--
Chip M
to be possible with a logical-
system, and I can't use fxp0 with a routing-instance.
I feel like this should be a fairly common configuration, placing
the management interface out-of-band and doing SNMP on that
interface, but I haven't found a lot of useful information
through sear
7 matches
Mail list logo