Re: converting line input into columns




A. Sinan Unur wrote:
vanagas99@xxxxxxxxx wrote in
news:1152496902.511701.167670@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:


Tad McClellan wrote:
vanagas99@xxxxxxxxx <vanagas99@xxxxxxxxx> wrote:

sorry,

...

It is pretty clear that your "sorry" is not at all sincere,

...

Mr. McClellan, Thanks for the counseling session. Appreciate it.
Great addition to my perl learning experience.....

Sarcasm is not going to help you.

Bye.

Sinan

--
A. Sinan Unur <1usa@xxxxxxxxxxxxxxxxxxx>
(remove .invalid and reverse each component for email address)

comp.lang.perl.misc guidelines on the WWW:
http://augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html

Sinan,

I understand that. There is no reason for Tad to give a speach, either.
I hate when people think they own the world. I didn't even know what
"posting on top" means... plus, blabing about the sincerity of my
"sorry"??? "Abuse us?? what kind of statement is that? I have been in
the professional world for a long time and I am very appreciate when
folks take their time and respond with guidance. So far, I was not able
to get to work any of the previous suggestions. I keep getting
"Malformed Record" error any way I try it.

use strict;
use warnings;


use Data::Dumper;
use English qw{ -no_match_vars };


$INPUT_RECORD_SEPARATOR = '';


RECORD:
while (my $record = <DATA>) {
my (%record) = $record =~ m{\A \s*
(Severity)
:(.+?)
(Status)
:(.+?)
(PDI . ID)
:(.+?)
(Finding . Details)
(.+?)
(Vulnerability . Discussion)
(.+?)
(Manual . Fix . recommendations)
(.+?)
(References and additional information) (.+?)
\z}xms;
if (not %record) {
warn "Malformed record";
next RECORD;
}
else {
# fix up spacing
for my $entry ( values %record ) {
$entry =~ s/^\s+//gm;
$entry =~ s/\s+$//gm;
$entry =~ s/\n/ /g;
}
print Dumper \%record;
}
}

__DATA__

Physical Security
Severity : Cat II / Important
Status : Unknown
PDI ID : 1836
Finding Details
This vulnerability could not be checked by the program, it must be
checked manually.
Vulnerability Discussion
Category: II Inadequate physical protection can undermine all other
security precautions utilized to protect the system. This can
jeopardize the confidentiality, availability, and integrity of the
system. Physical security of the individual machine is the first line
protection of any system.
Manual Fix Procedures
Ensure the computer equipment is located in a protected controlled
access area.
References and additional information
FSO Checklist: 3.1 CJCSM 6510.01, C-D.3


Administrator Documentation
Severity : Cat II / Important
Status : Unknown
PDI ID : 1788
Finding Details
This vulnerability could not be checked by the program, it must be
checked manually.
Vulnerability Discussion
Category: II Using a privileged account to perform routine functions
makes the computer vulnerable to attack by any virus or Trojan Horse
inadvertently introduced during a session that has been granted full
privileges. The rule of least privilege should always be enforced.
Manual Fix Procedures
Ensure administrative personnel have two accounts assigned, a standard
user account and an account with membership in the Administrators
group. Personnel should be instructed to use the less privileged
account for day-to-day use. Each System Administrator will have a
unique userid dedicated for administering the system. Each System
Administrator will have a separate account for normal user tasks. The
built-in Administrator account will not used to administer the system.
Administrators will be properly trained. The IAO will maintain a list
of users belonging to the Administrators group.
References and additional information
FSO Checklist: 3.2 DODI 8200.2, E3.4.7 CJCSM 6510.01, A-A.3

.



Relevant Pages

  • Re: complicated parsing from the file
    ... This vulnerability could not be checked by the program, ... Using a privileged account to perform routine functions makes the ... privileges. ... Administrators will be properly trained. ...
    (perl.beginners)
  • Re: List of privileges for the Administrators group
    ... CreateFilecall is run in an 'Administrators' group it will succeed. ... 'Administrators' permissions. ... New privileges are sometimes released with OS updates and/or new OS ... user account, and the name of the domain on which the account was ...
    (microsoft.public.platformsdk.security)
  • Re: User Privileges
    ... click on Groups and double click on Administrators. ... domain users account. ... > Yser user01 has administrative privilages on the local machine. ... > privileges on local machines. ...
    (microsoft.public.windows.server.general)
  • Route add - from a not-Administator account
    ... I get "Network Access denied". ... I have added all privileges that Administrators have to my account ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Event ID: 1202
    ... No mapping between account names and security IDs was ... SeIncreaseBasePriorityPrivilege = Administrators ... "Meinolf Weber" wrote: ... A user account in one or more Group policy objects (GPOs) could not ...
    (microsoft.public.win2000.active_directory)